Developer Docs
Rate limits & Credits
Per-key sliding-window limits and the prepaid credit currency.
Two independent controls govern usage: a rate limit (how fast) and credits (how much). They fail differently, so handle them differently.
Rate limits
Each key gets a per-second sliding window sized by your plan. Over the limit returns 429 rate_limit_exceeded; every response carries the window state in X-RateLimit-Limit / X-RateLimit-Remaining / X-RateLimit-Reset. Back off and retry — the limit is transient.
| Plan | Requests / 1s | Requests / min | Requests / day | API keys |
|---|---|---|---|---|
| Free | 1 | 60 | 5,000 | 1 |
| Starter | 5 | 300 | 15,000 | 3 |
| Pro | 20 | 1,200 | 100,000 | 10 |
| Scale | 60 | 3,600 | 400,000 | 25 |
| Agency | 150 | 9,000 | 1,200,000 | unlimited |
These are the figures the pricing page publishes and this API enforces — per minute is per second × 60, and per day is the hard daily quota (429 daily_quota_exceeded). A negotiated plan may raise them.
Credits
Every billable request spends prepaid credits by SKU. Running out returns 402 insufficient_credits — retrying will not help; top up. Check your balance and per-key spend at GET /v1/usage, and your allotment at GET /v1/entitlements.
| Operation | Credits | When it applies |
|---|---|---|
cached-read | 1 | A read served from our store — the common case for every dataset, and the unit your published requests/day limit counts. |
room-minute | 1 | Each completed minute a realtime subscription owns a LIVE room. |
comments-collect | 500 | An on-demand video-comment page collected from TikTok (R4.3). |
live-refresh | 1,250 | You asked us to refresh a creator's LIVE state from TikTok now. |
profile-resolve | 1,250 | An on-demand profile fetch from TikTok for an account we hold nothing fresh for (R4.1). |
export | 2,500 | A bulk dataset export job. |
follow-list-resolve | 4,000 | An on-demand follower/following list walk — many signed, rate-limited pages (R4.5). |
A store hit is always cached-read; only requests that touch TikTok cost more.