Does TikTok have an API?

How do you get access to post a video?

For a creator-facing app that sends finished content to TikTok, choose between posting directly and handing the final edit back to the creator.

A Direct Post integration, from permission to result

1. Register the app and request the right permission

   For Direct Post, add Content Posting API, enable Direct Post and obtain approval for video.publish. The target creator must also authorize that scope. Store the user's access token securely; an app key is not a substitute for their authorization.

2. Ask the creator what will be sent

   Fetch current creator information. Show the account and available privacy choices, then let the person preview the content, choose its audience and confirm the required disclosures and consent. Do not silently choose public visibility or treat a stored boolean as proof of consent.

3. Transfer the content and keep its identifier

   Initialize the Direct Post request. Upload the file or use a URL from a verified domain or URL prefix, as required for that transfer method. Keep the returned publish_id; an accepted request is not a finished post.

4. Check the original request's outcome

   Use Get Post Status with the same publish_id. Reconcile a failed or uncertain attempt before starting another. Confirm the actual result and audience rather than announcing public success after an upload.

Follow TikTok's request sequence and creator-facing sharing requirements. This is implementation guidance, not a claim that we registered your app, obtained approval or executed a live TikTok request.

Is the API free, and what needs approval?

Do not budget from a blanket “free TikTok API” claim. The official setup guides above describe product access; they do not establish one price or unlimited allowance across the whole catalogue.

TikTok product access

Read the selected API's requirements and developer terms. For Direct Post, separate app scope approval, user authorization and the audit needed to lift private-viewing restrictions.

Your implementation

Allow for secure token storage, hosting, content transfer, a review interface and handling failed or unfinished requests. Getting an app approved does not build those pieces.

A managed service

A service subscription pays for that service's workflow and supported features. For Postdom, check current plans; that price is not a TikTok API fee or a shortcut to unrestricted access.

For research, check eligibility and project approval first. Its client-token setup is not interchangeable with a creator's publishing authorization.

Which limits and permissions matter before you submit?

Check the connected creator—not a generic maximum

Use the current creator-info response for available privacy choices, disabled interactions and max_video_post_duration_sec. Do not copy an example response's duration or assume every account can use every privacy option.

For dimensions and transfer requirements, use the TikTok video requirements guide. A Postdom upload ceiling is not a universal Direct Post allowance.

Keep caption limits tied to their field

For video Direct Post, post_info.title has a documented maximum of 2,200 UTF-16 runes. This is the caption/title field on /v2/post/publish/video/init/, not a limit for every TikTok API.

Official field reference · Caption fact verified 2026-08-31. This documented native limit is not enforced by Postdom's caption-length check. Use the caption guide before sending a long caption.

API access is not permission to do anything

Display access is not an unrestricted scrape of other creators. Research access is not a general commercial-data entitlement. For posting, the person must see the content and make the required choices; a background job cannot manufacture their consent.

TikTok's Direct Post intended-use rules exclude apps that copy arbitrary content from other platforms and utilities limited to uploading to accounts you or your team manage. Check that fit before building an internal uploader and expecting audit approval.

Public-post audit approval is not a guarantee that a particular video will be accepted or distributed. Keep the original request identifier and inspect the actual outcome.

Should you use TikTok directly or a managed publishing API?

Build directly when you need the native product's controls and can own its approval, authorization, review interface and failure handling. Use a managed layer when its narrower publishing workflow fits the job and you want your backend or agent to work through that interface.

Postdom publishes supplied finished videos to 9 destinations: TikTok, Instagram Reels, YouTube Shorts, LinkedIn, Facebook Reels, X, Snapchat Spotlight, Threads and Bluesky. It does not generate the video or expose TikTok's login, research, ads or messaging products.

For a concrete example, use an accepted existing video URL or already-stored media handle, review the request, submit once and follow the same post ID. The linked example does not upload a new local file. A later publish_at time does not switch a private video to public.

The linked workflow was exercised with a released-package loopback fixture, not a real creator account or a provider publication. Private helper defaults are not evidence of TikTok audit approval.

What else should you know before building?