POST /api/npr/articles/transcripts
Price: 5 credits
Get the published transcript of an NPR audio story or podcast episode as ordered, speaker-labelled segments: speaker name, role (host, byline, guest), spoken text and sound cues such as music or archived recordings.
Fetch the transcript of one NPR audio story by its id (nx-s1-…, g-s1-… or a legacy numeric id) or full npr.org URL. Returns the transcript split into ordered segments with position, speaker, role and text; sound cues like '(SOUNDBITE OF MUSIC)' come back with is_sound_cue true. Only audio stories have transcripts — npr/articles reports has_transcript for a given id, and transcripts are usually published some hours after the audio itself.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)article string required — NPR story id or the full story URL (examples: "nx-s1-5920362", "https://www.npr.org/2026/08/05/nx-s1-5920362/abdul-el-sayed-michigans-democratic-senate-nominee-discusses-the-race"; minLength: 1)@type string (default: "NprTranscriptSegment")position integer requiredspeaker string nullablerole string nullabletext string requiredis_sound_cue boolean (default: false)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 transcript for this story — the id is text-only, has no transcript published yet, or does not exist 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.