OPENQUOK Twitter / X Scheduling API
Schedule Twitter/X posts through one simple API. Queue tweets and thread chains for a future instant with scheduledAt in UTC and chained follow-up replies.
Built for people who connect their own channels
Who schedules on, X via API?
Vibe coders
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 X 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 X 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 X through the same request shape.
Three steps
Add X scheduling,to your product in three steps
Connect X once, then schedule posts and track delivery through the same API.
New to OpenQuok? Read the getting started guide
Sample channels
Sample channels
Endpoint
POST /api/v1/public/posts
{
"scheduledAt": "2026-05-14T10:00:00.000Z",
"status": "scheduled",
"body": "Launch tweet from the public API.",
"integrationIds": [
"<integration-id>"
]
}Free payload wizard
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 tweet on X. Set scheduledAt to an ISO-8601 UTC timestamp.
Request
{
"scheduledAt": "2026-05-14T10:00:00.000Z",
"status": "scheduled",
"body": "Launch tweet from the public API.",
"integrationIds": [
"<integration-id>"
]
}Response
{
"success": true,
"data": {
"postGroup": "9a0a1b2c-3d4e-4f5a-9b8c-aa11bb22cc33",
"posts": [
{
"id": "5b3c1d2e-9a3f-4e6b-bb12-2c0a5f1a90a1",
"state": "QUEUE",
"publishDate": "2026-05-14T10:00:00.000Z",
"organizationId": "c1d8a3f4-1234-4abc-bf12-1234567890ab",
"integrationId": "1f9a4f3a-3b2c-4f4a-9d8e-7a3f6b1c8e22",
"content": "Launch tweet from the public API.",
"delay": 0,
"postGroup": "9a0a1b2c-3d4e-4f5a-9b8c-aa11bb22cc33",
"title": null,
"description": null,
"parentPostId": null,
"releaseId": null,
"releaseUrl": null,
"settings": null,
"image": null,
"intervalInDays": null,
"error": null,
"deletedAt": null,
"createdByUserId": null,
"createdAt": "2026-05-10T09:00:00.000Z",
"updatedAt": "2026-05-10T09:00:00.000Z"
}
]
}
}More social media scheduling API platforms
Compare X with other networks, or jump to platform docs and provider settings.
-
TikTok
Vertical video and photo carousels. Direct publish or queue to your TikTok inbox so you can add trending audio.
-
Instagram
Feed posts, Reels, carousels, and Stories. Trial Reels, collaborator tags, and follow-up comments.
-
YouTube
Long-form MP4 uploads and vertical Shorts. Title, privacy, tags, and custom thumbnail per video.
-
Facebook
Page feed posts, MP4 Reels, Stories, link-preview cards, and scheduled follow-up comments. Built for Facebook Pages, not personal profiles.
-
Threads
500-character posts with media and scheduled follow-up reply chains. Conversation-first text on Meta Threads.
-
LinkedIn
B2B thought leadership on profile and company Page. Scheduled and reviewed. Ready when buyers research you.
- Open X channel page
Node SDK
TypeScript SDKfor Node.js backendstyped REST calls
Install @openquok/node-sdk in your Next.js or TypeScript backend. Call post() to schedule on X with the same JSON you send to POST /public/posts. scheduledAt, repeatInterval, and provider settings stay typed.
npm install @openquok/node-sdk
import Openquok from '@openquok/node-sdk';
const openquok = new Openquok('opo_your_programmatic_token');
await openquok.post({
{
"scheduledAt": "2026-05-14T10:00:00.000Z",
"status": "scheduled",
"body": "Launch tweet from the public API.",
"integrationIds": [
"<integration-id>"
]
}
});# After you add OpenQuok in your MCP client config:
# Ask your agent to schedule on X.
> Schedule on X 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 X posts from chat with schedulePostTool and integrationList. Agents use the same REST API as curl and the SDK.
OAuth2 for apps
OAuth2 appsuser consent workspace tokens
Register your app under Developers → Apps. Users approve access to their workspace, then your app calls the public API for X 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: x — copy id into integrationIdsPricing
Transparent pricingfor X scheduling API
Every paid plan includes Public API access, MCP tools, and OAuth apps per workspace. Schedule on X via REST, Node SDK, or MCP — start with a 7-day free trial, no credit card required.
Solo
Prototype X scheduling from curl, SDK, or MCP before you ship to customers.
Features
- 1 agent workspace
- Total 15 channels
- 500 posts per month
- Unlimited AI Writer (experimental)
- Unlimited AI Summarizer (experimental)
- Public API access
- 1 OAuth app
- 1 MCP server (same OAuth connection)
- Total 5.0 GB cloud storage
- Multi-channel publishing
- Agent integrations
Self-host for $0
OpenQuok charges no software fee when you run it on your own infrastructure. You still pay for servers, Supabase, and bandwidth.
Hosted cloud Docker Compose Cloud production stack Self-hosting overview
API examples FAQ
X Scheduling API,answered
Connect X, build a valid POST /public/posts payload, and publish from your app or agent.