# /ansa/articles

`POST /api/ansa/articles`

Price: 5 credits

Get one ANSA article by its URL: headline, standfirst, full body text, publication and last update times, dateline city, byline, section breadcrumb, topic and named-entity tags, lead image with its caption, and media_url — the mp4 file on video items, the episode's player page on podcasts.

## How to use it

Fetch one ANSA item by its full page URL, which ends in the content id — a uuid on modern items, a bare number on the 2014 archive — and .html. That id on its own does not resolve, nor does any other path carrying it, and the path is case sensitive, so pass the URL exactly as ANSA published it; web_url from any of the three listing endpoints is already in that form. content_type says what the page is and what to expect: an article has body text, a video has none and puts the mp4 in media_url, a podcast has none either — its page carries the standfirst and nothing more — and puts the episode's player page, an HTML embed rather than an audio file, in media_url, and a gallery may return neither text nor a slide list. All four return the lead image. published_at and updated_at are separate instants and often differ — read updated_at for the wire's latest revision, and note that it is the only one the listing endpoints expose. tags mixes subject labels, people and organisations in one list without marking which is which, and each of them is accepted by ansa/tags/articles; ANSA also indexes place tags, which this list rarely carries. dateline is the wire's city of origin and is frequently absent.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `article` (string, required) — ANSA article URL (examples: "https://www.ansa.it/sito/notizie/cronaca/2026/08/26/pm-di-milano-i-rider-di-glovo-sono-ancora-sottopagati-vanno-assunti_cf877c3c-f775-4f87-a29a-460165bbb91c.html", "https://www.ansa.it/lombardia/notizie/2026/08/26/pm-milano-i-rider-di-glovo-ancora-sottopagati-vanno-assunti_c36d4b9c-32fc-4a4c-b463-72c197679889.html"; minLength: 1)

## Response

### 200 — Successful Response

- `@type` (string) (default: "AnsaArticle")
- `id` (string, required)
- `article_title` (string, required)
- `description` (string, nullable)
- `text` (string, nullable)
- `web_url` (string, required)
- `published_at` (integer, nullable)
- `updated_at` (integer, nullable)
- `section` (string, nullable)
- `sections` (array) (default: [])
- `channel` (string, required)
- `content_type` (string, required)
- `dateline` (string, nullable)
- `byline` (string, nullable)
- `tags` (array) (default: [])
- `image` (string, nullable)
- `image_caption` (string, nullable)
- `images` (array) (default: [])
  - `@type` (string) (default: "AnsaImage")
  - `image` (string, required)
  - `caption` (string, nullable)
  - `alt` (string, nullable)
- `media_url` (string, nullable)

## Errors

### 422 — Validation Error

Not an ANSA article URL, or the URL carries no content id

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 ANSA article at this URL, or the URL served a different item

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.