Someone connects TikTok, schedules a video, watches it publish successfully — and cannot find it on their profile. Nothing is broken. TikTok is doing exactly what it says it does.
The unaudited state
Until an app passes TikTok’s audit for the Content Posting API, everything it posts is forced to private visibility. The upload is real, the video is on the account, and only the account holder can see it. This is deliberate: it lets developers test end to end without letting an unreviewed app broadcast to the public.
An unaudited app cannot make a post public no matter what visibility your tool asks for. If a product implies otherwise, it has not read the same documentation the reviewers use.
What the audit actually looks at
- That the person publishing gave informed consent — they saw the caption, the video and the target account before it went out
- That your app shows TikTok’s own disclosure requirements, including the branded-content and disclosure toggles
- That the domain serving your video files is verified in the developer portal, if you upload by URL
- That a real, working demo exists — reviewers use the product, they do not read a description of it
The domain check catches most people
For URL-based uploads, TikTok fetches the file from your server rather than accepting a stream from your app. The domain it fetches from has to be verified beforehand, and an unverified domain fails the publish with an error that never mentions domains.
How long it takes
Weeks, not days, and a rejection usually means one specific thing is missing rather than the whole submission being wrong. The useful posture is to treat it as paperwork with a checklist, not as a judgement — and to keep publishing to the networks that do not require it while you wait.
