Short answer: an unaudited TikTok Content Posting API client can only post
private (SELF_ONLY) videos, for up to five users in a 24-hour window. After
audit, posts are public, but there is a per-creator daily cap (typically around
15 posts) and a per-client cap on active creators sized from your audit
application. Source: TikTok's
content sharing guidelines,
checked 17 September 2026.
If you are trying to post to TikTok programmatically, the limits below are the ones that will decide whether it works. They come from TikTok's own developer documentation. Check them there before you build anything — this page is current to September 2026 and TikTok changes it.
The limits at a glance
| Limit | Unaudited client | Audited client |
|---|---|---|
| Post visibility | SELF_ONLY (private) only |
As the creator chooses |
| Users who can post | Up to 5 per 24 hours | Client cap from your audit application |
| Posts per creator | Not the binding limit | Varies; typically around 15 per day |
| Branding on content | Not allowed | Not allowed |
The limit that stops most people
An unaudited API client can only post as SELF_ONLY.
Your posts go up private. Not unlisted, not limited reach — invisible to everyone but the account holder, who has to open the app and change the visibility by hand, per post.
If your reason for automating was to not open the app, this is the end of the road until you pass audit.
The other unaudited limit
Five users per 24 hours. An unaudited client can allow up to five accounts to post in a rolling day. So even setting the private-posts problem aside, an unaudited integration cannot run a fleet.
After audit
Passing audit lifts both of those, and introduces different ones.
- Around 15 posts per day per creator account. The exact ceiling varies by creator.
- A client-level cap on active creators per 24 hours, sized from the usage estimates you gave in your audit application. You do not pick this number afterwards; you declared it beforehand.
- No superimposed branding. Apps must not add a brand name, logo, watermark, link or promotional text to content shared through the API.
- Audit takes days to weeks, with a rejection-and-resubmit loop. Common rejections: the demo video does not show the full posting flow, creator settings are not respected, there is no visible confirmation screen before posting, policy pages are unreachable, or the requested scopes are broader than the demo justifies.
There is also a spam rejection — spam_risk_too_many_posts — with no published
number attached to it, so you will find that ceiling by hitting it.
Two scopes, and they are not the same
video.uploadputs a video in the account's drafts. A human still opens the app and posts it.video.publishposts directly.
A lot of tools that say "posts to TikTok" hold video.upload. Worth checking
which one you are buying.
When the API is the right answer
Genuinely, often. If you run a handful of established business accounts, publish a normal volume, and want scheduling and analytics in one place, the official API is cheaper, simpler and more reliable than driving a phone. It is also the sanctioned route, which counts for something.
When it is not
The audit is sized to the use case you declared. A client audited for a single-brand scheduler is not a client audited to run fifty creator accounts, and the per-client creator cap is the mechanism that enforces that.
The other ceiling is Instagram-shaped and worth knowing if you cross-post: Meta's publishing limit is a rolling 24-hour count derived from an account's own reach. A freshly connected account has almost no budget. New accounts are exactly the case where API posting is most constrained, and exactly the case most people automating are actually in.
What operators report about reach
This part is anecdote, and we would rather label it than dress it up.
Operators posting from desktop automation regularly report videos getting no distribution at all, while the same clip posted by hand from a phone performs normally. The usual explanation offered is that uploads are distinguishable at the upload layer and seeded differently.
Two honest caveats. First, most of those reports concern web and desktop automation, not the official API — and the same operators generally rate the official API above web automation. Second, there is no published controlled comparison of API posting versus in-app posting reach. The direction is widely reported; the size of the effect is not established, and anyone quoting you a percentage made it up.
The alternative
The other way to post to TikTok is the way an account holder does: from the app, on a phone. That is what Farmero does — it drives iPhones you own over USB, posts to your own accounts on a schedule, and confirms afterwards that the post went live.
No API scopes, no audit, no SELF_ONLY, no per-client creator cap. The
tradeoffs are real and worth knowing before you commit: you need the phones, you
need a Mac, and you are automating a UI that TikTok redesigns on its own
timetable.
If you are weighing tools, see the Repurpose.io comparison and how many TikTok accounts fit on one iPhone.
How Farmero posts · Start free
FAQ
Can an unaudited TikTok API app post publicly?
No. TikTok's guidelines say unaudited clients can only post in SELF_ONLY
viewership, and the getting-started docs say content from unaudited clients is
restricted to private viewing.
How many posts per day does the TikTok API allow?
TikTok says the per-creator limit varies and is typically around 15 posts per day per creator account via Direct Post.
How many accounts can an unaudited client post for?
Up to five users in a 24-hour window, per TikTok's content sharing guidelines.
Does Farmero use the TikTok API?
No. Farmero posts through the TikTok app on iPhones you own, so API audit and caps do not apply. Automating the app may breach TikTok's terms, and nobody can promise an account will never be restricted.
Limits above from TikTok's Content Posting API documentation and content sharing guidelines, checked 17 September 2026. TikTok is the authority on its own API; verify before building.