TikTok Backstage API: connect read-only reporting tools
Use the owner’s managed API key to read this network’s agency/team directory and imported reporting data, understand endpoints and diagnose responses.
This guide describes the available features. Your account role, assigned modules, signed contract and network plan determine which controls you can use. Reading a guide does not change your access.
Start here
- Owners: open TikTok Backstage API and copy the managed key into the secure configuration for your reporting integration.
- Use the Health working example first to confirm authentication and view the latest available month.
- Choose the Network summary example or another endpoint, specify a reporting month when needed and send a GET request with Authorization: Bearer or X-API-Key.
- Use Network directory to populate an external site with a JSON array of every agency/team account. Reporting endpoints return data, meta and any pagination. Follow the page’s OpenAPI 3.1 JSON reference when building an integration.
- Managers: review endpoint documentation here; the network owner must manage integrations that need the network-wide key.
Access and key management
The API reads the network’s agency/team account directory and network-owned data imported manually or through Backstage Automation. Its key fixes the network scope; callers do not choose another customer by supplying a user ID. The current API is read only and does not upload reports or change creator records.
Only the owner can view or replace the key because it exposes network-wide data. Managers can read endpoint documentation without receiving the key. The site generates one managed active key, stores it encrypted at rest, and shows creation and last-used timestamps to the owner.
Copy key and the owner’s Working examples contain the actual credential. Store these in secure server or integration settings rather than public pages, screenshots or shared documents. Replace key immediately invalidates the previous key; update every integration using it after replacement.
Make your first request
The page’s generated examples use the correct site address and URL-encode current account values. Copy the Health example and include the key in either Authorization: Bearer YOUR_KEY or X-API-Key. Use GET for the listed endpoints.
Month values use YYYY-MM. If omitted where supported, reporting months default to the newest imported month, which may not be the current calendar month. Available months helps discover actual reporting coverage. Date/time values use ISO 8601.
Choose the data endpoint
Health returns connectivity and the latest month; Available months lists Creator Data and Rookie months. Network summary gives totals, efficiency metrics, changes and top performers. Network history returns a monthly series between from and to.
Network directory uses ?path=network%2Fdirectory and returns every agency/team account as a JSON array, including accounts without imported reports. Entries contain id, name, type, status, parent_agency_id and parent_agency_name. There is no pagination or reporting month. All statuses are included by default; use status=active for active accounts, or type=agency or type=team to filter. Parent fields are null for agencies and standalone teams. Fetch from the external site’s server with the API key stored in server configuration.
Agencies and Teams return ranked rollups. Their detail endpoints add the selected agency/team and paginated creators. Creators returns paginated rankings and filters, while Creator detail returns a profile, latest statistics and full history. Rookies exposes Rookie Graduation ranking data.
Today’s Diamonds returns near-real-time totals and collector status. Daily snapshots contains actual daily captures; Daily forecasts contains forecast series, so keep the two separate in charts. Imports exposes manual/automatic import status and freshness. The on-page endpoint table and OpenAPI document provide precise paths and supported parameters.
Handle success, limits and errors
Network directory returns a JSON array directly, or [] when no accounts match. Other successful responses contain data and meta; lists may also include pagination. Read the pagination values instead of assuming the first page contains every creator. Examples use page 1 and limit 50 for applicable lists.
The default rate limit is 120 requests per minute; the actual key card displays its limit. Response headers report the limit, remaining allowance and reset. Cache reporting results appropriately and wait for reset if you exhaust the allowance.
Errors contain an error object with code and message plus an HTTP status. Check the key after an authentication failure, month and path parameters after a validation error, and import freshness when a valid result looks old. Percentage change can be null when the previous value was zero and the current value is non-zero; null is not a zero-percent change.
Frequently asked questions
Can a manager copy the key?
No. The key exposes network-wide data and is visible only to the main owner.
Does replacing a key keep the old one active temporarily?
No. The old key stops working immediately. Update all consumers after replacement.
Why is a current request returning an older month?
The default is the newest imported month, not necessarily the current calendar month. Check Available months and Imports.
Can this API edit creator information?
No. The documented v1 endpoints provide read-only GET access to reporting data.
Still stuck? Note the page name, the step you tried and the exact message shown. Managers and sub-users should contact their network owner; owners should contact their platform administrator. Never include passwords, webhook URLs, recovery links or private identity documents in a general support message.