API reference
unknown · 9002 · HTTP 503
The fetch failed for an unspecified reason.
Example response
{ "ok": false, "request_id": "req_…", "error": { "code": "unknown", "number": 9002, "message": "The fetch failed for an unspecified reason.", "docs": "https://transcriptfetch.com/docs/errors/unknown" } }
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: 9xxx · our fault.
What it means
Error. The fetch failed for an unspecified reason.
Shown to end users as: “Couldn't fetch that transcript. Please check the link and try again.”
Why it happens
- Error. The fetch failed for an unspecified reason.
- Transient by definition: the same request may succeed a moment later.
What to do
- Transient failure. Wait the seconds in the Retry-After header when present, otherwise back off about 30 seconds, then retry the same request.
- Back off exponentially on repeats. Failed requests are never charged.
Retryable? Yes, after the Retry-After window (about 30 seconds when the header is absent), with exponential backoff on repeats. Every error response carries a
request_id; include it when contacting support.Related errors
- upstream_unavailable (5101), the service itself, rather than the fetch, was unreachable
- rate_limited (2101), your own key's limit answers 429, never 503