Start here
invalid_input · 3005 · HTTP 422
The input is not something we can transcribe: it is not a YouTube, TikTok or Instagram video (a profile, playlist or LIVE room link, an unsupported site), nor a direct media file URL.
Number3005
HTTP status422Unprocessable Entity
Familyinput3xxx · this input cannot be served
Example response
JSON
{ "ok": false, "request_id": "req_…", "error": { "code": "invalid_input", "number": 3005, "message": "The input is not something we can transcribe: it is not a YouTube, TikTok or Instagram video (a profile, playlist or LIVE room link, an unsupported site), nor a direct media file URL.", "docs": "https://transcriptfetch.com/docs/errors/invalid_input" } }
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
Invalid input. The input is not something we can transcribe: it is not a YouTube, TikTok or Instagram video (a profile, playlist or LIVE room link, an unsupported site), nor a direct media file URL.
Shown to end users as: “That link isn't one we can transcribe. Use a YouTube, TikTok or Instagram video link, or a direct link to a media file.”
Why it happens
- Invalid input. The input is not something we can transcribe: it is not a YouTube, TikTok or Instagram video (a profile, playlist or LIVE room link, an unsupported site), nor a direct media file URL.
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: the content itself is not accessible to fetch.
Retryable? No, this is permanent for this input. Every error response carries a
request_id; include it when contacting support.