TikTok Events API Rate Limit: 1,000 Requests/s (2026)
Last checked · sources listed at the foot of this page
TikTok rate-limits each endpoint separately, against a one-minute sliding window. The Direct Post endpoint allows 6 requests per minute per user access token, Query Creator Info allows 20, Get Post Status allows 30, and the user and video read endpoints (/v2/user/info/, /v2/video/query/, /v2/video/list/) allow 600 each. Going over returns HTTP 429 with the error code rate_limit_exceeded. The Events API is a separate system on a separate host: 1,000 requests per second, the same at every application level, answering code 40100 when throttled.
What is the rate limit for each TikTok API endpoint?
The limits are set and enforced per endpoint, not as one shared budget. Exhausting Direct Post does not slow down Get Post Status, and vice versa.
| Endpoint | Limit | What it means in practice |
|---|---|---|
| Direct Post (/v2/post/publish/video/init/) | 6 requests / minute per user access token | The binding limit for anyone publishing to several accounts. It is per token, so per connected account — ten accounts do not share six requests, they each have six. |
| Query Creator Info | 20 requests / minute per user access token | Called before every post, because the posting UI must show the creator’s real privacy options. It is why a publish flow costs at least two calls, not one. |
| Get Post Status | 30 requests / minute per user access token | Polling. Thirty per minute sounds generous until you poll ten accounts every two seconds — that is 300. |
| /v2/user/info/ | 600 requests / minute | Profile reads. |
| /v2/video/query/ | 600 requests / minute | Metrics for specific videos. |
| /v2/video/list/ | 600 requests / minute | Paginated listing of a creator’s videos. |
How is the window calculated, and what happens when you exceed it?
The calculation uses a one-minute sliding window, not a fixed clock minute. A burst of six posts at 10:00:59 does not reset at 10:01:00 — it keeps counting until 10:01:59.
Over the threshold, the API answers HTTP 429 with the error code rate_limit_exceeded. TikTok states that limits can be raised on request through their support page, reviewed case by case.
The practical consequence for a multi-account publisher: a retry on a 429 must back off, not repeat. An immediate retry extends the window it is trying to escape.
What is the TikTok Events API rate limit, in requests per second?
One thousand per second, and it is the same number for every developer application — this is the one place where TikTok does not make you apply for more.
This is a different API from every endpoint above, and that is the part that catches people out. The Content Posting endpoints live on developers.tiktok.com and are counted per minute, per user access token. The Events API is part of the Marketing API on business-api.tiktok.com, and is counted in QPS, QPM and QPD against your developer application. Two hosts, two systems, two error codes: the Marketing API answers "code": 40100 where the developer API answers HTTP 429.
Your application also sits at one of four global levels — Basic 10 QPS, Advanced 20, Premium 30, Ultimate 50, and every app starts at Basic. The Events endpoints are explicitly exempt from that ladder: TikTok states you do not need to apply for a rate limit level change for Events API, because the rate limit is the same for all levels. So the 1,000 QPS below is what a brand-new app gets on day one.
| Endpoint | Limit | What it means in practice |
|---|---|---|
| Web Events (/pixel/track/) and /pixel/batch/ | 1,000 / second · 600,000 / minute · 86,400,000 / day | Browser and server-side web conversions. The daily figure is exactly 1,000 × 86,400, so the per-second limit is the only one you can realistically hit. |
| App Events (/app/track/) and /app/batch/ | 1,000 / second · 600,000 / minute · 86,400,000 / day | Mobile app conversions. |
| Offline Events (/offline/track/) and /offline/batch/ | 1,000 / second · 600,000 / minute · 86,400,000 / day | In-store and CRM conversions sent after the fact. |
| /event/track/ | 1,000 / second · 600,000 / minute · 86,400,000 / day | The Events API 2.0 endpoint. |
| Streaming API | 10,000 / second at Basic, up to 50,000 at Ultimate | The one events-side limit that does follow the level ladder. |
Why does publishing to ten accounts not take ten times longer?
Because every limit above is scoped to a user access token, and one token is one connected account. Ten accounts are ten independent buckets of six posts per minute.
What does serialise is your own infrastructure: one video file uploaded ten times is ten transfers. The limit that bites first is almost never TikTok’s, it is bandwidth.
Frequently asked
- Are TikTok API rate limits per app or per user?
- The Content Posting endpoints are documented per user access token — so per connected account. TikTok does not publish a separate app-wide ceiling for these endpoints, and states that limits are set and enforced separately for each API.
- What error does TikTok return when a rate limit is exceeded?
- HTTP status 429, with the error code rate_limit_exceeded in the response body.
- Can TikTok API rate limits be increased?
- Yes. TikTok’s documentation states that higher limits can be requested through their support page, and that each request is reviewed.
- What is the TikTok Events API rate limit per second?
- 1,000 requests per second, 600,000 per minute and 86,400,000 per day, for /event/track/, Web Events, App Events and Offline Events alike. TikTok applies the same figure at all four application levels and states that you do not need to apply for an increase for the Events API.
- Is the Events API rate limit the same as the Content Posting API rate limit?
- No, and they are not even the same system. Content Posting is documented on developers.tiktok.com, counted per minute against a user access token, and answers HTTP 429 with rate_limit_exceeded. The Events API belongs to the Marketing API on business-api.tiktok.com, is counted in requests per second, minute and day against your developer application, and answers code 40100.
- How many TikTok videos can I post per minute through the API?
- Six per connected account, since the Direct Post endpoint allows 6 requests per minute per user access token. Across ten connected accounts that is sixty, because each account carries its own limit.
Sources
- TikTok for Developers — Rate Limits on API Requests — read on .
- TikTok API for Business — Rate limits (Marketing API, incl. Events API) — read on .
- TikTok for Developers — Content Posting API, Direct Post — read on .
- TikTok for Developers — Query Creator Info — read on .
These figures come from another company’s documentation, which can change without notice and which nothing here verifies automatically. That is why every source carries the date it was read. Sources on this page are re-read every quarter.
How this page was made: drafted with AI assistance from the sources listed on this page, read on .