# /politico/articles/search

`POST /api/politico/articles/search`

Price: 20 credits

Search the POLITICO archive across every edition — Europe, UK, France, Germany and the cross-published US desk. Combine a full-text query with policy section, tag, author and post-type filters and a publication date range. Each match carries the headline, an opening excerpt, the publication timestamp, the credited authors, the policy sections and the tag list.

## How to use it

Search POLITICO stories and newsletter issues. count says how many to return; every other field is a filter. keyword is the full-text query, sections takes policy section slugs, tag_ids and author_ids take the identifiers published by politico/facets, post_types restricts to article, newsletter, sponsored-content or pro-free, and published_after/published_before take unix timestamps that line up with published_at. Without a keyword the newest stories come first, and with one the closest text matches come first; to walk back through the archive move published_before earlier. Each item has id, article_title, web_url, excerpt, published_at, post_types, image, authors[], sections[] and tags[] — pass id to politico/articles for the full body, except where web_url ends in a #{id} anchor, which marks a live-blog entry and must be passed as the whole web_url. At most 1000 stories are reachable for one set of filters, however many match; to go deeper move published_before earlier and search again.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `keyword` (string, nullable) — Full-text query matched against headline and body (examples: "tariffs")
- `sections` (array, nullable) — Only stories filed under these policy section slugs (examples: ["technology"])
- `tag_ids` (array, nullable) — Only stories carrying these tag identifiers (examples: ["81127"])
- `author_ids` (array, nullable) — Only stories credited to these author identifiers
- `post_types` (array, nullable) — Restrict to these kinds of POLITICO post (one of: "article", "newsletter", "sponsored-content", "pro-free"; examples: ["newsletter"])
- `published_after` (integer, nullable) — Only stories published at or after this unix timestamp (min: 0)
- `published_before` (integer, nullable) — Only stories published before this unix timestamp (min: 0)
- `count` (integer, required) — Max number of stories to return (min: 1)

## Response

### 200 — Successful Response

- `@type` (string) (default: "PoliticoArticleCard")
- `id` (string, required)
- `article_title` (string, required)
- `web_url` (string, required)
- `excerpt` (string, nullable)
- `published_at` (integer, nullable)
- `post_types` (array) (default: [])
- `image` (string, nullable)
- `image_small` (string, nullable)
- `image_caption` (string, nullable)
- `authors` (array) (default: [])
  - `@type` (string) (default: "PoliticoAuthor")
  - `id` (string, nullable)
  - `name` (string, required)
  - `alias` (string, nullable)
  - `profile_url` (string, nullable)
- `sections` (array) (default: [])
  - `@type` (string) (default: "PoliticoSection")
  - `alias` (string, required)
  - `name` (string, nullable)
- `tags` (array) (default: [])
  - `@type` (string) (default: "PoliticoTag")
  - `id` (string, required)
  - `name` (string, required)

## 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.