There is no separate base URL. The key prefix — unif_sk_test_ — decides the environment, so
switching is a matter of changing one environment variable.
A fixed fixture set of about 500 shops, 5,000 products and 2,000 creators
Credits
Never charged; GET /usage reports the live balance unchanged
Freshness
meta.refreshed_at is fixed to the fixture’s build date
Jobs
Complete in seconds regardless of size
Coverage
Mirrors tiktok_shop / US for every requested market
Fixture data is stable, not realistic. It is built so that assertions do not break, which
means it will not reproduce data-shaped problems — a market with weekly-only granularity, a
creator with a null agency, an ambiguous product. Test those against live data with a small
budget before you ship.
Known fixture IDs are listed in the dashboard under Settings → Sandbox, so you can write tests
against a specific shop or product rather than whatever happens to rank first.
Point CI at the sandbox and keep live keys out of it entirely. A test suite that spends credits
will eventually spend a lot of them on a branch nobody merged.
Sandbox webhooks deliver real signed requests with their own secret, so your verification code is
exercised properly. Register an endpoint with a test key and it fires on sandbox jobs and trackers
only — sandbox events never reach a live endpoint, and vice versa.
Was this page helpful?
Assistant
Responses are generated using AI and may contain mistakes.