no_video (4107, HTTP 422) · TranscriptFetch API error

The post has no video to transcribe: an Instagram photo post or photo carousel, a TikTok photo post (slideshow), or a page with no playable media. Permanent for this input; retrying fetches the same post.

Number4107

HTTP status422Unprocessable Entity

Familycontent4xxx · the media has no transcript to give

Example response

JSON

{
  "ok": false,
  "request_id": "req_…",
  "error": {
    "code": "no_video",
    "number": 4107,
    "message": "The post has no video to transcribe: an Instagram photo post or photo carousel, a TikTok photo post (slideshow), or a page with no playable media. Permanent for this input; retrying fetches the same post.",
    "docs": "https://transcriptfetch.com/docs/errors/no_video"
  }
}

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

No video. The post has no video to transcribe: an Instagram photo post or photo carousel, a TikTok photo post (slideshow), or a page with no playable media. Permanent for this input; retrying fetches the same post.

Shown to end users as: “This is a photo post, not a video, so there's nothing to transcribe.”

Why it happens

No video. The post has no video to transcribe: an Instagram photo post or photo carousel, a TikTok photo post (slideshow), or a page with no playable media. Permanent for this input; retrying fetches the same post.

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.
AI Fallback Transcription would not help here: there is no accessible speech to transcribe.

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