What happens between pressing publish and the post going live
A publish through TikTok’s Content Posting API is not one request. It is a short conversation, and most of the elapsed time is spent waiting for the other side. Knowing the shape of it explains both why a tool shows several states and why “done” arrives later than you expect.
Three steps, then waiting
Initialise. The app tells TikTok what is coming — the total size, how it will be split, and the settings for the post — and gets back an upload address plus an identifier for this publish. Nothing about the video has moved yet, but the post is now described.
Upload. The file goes to that address in chunks. This is the only part whose duration depends on you: the size of the export and the speed of the connection carrying it.
Poll. The app asks, repeatedly, what became of that identifier. TikTok transcodes the video and puts it through review; only when that resolves is there a post, and only then is there a link.
Polling is a separate kind of request from publishing, with its own allowance in the rate limits — which is why a tool publishing to many accounts has to leave room for it rather than spend the whole budget on uploads.
The states worth showing you
A spinner covers all of this with one word and throws away every difference that matters. These are the states an EasyDrop job moves through, and what each one actually means.
- pending
- Accepted and waiting its turn. Nothing has been sent to TikTok yet, which is why this is the only state where cancelling costs nothing.
- queued
- Picked up by the processor and cleared to go, within the pace this account can take.
- uploading
- Bytes are moving. The file goes up in chunks against an upload URL TikTok issued for this job specifically.
- processing
- TikTok has the whole file and is doing its own work — transcoding and review. The wait here is not ours and cannot be hurried.
- published
- TikTok reported the post as live, and a permalink exists. Reached only when the platform says so.
- failed
- Something ended it — a rejected file, an expired authorisation, a moderation decision. The reason is kept on the job so a retry is an informed choice.
Why the distinction earns its keep
Publishing the same clip to six accounts produces six jobs that do not travel together. One is still queued behind the pacing, one is uploading, three are with TikTok, one failed on an authorisation that lapsed last week. Collapsing that into a single progress bar hides the only fact you can act on — which account needs you.
It also makes retrying honest. A failure that happened before the upload can be retried immediately; one that came back from review will fail again unless the video changes. Keeping the reason on the job is what turns a retry button into a decision rather than a gamble.
What EasyDrop shows
Every video-and-account pair is its own job with its own state and, when it ends badly, its own reason. Published means TikTok said published, and the row carries the permalink. Retry acts on that one job, not the batch.
Common questions
How long does a TikTok API publish take?
The upload is as fast as the file and the connection allow; the wait afterwards belongs to TikTok, which transcodes and reviews the video before it appears. Minutes is normal for the whole sequence, and a large file on a slow link stretches the upload rather than the review.
Why does the app say processing when the upload finished?
Because the file arriving and the post existing are two different events. Once TikTok has all the bytes it does its own work, and until that finishes there is no post and no link to give you.
Can a publish fail after the upload succeeded?
Yes. The file can be complete and still be rejected in review, or the account's authorisation can have lapsed between queueing and publishing. That is why the status has to come from polling the platform rather than from whether the upload request returned cleanly.
Why is the video uploaded in chunks?
It is how the API takes large files: the app declares the total size and a chunk size when it initialises the upload, then sends the parts. Chunking also means a stalled transfer fails on one part rather than losing the whole file.