Scheduling to TikTok through SkedCast's API#
SkedCast's /v1 REST API schedules video to TikTok 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 TikTok account authorized via TikTok Login Kit for Web (Content Posting API), 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 TikTok's own developer API — it is one versioned, platform-agnostic contract that fans a single compose call out across every connected network, with the TikTok-specific fields listed below folded into the same request shape.
TikTok-specific fields (`variants[].overrides.tiktok`)#
| Field | Notes |
|---|---|
privacyLevel | **Required.** A privacy decision our API cannot guess — the content gate returns 422 naming the field if it's missing. |
Example: schedule a post to TikTok#
{
"clientId": "…",
"content": "Day 12 of building a scheduler in public.",
"targets": { "mode": "accounts", "accountIds": ["…"] },
"schedule": { "type": "at", "at": "2026-10-01T09:00:00" },
"variants": [
{ "platform": "tiktok", "overrides": { "tiktok": { "privacyLevel": "PUBLIC_TO_EVERYONE" } } }
]
}TikTok facts#
| Fact | Value |
|---|---|
| Max caption length | 2,200 characters |
| Media per post | one video per post — our adapter is video-only. |
| Native platform scheduling | No — SkedCast's managed engine holds the timer |
| SkedCast's default pacing | 15 posts/day, ~60 min apart per account (conservative anti-ban default — not TikTok's own published rate limit; see the rate-limit guide below) |
Published-post URL (permalink) | only known once the platform's status poll returns PUBLISH_COMPLETE with publicaly_available_post_id set — a SELF_ONLY post may never mint a public URL, and the stored external_id is TikTok's publish_id, not the video id. |
Reading status and results#
GET https://api.skedcast.com/v1/post-targets/:id returns the TikTok 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 TikTok through the API?
- TikTok posts of type: 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 TikTok 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.