/npr/authors/articles

POST /api/npr/authors/articles

Price: 20 credits

List the stories published by one NPR journalist, host or contributor, newest first: headline, teaser, publication date, section, program, lead image with caption and credit, and the direct mp3 and duration when the story was broadcast.

How to use it

List what one NPR person has published. Pass the people id from npr/articles authors[].id or a https://www.npr.org/people/{id}/{slug} URL, plus count. Stories come back newest first with id (usable in npr/articles), article_title, description, web_url, published_date as YYYY-MM-DD, section, show, image and audio_url with duration in seconds.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• author string required — NPR people id or the full npr.org people URL (examples: "2100593", "https://www.npr.org/people/g-s1-128730/maham-javaid"; minLength: 1)
• count integer required — Max number of stories to return (min: 1)

Response

• @type string (default: "NprStoryCard")
• id string required
• article_title string required
• description string nullable
• web_url string nullable
• published_date string nullable
• section string nullable
• section_url string nullable
• show string nullable
• show_url string nullable
• image string nullable
• image_caption string nullable
• image_credit string nullable
• audio_id string nullable
• audio_url string nullable
• duration integer nullable
• has_audio 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 NPR person with this id — the id is unknown or points at another kind of page 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.