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 through a connect link that POST /v1/clients/{id}/connect-invites creates.
The request is one contract for every connected platform. The fields that are specific to Threads are listed below.
Example: schedule a post to Threads#
{
"clientId": "00000000-0000-4000-8000-000000000001",
"content": "Hot take: your posting cadence matters less than your consistency.",
"targets": { "mode": "accounts", "accountIds": ["00000000-0000-4000-8000-000000000002"] },
"schedule": { "type": "at", "scheduledAt": "2030-01-15T15:00:00Z" }
}Threads facts#
| Fact | Value |
|---|---|
| Max caption length | 500 characters |
| Media per post | up to 20 media items per post. |
| Native platform scheduling | No. SkedCast holds the timer and publishes at the scheduled time. |
| SkedCast's default pacing | 200 / day, with at least 5 min between posts, per account. This is SkedCast's per-account pacing, not Threads's own published limit. See the rate limits reference. |
Published-post URL (permalink) | Available once the target is published. SkedCast reads it from Threads when you fetch the target, the same as Instagram. |
Reading status and results#
GET https://api.skedcast.com/v1/post-targets/{id} returns the Threads target's status (for example scheduled, on_hold, published, failed or missed). Once the post is published, externalId and permalink point at the live post (see the table above).
on_hold:holdReasonsays why (pacing, a platform limit, media still processing, your plan, or a channel that needs reconnecting) andretryAtsays when the next try is.missed: the scheduled time passed while the post waited.outcomeReasonsays why; reschedule it.failed:failureReasonsays why. When the post may already be live,outcomeReasonisdelivery_unconfirmed: check the account, because a retry is refused.requiredActionsays what you must do (reconnect_channel,change_plan,contact_support,reschedule,retryorcheck_platform), or isnullwhen nothing is needed.- Instead of polling, subscribe to the
target.publishedandtarget.failedwebhooks (one per destination;post.publishedandpost.failedreport the whole post). See the webhooks reference below. - Or connect an MCP client and ask an agent to check. See the MCP hub below.