/nytimes/authors

POST /api/nytimes/authors

Price: 1 credit

Get a New York Times journalist's profile by author page URL or slug: display name, job title, the full biography as plain text and as HTML with its links, portrait photograph, canonical author page URL and how many published items carry their byline.

How to use it

Fetch one nytimes.com journalist profile. author takes the author page URL, the '/by/<slug>' path or the bare slug ('andrew-e-kramer'). Returns uri, name, job_title, bio, bio_html (the biography with its original links intact), image and published_item_count. Use nytimes/authors/articles with the same value to page through what they have written. A URL that points at an article or a section is rejected rather than returned as a person.

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)

Response

• @type string (default: "NytimesAuthor")
• uri string required
• name string required
• alias string nullable
• job_title string nullable
• bio string nullable
• bio_html string nullable
• web_url 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
• published_item_count integer nullable
• created_at integer nullable
• updated_at 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.