transcriptfetchGitHubDashboard
API reference

parse_error · 5005 · HTTP 503

Upstream returned a response that couldn't be parsed.

Example response

{
  "ok": false,
  "request_id": "req_…",
  "error": {
    "code": "parse_error",
    "number": 5005,
    "message": "Upstream returned a response that couldn't be parsed.",
    "docs": "https://transcriptfetch.com/docs/errors/parse_error"
  }
}

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: 5xxx · transient, retry with backoff.

What it means

Parse error. Upstream returned a response that couldn't be parsed.

Shown to end users as: “We got an unexpected response fetching this video. Please try again.”

Why it happens

  • Parse error. Upstream returned a response that couldn't be parsed.
  • 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

Next →All error codes
parse_error (5005, HTTP 503) · TranscriptFetch API error