/npr/podcasts/episodes

POST /api/npr/podcasts/episodes

Price: 20 credits

List the episodes published in an NPR podcast feed, newest first: title, show notes, publish time, duration, direct mp3 url and file size, cover art, episode type and the npr.org story page the episode belongs to.

How to use it

List episodes of one NPR podcast. Pass the show id (510318 for Up First, g-s1-111189 for All Songs Considered) or a https://www.npr.org/podcasts/{id}/{slug} URL, plus count. Episodes come back newest first with episode_title, description (plain text) and description_html (show notes with chapter timestamps), published_at and duration in seconds, audio_url (direct mp3), audio_bytes and article_id — feed that id to npr/articles or npr/articles/transcripts. NPR feeds carry a rolling window of recent episodes rather than the full back catalogue.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• show string required — NPR show id or the full npr.org podcast URL (examples: "510318", "g-s1-111189", "https://www.npr.org/podcasts/510318/up-first"; minLength: 1)
• count integer required — Max number of episodes to return (min: 1)

Response

• @type string (default: "NprPodcastEpisode")
• id string required
• episode_title string required
• feed_title string nullable
• description string nullable
• description_html string nullable
• published_at integer nullable
• duration integer nullable
• audio_url string nullable
• audio_bytes integer nullable
• audio_type string nullable
• web_url string nullable
• article_id string nullable
• image string nullable
• episode_type string nullable
• is_explicit boolean (default: false)
• is_blocked boolean (default: false)

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — No podcast with this id — the id is unknown or belongs to a topic or section rather than a podcast Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.