Skip to content

TikTok Scheduling API

The TikTok Scheduling API lets a product, agency workflow, automation, or AI system queue a TikTok video for an exact future date and time without maintaining its own publishing queue.

Schedule a TikTok video with POST /v1/posts
POST {{API_BASE_URL}}/v1/posts
x-access-key: YOUR_API_KEY
Content-Type: application/json

{
  "content": "A short example update.",
  "platforms": [
    {
      "platform": "tiktok",
      "accountId": "tt_321",
      "platformSpecificData": {
        "privacyLevel": "PUBLIC_TO_EVERYONE",
        "disableComment": false,
        "disableDuet": false,
        "disableStitch": false
      }
    }
  ],
  "mediaItems": [
    {
      "type": "video",
      "url": "https://cdn.example.com/tutorial.mp4"
    }
  ],
  "scheduledFor": "2026-09-10T09:00:00",
  "timezone": "America/Chicago"
}

// Illustrative response — HTTP 202
{
  "success": true,
  "status": "scheduled",
  "postId": "post_xyz789",
  "scheduledFor": "2026-09-10T14:00:00.000Z",
  "platforms": [
    {
      "platform": "tiktok",
      "success": true
    }
  ]
}
Illustrative request
Example line 1

POST {{API_BASE_URL}}/v1/posts

Illustrative request
Example line 2

x-access-key: YOUR_API_KEY

Illustrative request
Example line 3

Content-Type: application/json

You send the caption, video, connected account, and TikTok settings in one request, optionally with an IANA timezone, and the service resolves the delivery time and publishes when it arrives.

What the TikTok Scheduling API does and who it is for

This page is for developers and operators who need to schedule a TikTok video by exact date, time, and timezone from inside their own product. Instead of building a queue, a scheduler, and TikTok publishing infrastructure yourself, you create the post once through the scheduling endpoint and let the service hold it until the scheduled moment. The same connected accounts can also be used for immediate posting, analytics, comments, and messaging, so scheduling fits into a broader social workflow rather than standing alone.

Add scheduling in three steps

Integration follows three steps. First, obtain API access for your application. Second, connect the TikTok account once and integrate the endpoint into the stack your application already uses, whether that is a developer stack with typed SDKs and REST calls, a no-code workflow tool, or an AI agent using tool calling or MCP. Third, use the same endpoint for scheduling, and the same connected accounts for the other capabilities you need, instead of building and maintaining a separate integration for each platform.

Field map: scheduledFor, timezone, accountId, platformSpecificData, and mediaItems

Scheduling uses POST {{API_BASE_URL}}/v1/posts. The request carries the caption in content, the video in mediaItems, and one entry per target platform in platforms. For TikTok, that entry sets platform to tiktok, identifies the connected account with accountId, and holds TikTok-only settings in platformSpecificData. The scheduledFor field takes an ISO 8601 datetime, and timezone takes an IANA timezone name when you want the time interpreted as local time. See the field map table and the worked request example titled Schedule a TikTok video with POST /v1/posts for the exact fields. The captured contract example covers video; photo and photo carousel formats are named as publishing formats in the source, but no fields for those formats were captured, so this page does not invent fields for them.

Worked example and the 202 scheduled response

A successful scheduling request returns HTTP 202 with success set to true, status set to scheduled, a postId you can use to track the queued post, and a scheduledFor value in UTC. The platforms array in the response confirms each target, with platform and success for TikTok. Treat the 202 response as queued, not published: the video goes live when the scheduled time arrives, so your product should show the post as scheduled until then.

Timezone resolution: local time to UTC, and the UTC default

Timezone-aware scheduling separates the time you enter from the time the service stores. You pass scheduledFor as local time, for example 2026-09-10T09:00:00, together with timezone set to America/Chicago. The service resolves the offset for that date and returns the corresponding UTC publishing time, in this case 2026-09-10T14:00:00.000Z. Other IANA timezones such as Europe/London and Asia/Kolkata work the same way. If you omit timezone, UTC is used, so a time you meant as local time will be treated as UTC — always send timezone explicitly when the user picks a local time.

Creator-info check for privacyLevel, disableComment, disableDuet, and disableStitch

Before you schedule, check what the connected account actually allows. Fetch /v1/tiktok/creator-info and use the returned options to build the privacy and interaction controls in your product, rather than hardcoding a fixed list. Pass the chosen privacyLevel inside platformSpecificData, and set disableComment, disableDuet, and disableStitch only where the creator-info response shows the account supports them. If a setting is not available for that creator, do not send it as if it were; surface only the options the creator-info response returns. See the example titled Check TikTok Creator Info before scheduling.

Managing queued posts: list, edit, reschedule, cancel

A queued post is not locked in. Before publication, you can list queued TikTok posts to see what is coming, revise the caption or media, change TikTok-specific settings, and move delivery to a new date or time. You can also cancel a queued post before it goes live. Build your content calendar around those four operations — list, update, reschedule, cancel — and always confirm the post is still in scheduled state before attempting a revision, because that path applies only prior to publication.

Cross-post scheduling and adjacent posting and analytics capabilities

To plan ahead, create each post in a series with its own scheduledFor time, spreading delivery across days or weeks without running your own scheduler. For cross-posting, add separate entries to platforms for TikTok, Instagram, YouTube, and other supported networks in the same request, each with its own accountId and platform-specific settings, so compatible video content can go out on a single schedule. Scheduling is also one part of a wider workflow: the TikTok Posting API covers immediate publishing of videos, photos, and photo carousels, and the TikTok Analytics API brings performance data back into your product or reporting.

POST /v1/posts request fields for TikTok scheduling
FieldLocationType / examplePurpose
contentRequest bodystring — "Quick tutorial! #coding #devtips"Caption for the video
platforms[].platformRequest bodystring — "tiktok"Target platform for this entry
platforms[].accountIdRequest bodystring — "tt_321"Connected TikTok account identifier
platforms[].platformSpecificData.privacyLevelRequest bodystring — "PUBLIC_TO_EVERYONE"TikTok privacy level; available values depend on the connected creator
platforms[].platformSpecificData.disableCommentRequest bodyboolean — falseDisable comments on the video
platforms[].platformSpecificData.disableDuetRequest bodyboolean — falseDisable duets on the video
platforms[].platformSpecificData.disableStitchRequest bodyboolean — falseDisable stitches on the video
mediaItems[].typeRequest bodystring — "video"Media type
mediaItems[].urlRequest bodystring — "https://cdn.example.com/tutorial.mp4"Hosted video URL
scheduledForRequest bodyISO 8601 datetime — "2026-09-10T09:00:00"Local scheduled date and time
timezoneRequest bodyIANA timezone — "America/Chicago"Timezone used to interpret scheduledFor; if omitted, UTC is used

Captured source contract for POST {{API_BASE_URL}}/v1/posts; requiredness beyond the example is not specified in the captured source. Captured example covers video only.

POST /v1/posts response fields (HTTP 202)
FieldLocationType / examplePurpose
successResponse bodyboolean — trueWhether the request succeeded
statusResponse bodystring — "scheduled"Queue state of the post
postIdResponse bodystring — "post_xyz789"Identifier of the queued post
scheduledForResponse bodyUTC datetime — "2026-09-10T14:00:00.000Z"Resolved UTC publishing time
platforms[].platformResponse bodystring — "tiktok"Target platform confirmation
platforms[].successResponse bodyboolean — trueWhether that platform target was accepted

Captured source contract; example shown with HTTP 202.

Timezone resolution: local scheduledFor to UTC
InputResolved outputWhat to check
scheduledFor 2026-09-10T09:00:00 with timezone America/ChicagoscheduledFor 2026-09-10T14:00:00.000Z (UTC)Confirm the returned UTC time matches the local time the user picked
scheduledFor with no timezoneTreated as UTCWarn the user if they intended local time but omitted timezone
scheduledFor with Europe/London or Asia/KolkataUTC time resolved for that timezone and dateUse an IANA timezone name, not a fixed offset

Worked example from the captured source; offsets vary by date and timezone.

Failure and validation checks
SituationExpected behaviorCheck before proceeding
timezone omittedUTC is used for scheduledForAsk the user to confirm UTC, or collect an IANA timezone
privacyLevel or interaction setting not allowed for the creatorSetting must fit what the connected account permitsFetch /v1/tiktok/creator-info and offer only returned options
Edit or reschedule attempted after publicationRevision applies only before publicationList queued posts and confirm the post is still scheduled first
Cancel attempted after publicationCancel applies before publicationConfirm scheduled state before cancelling

Derived from captured source FAQ and lifecycle descriptions; no error catalogue was supplied in the source.

Frequently asked questions

How do I schedule a TikTok video through the API?

Use POST {{API_BASE_URL}}/v1/posts with content, a video in mediaItems, a connected TikTok accountId in platforms, and a scheduledFor ISO 8601 datetime. Add timezone as an IANA timezone such as America/Chicago when you want local-time scheduling. The request is validated and queued, and the response returns status scheduled with a postId and a resolved UTC scheduledFor.

Can I control TikTok privacy settings on a scheduled video?

Pass privacyLevel inside platformSpecificData for the TikTok target. Do not hardcode the list of levels. Fetch /v1/tiktok/creator-info for the connected account first and present only the privacy options returned for that account.

Can I control comments, duets, and stitches when scheduling?

Yes. Set disableComment, disableDuet, and disableStitch inside platformSpecificData. Before sending them, confirm the connected creator permits each choice by reviewing the creator-info response, and omit any option that account does not support.

Can I edit and reschedule a TikTok video after scheduling it?

During the period before publication, a queued item can be revised: change its caption, swap or update media, adjust target platforms or TikTok settings, or move delivery to a different date or time. After it has gone live, that pre-publication revision path is no longer available.

How does timezone-aware TikTok scheduling work?

Pass scheduledFor as local time together with an IANA timezone such as America/Chicago, Europe/London, or Asia/Kolkata. The timezone offset for that date is resolved and the response returns the corresponding UTC time. If no timezone is provided, UTC is used.

Do I need my own TikTok developer app?

No separate TikTok developer app is required for this workflow. The connected-account OAuth, token refresh, and publishing infrastructure are handled by the scheduling service, so your product connects an account and calls the scheduling endpoint.

Can I schedule TikTok and Instagram Reels or YouTube Shorts together?

Yes. Add TikTok, Instagram, YouTube, and other supported networks as separate entries in platforms in the same scheduled request, with platform-specific settings where needed. Each platform entry keeps its own accountId and platformSpecificData.

Check TikTok Creator Info before scheduling
{{API_BASE_URL}}/v1/tiktok/creator-info

// Illustrative check before scheduling: fetch the connected account's
// available privacy and interaction options, then use only returned
// values for privacyLevel, disableComment, disableDuet, and disableStitch.
// The captured source specifies this path without a method or response
// schema, so no method or response body is shown here.