# /elpais/topics/articles

`POST /api/elpais/topics/articles`

Price: 5 credits

List El Pais articles filed under one topic tag, newest first, walking the topic archive page by page. Returns 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

Read the chronological archive of an El Pais topic. topic is the slug used in /noticias/ URLs, which elpais/articles returns in tags[].alias and every listing entry returns in kicker_url; a full topic URL is accepted too, an 'en/' prefix switches to the English edition, where the same surface lives under /news/, and a 'cd/' prefix to Cinco Dias. Many section names also exist as topics (economia, deportes, cultura, opinion), so this is the way to read deep into a section; a few do not (internacional has no topic page) and then the request returns 412. 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 and the badge are printed on modern Spanish cards only, and elpais/articles holds the authoritative subscription tier. Feed id or web_url into elpais/articles for the body. How far back a topic's archive reaches depends on how much El Pais has filed under it, so ask for the count you want and read how many rows came back.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `topic` (string, required) — El Pais topic slug, or the URL of the topic page; prefix with en/ for the English edition or cd/ for Cinco Dias (examples: "isabel-diaz-ayuso", "https://elpais.com/noticias/crisis-migratoria/", "en/donald-trump", "cd/banca"; minLength: 1)
- `count` (integer, required) — Max number of articles to return (min: 1; max: 10000)

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

Not an El Pais topic slug or topic page URL

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

No El Pais topic page for this slug

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.