TikTok Content Publishing API: What It Can and Can’t Do

What the API can do

The TikTok workflow connects accounts through official flows, including the QR login API for products that link accounts inside their own interface, and supports video and photo carousel publishing. Posts can be published immediately or scheduled up to 7 days ahead. After submission, status tracking reports queued, processing, published, or failed states, and analytics return followers, likes, video counts, and top videos for the connected account. All of this works from a backend using the same content endpoint used for the other four platforms.

What the API cannot do

TikTok does not accept text-only posts, so a request without media is rejected. The API is for publishing content to a connected account; it does not read or post comments, send direct messages, or perform actions like following on your behalf. Content that violates platform rules is rejected by TikTok, and the failure shows up in status tracking as a failed post. Media must also match the format rules below, or the request fails validation before it leaves your workflow. There is no webhook for publish completion either, so integrations poll status endpoints after submitting.

Media requirements that actually matter

Getting media right avoids most failed publishes. The recommended profile is vertical MP4 with H.264, because that is what short-form feeds are built for. The table below lists the limits that come up most often in integrations.

QR login and account access

QR login lets a user connect a TikTok account by scanning a code and confirming in the TikTok app, without a standard browser redirect. It is available on Professional and Maximum plans. Your backend requests a QR session, your interface shows the code, and your system polls until the user confirms, the session expires, or the code is used. Polling should stop on any non-OK response and always stop after 5 minutes. This flow is useful for embedded products that want account linking inside their own experience, and the session lifecycle is explicit: new, scanned, confirmed, expired, and utilised states map directly to UI states.

Scheduling and status

TikTok posts follow the same 7-day scheduling window as every other platform in the workflow. Scheduled content is queued and processed server-side, so the queue keeps running without a browser open. Once a post is submitted, single or batch status endpoints tell you whether it is queued, processing, published, or failed. For status checks, include the media type for TikTok so the API returns the correct public post URL behavior for video or photo workflows.

A practical publish sequence

A working TikTok integration looks like this. List connected accounts and pick the TikTok account. Prepare the media: one video URL for a video post, or up to 35 image URLs for a photo carousel, and add TikTok-specific settings such as the cover frame timestamp. Submit through the content endpoint and keep the publish ID. Poll the status endpoint with the media type included until the post is published or failed. Then read analytics for followers, likes, video counts, and top videos when the campaign wraps. The same sequence works for the other four platforms, with their own settings where they exist.

TikTok API for Business: what the developer portal gives you

The TikTok for Developers portal is the route to the Content Posting API, and it sets a gate that is easy to miss: an unaudited app can only publish to private accounts. Until TikTok reviews the app, posts go out with a privacy level of "Only Me", which means nobody sees the content even though the request succeeds. The portal also decides which privacy options an account can offer, and the API exposes those options per creator, so an integration has to read them before it can publish. When the list comes back empty, the account cannot post through the API at that moment, and no amount of retrying fixes it.

• An unaudited app can publish only with privacy set to "Only Me".
• The portal controls the app review that unlocks public privacy levels.
• The API returns the privacy options available to each creator; an empty list means no publishing right now.
• A per-account daily ceiling applies on top of the app review state.

Working with failures

Failures on TikTok are usually media problems, and most of them can be caught before the request is sent. Confirm the media URL is reachable by the backend, check that file size and duration are within limits, and never mix photos and videos in one payload. When a post does fail, the status endpoint reports it, and failed publishes do not count toward the monthly upload quota. That last detail matters for planning: your quota reflects successful publishes, so a rejected video costs a retry, not an upload credit.

Planning TikTok content at volume

TikTok rewards consistency, which is another way of saying the workflow has to survive a full content calendar. Batch scheduling up to 7 days ahead covers a weekly cadence: prepare Monday through Sunday on Friday, queue the posts, and let the server process them in order. The quota model supports this planning because only successful publishes count toward the monthly limit, so a rejected video costs a retry rather than an upload credit. For agencies that run many client accounts, the QR login API keeps onboarding inside the product, and account groups organize each client’s TikTok accounts for the operators. Status tracking then turns publishing from a hope into a checklist: queued, processing, published, or failed per post, with the media type included so the correct public post URL resolves. When the week ends, analytics return followers, likes, video counts, and top videos per account, which feeds the next week’s plan. The feedback loop is concrete: the formats that produced the top videos get scheduled again, and the ones that failed validation get fixed at the media preparation stage instead of at publish time.

Standardizing media preparation

Media preparation belongs in the same loop. Keep the MP4 with H.264 vertical profile as the house standard, check duration against the 3-second to 10-minute window, and validate that every media URL is reachable by the backend before it enters the queue. Photo carousels add a second content type without new code, capped at 35 images per post. Building those checks into the publishing step is what keeps a high-volume calendar from turning into a high-volume retry queue, and it is the same checklist a developer would want to see in a runbook rather than a surprise at publish time.