reference tiktok sandbox rate limit gotcha 20260715T171805

---

name: TikTok Display API: sandbox rate limit is far tighter than documented production tier description: TikTok's sandbox app hits 429s well below the documented ~600 req/min production ceiling; resume/retry messaging should not quote the production figure. type: reference

---

TikTok's Display API documents a production rate limit around 600 req/min, but an app still in sandbox mode (not yet audited to production) hits 429s at a far lower real ceiling. Confirmed live during CreatorTrack's TikTok backfill (2026-07-15): a resume attempt immediately after one rate-limit hit was rate-limited again, requiring a 60+ second cooldown loop rather than the one-minute wait the ~600/min figure would imply.

Why: a backfill/resume script that quotes the production limit in its retry guidance sends an operator (or unattended retry logic) into a false "the checkpoint/resume machinery must be broken" conclusion when in fact the sandbox tier itself just needs more patience.

How to apply: when writing or troubleshooting rate-limit handling for any TikTok integration still running under a sandbox/unaudited app, do not size backoff or resume-wait messaging off TikTok's published production limits; budget for a materially tighter live ceiling and confirm the real limit empirically.

[auto-memory session 60d132de-4659-485c-8044-427af0ccce7f, confidence 0.70, mode staged]