Start here
drm_protected · 3007 · HTTP 422
The source is DRM-protected and cannot be downloaded. Spotify and Apple Podcasts pages fall here; podcast links are not supported.
Number3007
HTTP status422Unprocessable Entity
Familyinput3xxx · this input cannot be served
Example response
JSON
{ "ok": false, "request_id": "req_…", "error": { "code": "drm_protected", "number": 3007, "message": "The source is DRM-protected and cannot be downloaded. Spotify and Apple Podcasts pages fall here; podcast links are not supported.", "docs": "https://transcriptfetch.com/docs/errors/drm_protected" } }
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
DRM-protected. The source is DRM-protected and cannot be downloaded. Spotify and Apple Podcasts pages fall here; podcast links are not supported.
Shown to end users as: “This content is DRM-protected, so it can't be transcribed.”
Why it happens
- DRM-protected. The source is DRM-protected and cannot be downloaded. Spotify and Apple Podcasts pages fall here; podcast links are not supported.
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.