TikTok API Posting Limit: 6 Requests a Minute, an Unpublished Daily Cap, and Why Your Video Is Private
- Official: "Each user access_token is limited to 6 requests per minute."
- A daily post cap exists — it appears as an error condition — but the documentation never states the number.
- The line that explains everything: "All content posted by unaudited clients will be restricted to private viewing mode."
- If a video posted by a third-party tool gets zero views and cannot be found, open it while logged out. Private is not the same as suppressed.
You connected a tool, published three videos, and they got nothing. Not low views — nothing. Nobody can find them. So you searched, and every answer said the same word: shadowban.
Before you spend three months on remediation, read one sentence from TikTok's own developer documentation.
"All content posted by unaudited clients will be restricted to private viewing mode"
That is verbatim from the TikTok Content Posting API reference. There is a matching error condition named unaudited_client_can_only_post_to_private_accounts.
Here is what it means in plain terms. Applications that publish to TikTok go through an audit. Until an application passes that audit, anything it posts is private — visible to the account owner and nobody else. That is not a penalty applied to your account. It is a deliberate safety default applied to the application.
So the video with zero views may be working exactly as specified. It was never shown to anyone, because the tool that posted it has not been audited.
A shadowban is a hypothesis. "Unaudited clients post privately" is a documented default. When one of your two explanations is written down by the platform, start there.
The two-minute check: open the video's link in a private browsing window, or from a second account. If it will not load, it is private. If it loads fine, you have a different problem — and now you know which one you do not have.
The rate limit that is published: 6 requests per minute
The documentation is exact: "Each user access_token is limited to 6 requests per minute."
Note what is being counted — requests, not posts. Publishing one video involves several calls (initialise, upload, check status, and often repeated status polls). So six requests a minute is considerably tighter than "six videos a minute", and a tool that polls aggressively while waiting for a video to process can spend the whole allowance on one upload.
Practical reading: bulk publishing to TikTok is inherently paced. If a tool advertises rapid batch upload, either it is queuing internally and telling you it is instant, or it is generating errors you will meet later.
The daily cap that exists but has no number
Now the odd part, and the most useful thing on this page.
The documentation lists an error meaning the daily post cap from the API has been reached for the current user — and never says what the cap is. Anywhere.
That is a specific and recognisable shape. It is not "the limit does not exist" — an error code proves it does. It is "the limit exists, it will be enforced, and the number is not being published."
Which means the only rational response is to stop looking for the figure and change what you do with failures instead:
- Log the error code, not the feeling. "It failed" is unusable. The daily-cap error is distinguishable from a permission error and from a rejected upload, and the three need different responses.
- Count what got through before it stopped. Across several occurrences you will derive your own working ceiling. It is the only number that will ever apply to you.
- Do not tune to the edge. An unpublished limit can move without notice. A plan built to sit just under an invisible line breaks silently the day the line moves.
Three failures that look identical and are not
| What you see | What it probably is | What actually fixes it |
|---|---|---|
| Posts fine, zero views, cannot be found by others | Unaudited client → private viewing mode | Nothing on your account. Check the app's audit status; verify by opening the link logged out |
| Errors during a burst, works again if you slow down | 6 requests per minute | Pace the batch; check whether your tool is polling status aggressively |
| Worked all day, then stopped, resumes tomorrow | Daily post cap (number unpublished) | Wait. Record how many got through so you learn your own ceiling |
Note that none of these three is a shadowban, and all three get reported as one. If you want the actual diagnostic path for suppressed reach, that is a separate question — we worked through it in How Many Times Can You Post on TikTok a Day? and Does Posting Time Matter on TikTok?.
Why the private-by-default rule exists at all
It helps to understand the logic, because it tells you whether the situation will ever change.
A publishing API is, from the platform's side, a way for unknown third-party software to put content in front of its users. The audit is the gate: until an application has been reviewed, TikTok lets it publish — so developers can build and test — but not to an audience. Nothing about your account enters the decision, which is why every remediation aimed at your account fails to help.
The practical implications follow directly. It is per application, not per user, so switching accounts changes nothing while switching tools might change everything. It is binary, so there is no partial state to observe your way out of. And it is not something you can influence — the audit is a relationship between TikTok and the developer, and the only lever you hold is choosing a tool that has already been through it.
What this means when you are choosing a tool
Two questions worth asking any tool that offers TikTok publishing, before you pay:
- Is your TikTok application audited? If the answer is unclear, assume your posts land private. This one question is worth more than a feature list.
- How do you handle the daily cap? A tool that surfaces the specific error is telling you the truth. A tool that shows "failed, retry" is going to cost you a lot of guessing — and, worse, may retry into a cap and burn capacity that valid posts needed.
There is also the structural alternative, which is worth stating plainly because it is the reason this whole class of problem exists. All of the above follows from publishing through TikTok's developer interface. NoobClaw publishes a different way: it runs on your own machine and signs into your own TikTok account in a fingerprint-isolated browser, posting through your own session rather than an API token — so application audit status, API rate limits and API daily caps are not part of the picture. The honest exchange is that it needs your machine running and your login valid, which a cloud service does not. Different constraints. But if your videos have been quietly private for a month, knowing that a different route exists is worth more than another shadowban checklist.
FAQ
How many videos can I post to TikTok through the API per day?
TikTok does not publish the figure. The documentation includes an error for the daily post cap being reached, which proves a limit exists, but never states its value. The workable approach is to record how many posts succeed before the error appears and treat that as your own ceiling — while leaving margin, since an unpublished number can change without notice.
Why does my TikTok posted by a third-party tool have zero views?
Most likely it is private rather than suppressed. TikTok's documentation states that content posted by unaudited applications is restricted to private viewing mode. Open the video's link in a logged-out browser: if it will not load, it is private, and no amount of account remediation will change that — the audit status of the app is what matters.
What does "6 requests per minute" actually allow?
Fewer videos than it sounds like. Publishing a single video takes several API calls including status polling, so the allowance is consumed faster than one request per video. Batch uploads to TikTok are inherently paced, and a tool that polls upload status aggressively can exhaust the minute on one item.