# /corriere/articles/search

`POST /api/corriere/articles/search`

Price: 1 credit

Search the Corriere della Sera archive by keyword, optionally narrowed to one section. Returns listing entries with headline, standfirst, first publication and last update times, byline, section path, topic tags, images with their photo credits and the paywall tier, newest first.

## How to use it

Keyword search over the Corriere della Sera archive, which reaches back to at least 2010 and covers the national site, the supplements and the local editions in one index. Results are ordered newest first, not by relevance. Pass section to narrow to one part of the paper, spelled exactly as Corriere does ('Esteri', 'Politica', 'Sport', 'Economia/finanza', 'Roma/Cronaca'); a top-level value such as 'Sport' also returns its subsections. Each entry carries id (the content id), article_title, short_headline, description, web_url, published_at, updated_at, section and sections, label, byline, tags, images with credit, edition and is_premium. Feed web_url into corriere/articles for the body text. A keyword with no matches returns an empty list; an unknown section is rejected.

## 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: "meloni", "intelligenza artificiale", "ornitorinco"; minLength: 1)
- `count` (integer, required) — Max number of articles to return (min: 1; max: 20000)
- `section` (string, nullable) — Restrict the search to one Corriere section path, exactly as Corriere spells it (case sensitive). A top-level value also matches its subsections (examples: "Esteri", "Politica", "Economia/finanza", "Roma/Cronaca")

## Response

### 200 — Successful Response

- `@type` (string) (default: "CorriereArticleCard")
- `id` (string, required)
- `article_title` (string, required)
- `short_headline` (string, nullable)
- `description` (string, nullable)
- `web_url` (string, required)
- `published_at` (integer, nullable)
- `updated_at` (integer, nullable)
- `section` (string, nullable)
- `sections` (array) (default: [])
- `label` (string, nullable)
- `content_type` (string, nullable)
- `provider` (string, nullable)
- `edition` (string, nullable)
- `byline` (string, nullable)
- `tags` (array) (default: [])
- `sub_types` (array) (default: [])
- `sub_section` (string, nullable)
- `paywall_category` (integer, nullable)
- `is_premium` (boolean) (default: false)
- `image` (string, nullable)
- `images` (array) (default: [])
  - `@type` (string) (default: "CorriereImage")
  - `image` (string, required)
  - `width` (integer, nullable)
  - `height` (integer, nullable)
  - `credit` (string, nullable)
  - `preset` (string, nullable)
  - `caption` (string, nullable)
  - `alt` (string, nullable)

## Errors

### 422 — Validation Error

Blank keyword, blank section, 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

Corriere does not know this section

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.