Connect your channels in OpenQuok Cloud. Complete OAuth in the dashboard. Then set scheduledAt with curl, the Node SDK, MCP, or CLI. UTC timestamps stay predictable in JSON. Schedule to Bluesky through the same request shape.
CLI and SDK users
Queue publish times in one REST call. OpenQuok delivers on the worker. You do not run cron per platform. Channel and post caps on your plan still apply. Schedule to Bluesky through the same request shape.
Agent operators
Ask your agent to schedule into your workspace. It uses the accounts you connected. It does not onboard other people’s customers onto your token. Schedule to Bluesky through the same request shape.
Federated & custom-PDS users
Stay on bsky.social or run your own PDS. OpenQuok resolves your service URL at connect and schedules through your home server with an app password — not your main account password. Schedule to Bluesky through the same request shape.
Three steps
Add Bluesky scheduling,to your product in three steps
Connect Bluesky once, then schedule posts and track delivery through the same API.
Test your social media scheduling API payload before you ship code
Compose a scheduled post with sample channels in your browser. Set publish time, document carousel names, follow-up comments, and optional repeat cadence, then copy the JSON body. Copy JSON is free — no account required. Scheduling and file uploads need a workspace.
Explore request and response examples by format
Static examples mirror shipped OpenQuok public API payloads and success responses.
Schedule a text post on Bluesky. Set scheduledAt to an ISO-8601 UTC timestamp.
Install @openquok/node-sdk in your Next.js or TypeScript backend. Call post() to schedule on Bluesky with the same JSON you send to POST /public/posts. scheduledAt, repeatInterval, and provider settings stay typed.
# After you add OpenQuok in your MCP client config:
# Ask your agent to schedule on Bluesky.
> Schedule on Bluesky for tomorrow at 10am UTC:
> Product launch recap with a link to our pricing page.
MCP server
MCP toolsfor Cursor and Claude Codesame public API
Connect your MCP client with an opo_ token. Schedule Bluesky posts from chat with schedulePostTool and integrationList. Agents use the same REST API as curl and the SDK.
Register your app under Developers → Apps. Users approve access to their workspace, then your app calls the public API for Bluesky scheduling without pasted workspace keys.
# Redirect the user to approve your app
https://www.openquok.com/oauth/authorize?client_id=oqc_your_client_id&response_type=code&state=random123
# Exchange the code for an opo_ access token, then call:
curl -H "Authorization: Bearer opo_oauth_access_token" \
https://api.openquok.com/api/v1/public/integrations
# Match identifier: bluesky — copy id into integrationIds
Pricing
Transparent pricingfor Blueskyscheduling API
Every paid plan includes Public API access, MCP tools, and OAuth apps per workspace. Schedule on Bluesky via REST, Node SDK, or MCP — start with a 7-day free trial, no credit card required.
Solo
$29/ mo
Prototype Bluesky scheduling from curl, SDK, or MCP before you ship to customers.
Connect Bluesky with an app password, set scheduledAt in UTC, and schedule text, media, and follow-up replies from your app or agent.
Sign up for free, open a workspace, and choose Connect channel → Bluesky. Enter your handle or email, PDS service URL (https://bsky.social for most accounts), and an app password from Bluesky settings — not your main password. For self-hosted deployments, see the self-host Bluesky setup guide.
Call GET /public/integrations with your workspace programmatic token. Match the `identifier` field to `bluesky` and copy the channel UUID into `integrationIds`. Field tables for Bluesky live on Bluesky provider settings.
Yes. Send one POST /public/posts payload with the channel UUID in `integrationIds`. Set `scheduledAt` to an ISO-8601 UTC timestamp for the publish time. OpenQuok stores the instant in UTC and publishes when the worker dequeues the row. See Bluesky CLI examples for copy-paste recipes.
No. OpenQuok bills workspaces on paid plans, not per-post credits. Public API access requires a paid tier. Each opo_ token gets 30 requests per hour on OpenQuok Cloud. Scheduled posts still count toward your monthly post quota. See cloud limits.
Use the interactive Payload Wizard on this page with sample channels, or open the full wizard in your workspace after you sign in. Copy JSON stays free on public pages. Provider field reference: Bluesky settings. Channel landing: Bluesky.
A channel is one connected social account (Facebook, Instagram, LinkedIn, TikTok, YouTube, Threads, and more). Connect channels in the dashboard. Browse networks on Supported channels.