# /elpais/articles/search

`POST /api/elpais/articles/search`

Price: 5 credits

Search El Pais articles by keyword across the whole archive. Returns listing entries with headline, standfirst, publication time, byline and linked authors, kicker, thumbnail, the body word count El Pais publishes and its subscription badge.

## How to use it

Keyword search over El Pais. keyword is the only filter the site offers: there is no date range, no section facet and no sort option. Set edition to en to search english.elpais.com instead of the Spanish site; the two editions have separate newsrooms and share no articles. Each entry carries id, article_title, description, web_url, published_at, language, publication, content_type, section, kicker, byline, authors, dateline, has_subscription_badge, has_video, word_count and image. word_count is El Pais's own count of the body words and is absent on the older archive templates; has_subscription_badge is the subscription icon El Pais prints on modern Spanish cards, never on English or archive cards, so false there means unmarked rather than open and elpais/articles holds the authoritative tier. Feed id or web_url into elpais/articles for the body. Results are ordered by relevance mixed with recency, not strictly by date. No result total is reported: the figure El Pais prints above its results is a match count it will not fully hand out, measured 5431 claimed against 3624 articles actually reachable for 'gasoducto medgaz', so ask for the count you want and read how many came back. A keyword nothing matches is not an error: the call returns an empty list.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `keyword` (string, required) — Search phrase (examples: "trump", "inteligencia artificial"; minLength: 1)
- `count` (integer, required) — Max number of articles to return (min: 1)
- `edition` (string) — Which title to search: es for elpais.com, en for english.elpais.com, cd for the business daily Cinco Dias (default: "es"; one of: "es", "en", "cd")

## Response

### 200 — Successful Response

- `@type` (string) (default: "ElpaisArticleCard")
- `id` (string, required)
- `article_title` (string, required)
- `description` (string, nullable)
- `web_url` (string, required)
- `published_at` (integer, nullable)
- `language` (string, required)
- `publication` (string, required)
- `content_type` (string, required)
- `section` (string, required)
- `kicker` (string, nullable)
- `kicker_url` (string, nullable)
- `byline` (string, nullable)
- `authors` (array) (default: [])
  - `@type` (string) (default: "ElpaisAuthorRef")
  - `name` (string, required)
  - `alias` (string, nullable)
  - `profile_url` (string, nullable)
  - `bio` (string, nullable)
  - `image` (string, nullable)
- `dateline` (string, nullable)
- `has_subscription_badge` (boolean) (default: false)
- `has_video` (boolean) (default: false)
- `word_count` (integer, nullable)
- `image` (string, nullable)

## Errors

### 422 — Validation Error

Blank keyword or count out of range

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.