# /nytimes/articles/search

`POST /api/nytimes/articles/search`

Price: 20 credits

Search everything The New York Times has published since 1851 — news and opinion articles, videos, interactives, slideshows, audio, recipes, The Athletic and Wirecutter pieces, paid posts and card decks. Filter by kind of item, section, publication day range and language edition, and order by relevance, newest or oldest. Each result carries headline, summary, kicker, authors, section, topic tags, lead image and publication times.

## How to use it

Search nytimes.com. Give a keyword phrase, or leave keyword empty and browse with filters and sort alone — that is how to pull the newest items in a section. Narrow with types, section, language and the start_date/end_date day range; sort takes best, newest or oldest. Each result carries uri (feed it to nytimes/articles for articles, nytimes/recipes for recipes), web_url, document_title, summary, authors, section and image. related is filled on video rows (40 of 100 sampled) and on older articles (29 of 100 sampled from 2015 against 0 of 100 from 2024), and is empty on the other kinds. The Athletic rows carry an image but no author names — The Athletic publishes none on this surface. asset_type says which kind of item the row is, so check it before feeding uri onward. language selects the newsroom edition, so an item's own language field can be finer-grained — a zh search returns zh-hans, zh-CN and zh rows. A single search reaches at most 1100 matches however large the match set says it is — narrow the date range or the section to reach further back.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `keyword` (string) — Full-text phrase to search for; leave it empty to browse by filters alone (default: ""; examples: "ukraine", "artificial intelligence")
- `count` (integer, required) — Max number of results to return (min: 1; max: 1100)
- `types` (array) — Kinds of published item to include (default: ["article","athleticarticle","audio","carddeck","interactive","legacycollection","paidpost","recipe","slideshow","video","wirecutterarticle"]; one of: "article", "athleticarticle", "audio", "carddeck", "interactive", "legacycollection", "paidpost", "recipe", "slideshow", "video", "wirecutterarticle")
- `sort` (string) — Result ordering (default: "best"; one of: "best", "newest", "oldest")
- `language` (string) — Which language edition of the newsroom to search; each holds its own set of stories (default: "en"; one of: "en", "es", "zh")
- `section` (string, nullable) — Restrict results to one New York Times section (one of: "archives", "arts", "automobiles", "blogs", "books", "briefing", "business", "climate", "crosswords", "dining", "education", "fashion", "garden", "health", "insider", "learning", "magazine", "movies", "nyregion", "nytnow", "obituaries", "opinion", "pageoneplus", "podcasts", "reader-center", "realestate", "science", "smarter-living", "sports", "style", "t-magazine", "technology", "theater", "travel", "upshot", "us", "weather", "weekinreview", "world", "your-money")
- `start_date` (string, nullable) — Only items first published on or after this day, YYYY-MM-DD (examples: "2020-01-01")
- `end_date` (string, nullable) — Only items first published on or before this day, YYYY-MM-DD (examples: "2020-01-31")

## Response

### 200 — Successful 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 — Validation Error

The request body did not validate

What to do: Check the fields against this schema. A URN with the wrong prefix is the most common cause.

- `detail` (array)
  - `loc` (array, required)
  - `msg` (string, required)
  - `type` (string, required)
  - `input` (any)
  - `ctx` (object)

### 408

The request ran past its time limit

What to do: 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

The entity was not found, or a precondition failed

What to do: 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

What to do: 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

What to do: 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

What to do: Wait at least 30 seconds, then retry.

## Response envelope

Success: Array of objects (may be empty if no results)

Error: Error may coexist with partial results if it occurs mid-execution. Check X-Error header and status code.

Every response carries these 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.