# /ansa/articles/search

`POST /api/ansa/articles/search`

Price: 1 credit

Search the ANSA wire archive by keyword, optionally narrowed to one desk, regional wire or international edition, to an editorial genre, to an index tag or to a recent window. Returns listing entries with headline, a matching text excerpt, section label, last update time and the lead image.

## How to use it

Keyword search over the whole ANSA archive, which reaches back to at least 2014 and holds the national wire, the Italian regional wires, the verticals and the ANSAMed, Europa-UE and NuovaEuropa editions in one index. A keyword that matches nothing still returns a few dozen loosely related items rather than an empty list, so judge relevance from the rows, not from the fact that rows came back. sort defaults to date, which orders by the item's last update, not by its first publication; switch to relevance when the query is a topic rather than a time window. period counts whole calendar days, so last_week reaches back to the start of the day seven days ago. Filters combine. Each row is a listing card, not the article: snippet is an excerpt around the keyword match and is not the standfirst, and there is no body text or byline here — feed web_url into ansa/articles for those.

## 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, at least two characters (examples: "meloni", "intelligenza artificiale", "ornitorinco"; minLength: 2)
- `count` (integer, required) — Max number of items to return (min: 1)
- `section` (string, nullable) — Restrict to one ANSA desk, channel, Italian regional wire or international edition (one of: "cronaca", "cultura", "economia", "mondo", "politica", "sport", "foto", "video", "podcast", "scuola", "lifestyle", "motori", "responsabilmente", "terra_e_gusto", "oltretevere", "osservatorio_ai", "ansamed", "europa_ue", "nuovaeuropa", "abruzzo", "basilicata", "calabria", "campania", "emilia_romagna", "friuli_venezia_giulia", "lazio", "liguria", "lombardia", "marche", "molise", "piemonte", "puglia", "sardegna", "sicilia", "toscana", "trentino_alto_adige", "umbria", "valle_daosta", "veneto"; examples: "politica", "lombardia", "ansamed")
- `tag` (string, nullable) — Restrict to items carrying this ANSA index tag, spelled exactly as ANSA does, case sensitive (examples: "Giorgia Meloni", "Partito Democratico", "Governo nazionale")
- `period` (string, nullable) — Restrict to items updated inside this window, counted in whole days (one of: "last_week", "last_month", "last_year")
- `genre` (string, nullable) — Restrict to one ANSA editorial genre (one of: "analisi", "focus", "intervista", "news", "profilo", "reportage", "riepilogo", "scheda")
- `sort` (string) — Order of the result: newest update first, or keyword relevance (default: "date"; one of: "date", "relevance")

## Response

### 200 — Successful Response

- `@type` (string) (default: "AnsaArticleCard")
- `id` (string, required)
- `article_title` (string, required)
- `snippet` (string, nullable)
- `web_url` (string, required)
- `updated_at` (integer, nullable)
- `section` (string, nullable)
- `channel` (string, nullable)
- `image` (string, nullable)

## Errors

### 422 — Validation Error

Keyword shorter than two characters, containing " or ^, or ending in a backslash, blank tag, unknown section, genre, period or sort, or count below 1

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.