rate_limited (2101, HTTP 429) · TranscriptFetch API error

Your account or key has reached a request or work-capacity limit. Wait Retry-After seconds, then continue.

Number2101

HTTP status429Too Many Requests

Familyaccount2xxx · your account or plan

Example response

JSON

{
  "ok": false,
  "request_id": "req_…",
  "error": {
    "code": "rate_limited",
    "number": 2101,
    "message": "Your account or key has reached a request or work-capacity limit. Wait Retry-After seconds, then continue.",
    "docs": "https://transcriptfetch.com/docs/errors/rate_limited"
  }
}

Every failure carries error.code, error.number, error.message and error.docs, plus at most one of retry_with (the request change that would succeed), details (structured specifics) or issues (validation problems).

What it means

Your account or key has reached a request or work-capacity limit. Wait Retry-After seconds, then continue.

Why it happens

Too many requests across your account, or an individual key's lower limit.
A burst of concurrent calls (a parallel loop without throttling).

What to do

Wait the number of seconds in the Retry-After response header, then retry.
Add exponential backoff, or spread bulk work through the batch endpoint (many 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.