unauthorized (1101, HTTP 401) · TranscriptFetch API error

Example response

{
  "ok": false,
  "request_id": "req_…",
  "error": {
    "code": "unauthorized",
    "number": 1101,
    "message": "Missing or invalid API key.",
    "docs": "https://transcriptfetch.com/docs/errors/unauthorized"
  }
}

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: 1xxx · the request itself.

What it means

Missing or invalid API key.

Why it happens

The Authorization header is missing or not in the form `Bearer tf_live_...`.
The API key was revoked in the dashboard, or has a typo.
The key was pasted with surrounding whitespace or quotes.

What to do

Send the key as `Authorization: Bearer tf_live_...` on every request.
Check the key's status at transcriptfetch.com/app/keys; revoked keys never work again, so create a fresh one if needed.
Verify the key with a free call to GET /api/v2/me; it returns your credit balance when the key is valid.

Retryable? No, retrying with the same key will keep failing. Fix the credential first. Every error response carries a request_id; include it when contacting support.

Related errors

invalid_request (1001), the request was readable but malformed, rather than unauthenticated
insufficient_credits (2001), the key is valid but the account cannot pay for the call

Next →All error codes