/nytimes/authors/articles

POST /api/nytimes/authors/articles

Price: 20 credits

List everything a New York Times journalist has published, newest first — articles, videos, interactives, slideshows, audio and recipes. Each item carries headline, summary, kicker, co-authors, section, topic tags, lead image and publication times.

How to use it

Page through one nytimes.com journalist's byline history, newest first. author takes the author page URL, the '/by/<slug>' path or the bare slug. Each item carries uri (feed it to nytimes/articles for articles, nytimes/recipes for recipes), web_url, document_title, summary, authors (co-authors included), section and image; asset_type says which kind of item it is. related is filled on video rows and on older articles, and empty on the other kinds. This stream has no reachability wall — count can go past a thousand where the journalist has that many bylines.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• author string required — New York Times author page URL, its /by/<slug> path, the bare slug, or a nyt://person/<uuid> identifier (examples: "https://www.nytimes.com/by/andrew-e-kramer", "by/michael-schwirtz", "adam-goldman"; minLength: 1)
• count integer required — Max number of items to return (min: 1)

Response

• @type string (default: "NytimesAsset")
• uri string required
• asset_type string required
• document_type string nullable
• web_url string nullable
• alias string nullable
• document_title string required
• seo_title string nullable
• sub_headline string nullable
• kicker string nullable
• summary string nullable
• promotional_headline string nullable
• promotional_summary string nullable
• published_at integer nullable
• updated_at integer nullable
• word_count integer nullable
• tone string nullable
• desk string nullable
• language string nullable
• section object nullable
  • @type string (default: "NytimesSectionRef")
  • uri string nullable
  • name string required
  • display_name string nullable
  • web_url string nullable
• subsection object nullable
  • @type string (default: "NytimesSectionRef")
  • uri string nullable
  • name string required
  • display_name string nullable
  • web_url string nullable
• authors array (default: [])
  • @type string (default: "NytimesPersonRef")
  • uri string nullable
  • name string required
  • alias string nullable
  • job_title string nullable
  • web_url string nullable
• byline string nullable
• image object nullable
  • @type string (default: "NytimesImage")
  • uri string nullable
  • image string required
  • width integer nullable
  • height integer nullable
  • caption string nullable
  • credit string nullable
  • alt_text string nullable
• tags array (default: [])
  • @type string (default: "NytimesTag")
  • uri string nullable
  • name string required
  • tag_type string nullable
• related array (default: [])
  • @type string (default: "NytimesArticleReference")
  • uri string required
  • asset_type string nullable
  • document_title string nullable
  • web_url string nullable
• duration_seconds integer nullable

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 New York Times journalist at this slug, or the identifier 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.