# /ansa/sections/articles

`POST /api/ansa/sections/articles`

Price: 1 credit

List ANSA items filed under one desk, channel, Italian regional wire or international edition, most recently updated first, straight down the archive. Returns listing entries with headline, lead excerpt, section label, last update time and the lead image.

## How to use it

Browse ANSA by section without a keyword. section spans three different things under one name: the national desks (cronaca, politica, economia, mondo, cultura, sport), the media and vertical channels (foto, video, podcast, motori, lifestyle, scuola, terra_e_gusto, oltretevere for the Vatican desk, osservatorio_ai, responsabilmente), the twenty Italian regional wires (lombardia, sicilia, valle_daosta and so on), and the three international editions (ansamed, europa_ue, nuovaeuropa). One item is often filed under several of them at once, under a different URL and a different id each time, so the same story can appear in both a desk and a regional listing. Ordering is by last update, so a revised older item can outrank a newer one. Each row is a listing card: feed web_url into ansa/articles for the body text, byline and tags.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `section` (string, required) — 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")
- `count` (integer, required) — Max number of items to return (min: 1)
- `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")

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

Unknown section, genre or period, blank tag, 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.