Scheduling to Threads through SkedCast's API#
SkedCast's /v1 REST API schedules text, image, carousel, and video to Threads 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 a Threads professional account (same Meta login as Instagram), 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 Threads's own developer API — it is one versioned, platform-agnostic contract that fans a single compose call out across every connected network, with the Threads-specific fields listed below folded into the same request shape.
Example: schedule a post to Threads#
{
"clientId": "…",
"content": "Hot take: your posting cadence matters less than your consistency.",
"targets": { "mode": "accounts", "accountIds": ["…"] },
"schedule": { "type": "at", "at": "2026-10-01T09:00:00" }
}Threads facts#
| Fact | Value |
|---|---|
| Max caption length | 500 characters |
| Media per post | up to 20 media items per post (our adapter's ceiling; Threads' own limit is higher). |
| Native platform scheduling | No — SkedCast's managed engine holds the timer |
| SkedCast's default pacing | 200 posts/day, ~5 min apart per account (conservative anti-ban default — not Threads's own published rate limit; see the rate-limit guide below) |
Published-post URL (permalink) | read live from the platform (fields=permalink) once the target reaches published, the same as Instagram. |
Reading status and results#
GET https://api.skedcast.com/v1/post-targets/:id returns the Threads 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 Threads through the API?
- Threads posts of type: text, image, carousel, and video, via one `POST https://api.skedcast.com/v1/posts` call — the same endpoint used for every other connected platform.
- How do I authenticate against the Threads 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.