Scheduling to X (Twitter) through SkedCast's API#
SkedCast's /v1 REST API schedules text, image, video, GIF, poll, and thread to X (Twitter) the same way it does every other platform: one POST https://api.skedcast.com/v1/posts call with a content caption and a targets block naming the connected accounts. You need an X account authorized over OAuth 2.0 with PKCE, connected once through the console (or minted as a self-serve connect link via POST /v1/clients/:id/connect-invites).
SkedCast is not a raw wrapper over X (Twitter)'s own developer API — it is one versioned, platform-agnostic contract that fans a single compose call out across every connected network, with the X (Twitter)-specific fields listed below folded into the same request shape.
Example: schedule a post to X (Twitter)#
{
"clientId": "…",
"content": "Shipped: the /v1 API now covers campaigns, recycle, and connect-invites.",
"targets": { "mode": "accounts", "accountIds": ["…"] },
"schedule": { "type": "at", "at": "2026-10-01T09:00:00" }
}X (Twitter) facts#
| Fact | Value |
|---|---|
| Max caption length | 280 characters |
| Media per post | up to 4 images, or one video/GIF, per post; threads chain multiple posts. |
| Native platform scheduling | No — SkedCast's managed engine holds the timer |
| SkedCast's default pacing | 100 posts/day, ~5 min apart per account (conservative anti-ban default — not X (Twitter)'s own published rate limit; see the rate-limit guide below) |
Published-post URL (permalink) | https://twitter.com/i/web/status/{id} — always derivable from the stored id. |
Reading status and results#
GET https://api.skedcast.com/v1/post-targets/:id returns the X (Twitter) target's status (scheduled, published, failed, …), plus error, statusReason, and retryAt when it's parked waiting on something — SkedCast's own pacing, a platform rate limit, or media still transcoding, each with its own machine-readable reason. Once published, externalId and permalink (see the table above) point at the live post.
- Subscribe to
target.published/target.failedwebhooks (or the legacypost.*pair) instead of polling — see [Webhooks](/developers/webhooks). - Or connect an MCP client and ask an agent to check — see [Connect an AI agent](/mcp).
FAQ
- What can I schedule to X (Twitter) through the API?
- X (Twitter) posts of type: text, image, video, GIF, poll, and thread, via one `POST https://api.skedcast.com/v1/posts` call — the same endpoint used for every other connected platform.
- Does SkedCast's X API cost anything per post?
- X bills the developer app per post through its own paid API tiers — SkedCast's `/v1` endpoint itself has no separate per-post fee beyond your SkedCast plan, but a post that includes a URL costs X's API more than a plain text post, which is why X is the one platform in this list with a nonzero `costModel` in the capabilities response.
- How do I authenticate against the X (Twitter) API endpoint?
- The same way as every `/v1` route: an API key (`Authorization: Bearer sked_live_…`) or an OAuth 2.1 bearer token, scoped to `posts.compose` to schedule and `posts.read` to read back status. See Authentication.