was_live (4102, HTTP 422) · TranscriptFetch API error

The video was a live broadcast and has no caption track.

Number4102

HTTP status422Unprocessable Entity

Familycontent4xxx · the media has no transcript to give

Example response

JSON

{
  "ok": false,
  "request_id": "req_…",
  "error": {
    "code": "was_live",
    "number": 4102,
    "message": "The video was a live broadcast and has no caption track.",
    "docs": "https://transcriptfetch.com/docs/errors/was_live",
    "retry_with": {
      "mode": "auto"
    }
  }
}

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

Past live stream. The video was a live broadcast and has no caption track.

Shown to end users as: “This was a live stream and doesn't have a transcript.”

Why it happens

Past live stream. The video was a live broadcast and has no caption track.

What to do

Permanent for this input: the same request will fail the same way, so do not retry unchanged. Failed requests are never charged.
The content likely contains speech even though no caption track can be served, so AI Fallback Transcription may still produce a transcript. When it can, the response carries error.retry_with: { "mode": "auto" }; send that and it bills from 1 credit (1 credit per started 5 minutes of audio) on delivery, never on failure.

Retryable? No, this is permanent for this input. Every error response carries a request_id; include it when contacting support.