no_captions · 4103 · HTTP 422

Example response

{
  "ok": false,
  "request_id": "req_…",
  "error": {
    "code": "no_captions",
    "number": 4103,
    "message": "No caption track (manual or auto-generated) is available.",
    "docs": "https://transcriptfetch.com/docs/errors/no_captions",
    "retry_with": {
      "mode": "audio"
    }
  }
}

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: 4xxx · the media has no transcript to give.

What it means

No captions. No caption track (manual or auto-generated) is available.

Shown to end users as: “Subtitles aren't available for this video.”

Why it happens

• No captions. No caption track (manual or auto-generated) is available.

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 transcription of the audio may still produce a transcript. When it can, the response carries `error.retry_with: { "mode": "audio" }`; send that and it bills from 1 credit (2 credits per minute of audio) on delivery, never on failure.

Related errors

• audio_ineligible (3004), an audio retry on an input transcription cannot serve
• insufficient_credits (2001), an audio retry the balance cannot cover