insufficient_credits (2001, HTTP 402) · TranscriptFetch API error

Example response

{
  "ok": false,
  "request_id": "req_…",
  "error": {
    "code": "insufficient_credits",
    "number": 2001,
    "message": "Not enough credits for the request. Nothing was charged; retry once credits are available.",
    "docs": "https://transcriptfetch.com/docs/errors/insufficient_credits"
  }
}

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). Family: 2xxx · your account or plan.

What it means

Not enough credits for the request. Nothing was charged; retry once credits are available.

Why it happens

The account's credit balance is 0: the 100 free credits a month are spent, or a paid plan's monthly allowance is used up.
A batch request needs more credits than the balance holds.
An audio transcription would cost more than the remaining balance (it bills by length).

What to do

Check your balance with GET /api/v2/me (free) or in the dashboard.
Subscribe to a plan or top up credits at transcriptfetch.com/app/plans; top-ups are priced at your plan's per-credit rate ($10 per 1,000 without a plan).

Retryable? Yes, once credits are available. Failed requests are never charged. Every error response carries a request_id; include it when contacting support.

Related errors

unauthorized (1101), if the key itself is wrong, fix that before topping up
batch_too_large (2002), a batch can also be refused for its size, before credits are checked

Next →All error codes