/ansa/tags/articles

POST /api/ansa/tags/articles

Price: 1 credit

List ANSA items carrying one index tag — a person, an organisation, a place or a subject label ANSA attaches to the item — most recently updated first. Returns listing entries with headline, lead excerpt, section label, last update time and the lead image.

How to use it

Follow one of ANSA's own index tags instead of searching text, which is what makes it the right call for 'everything about this person or organisation': the tag is attached by ANSA's desk, so it reaches items whose headline and excerpt never spell the name out — most of a 'Partito Democratico' feed does not. Matching is exact and case sensitive: 'Giorgia Meloni' works, 'giorgia meloni' returns nothing, and 'Meloni' is a separate entry with its own corpus rather than a prefix match. An unknown tag returns an empty list rather than an error, so a zero result usually means the spelling is off. Take tags from an article's own tags field. ANSA also indexes place tags such as 'Bruxelles' and 'Roma' and accepts them here, though an article's own tags field rarely lists a place. Rows are listing cards: feed web_url into ansa/articles for the body.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• tag string required — ANSA index tag, spelled exactly as ANSA does, case sensitive (examples: "Giorgia Meloni", "Partito Democratico", "Bruxelles", "Governo nazionale"; minLength: 1)
• 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")
• 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

• @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 — Blank tag, unknown section, genre or period, or count below 1 Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit 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 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 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 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 Wait at least 30 seconds, then retry.

Response 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.