transcriptfetchGitHubDashboard
API reference

podcast_feed_not_found · 3003 · HTTP 422

The podcast link could not be matched to an episode in a public RSS feed. Spotify-exclusive shows have no feed; a deleted episode has no metadata.

Example response

{
  "ok": false,
  "request_id": "req_…",
  "error": {
    "code": "podcast_feed_not_found",
    "number": 3003,
    "message": "The podcast link could not be matched to an episode in a public RSS feed. Spotify-exclusive shows have no feed; a deleted episode has no metadata.",
    "docs": "https://transcriptfetch.com/docs/errors/podcast_feed_not_found"
  }
}

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: 3xxx · this input cannot be served.

What it means

The podcast link could not be matched to an episode in a public RSS feed. Spotify-exclusive shows have no feed; a deleted episode has no metadata.

Why it happens

  • A Spotify-exclusive show: it has no public RSS feed, so there is no audio to fetch. `error.details.reason` is `show_not_found`.
  • The episode was deleted or made private after the link was shared (`metadata_unavailable`, `episode_not_found`).
  • Several episodes matched about equally (`ambiguous_match`); `error.details.candidates` lists them with their audio URLs.

What to do

  • Paste the episode's Apple Podcasts link, or the show's RSS feed URL, instead of the Spotify link.
  • For an ambiguous match, send one of the `details.candidates[].audioUrl` values directly as the `video` input.
Retryable? No, not with the same link. The feed_unreadable case is different: it answers upstream_unavailable (502) and is worth retrying. Every error response carries a request_id; include it when contacting support.

Related errors

Next →All error codes
podcast_feed_not_found (3003, HTTP 422) · TranscriptFetch API error