API reference

This API exposes TikTok public data (video, user, feed, comments, challenges, playlists, collections, story highlights, and more). All requests use HTTPS and return JSON with top-level code, msg, and data.

Response headers · Rate limits

Successful responses include two groups of headers: a per-minute window (how fast you can call the API) and a subscription quota (how much you can use within your current billing period). Numbers are examples; your actual values depend on plan and usage.

• x-ratelimit-* (without quota): limit and remaining calls in the current minute; reset is seconds until that minute window refreshes.
• x-ratelimit-quota-*: your plan’s total allowance for the period, what’s left, and quota-reset — seconds until the subscription quota rolls over (next reset for the billing cycle).

When a client is rate limited (per-minute throttle or plan caps), the API returns HTTP 429 with a JSON body such as:

• {"code":10429,"msg":"Too many requests. Please reduce your request rate."}
• {"code":10429,"msg":"You've reached the rate limit for your current plan. Upgrade for higher limits."}

When the subscription / period quota is exhausted, the API also returns HTTP 429 with:

• {"code":10430,"msg":"Monthly/Period quota exhausted. Please contact support or upgrade your plan."}

Response codes

Common values for the top-level code field in JSON responses:

Authentication

Every request must include your API key in HTTP headers. Requests without a valid key are rejected.

• Use HTTPS only — the base URL above is served over TLS.
• Include the header on every call, including GET requests that pass parameters in the query string.
• Rotate or revoke keys if they may have leaked; update all clients when you change keys.