API reference

rate_limited — HTTP 429

Per-key rate limit exceeded. Retry after backoff.

Example response

{
  "ok": false,
  "request_id": "req_...",
  "error": {
    "code": "rate_limited",
    "message": "Per-key rate limit exceeded. Retry after backoff."
  }
}

Why it happens

  • Too many requests per minute on one API key.
  • A burst of concurrent calls (e.g. a parallel loop without throttling).

How to fix it

  • Wait the number of seconds in the `Retry-After` response header, then retry.
  • Add exponential backoff, or spread bulk work through the batch endpoint (up to 50 videos in one request = one rate-limit unit).
Retryable? Yes — after the Retry-After window. Back off exponentially on repeats. Every error response carries a request_id — include it when contacting support.
Next →All error codes
rate_limited (HTTP 429) · TranscriptFetch API error