/politico/articles

POST /api/politico/articles

Price: 10 credits

Get a full POLITICO article or newsletter issue: headline, standfirst, the whole body as plain text and as HTML with the editors' inline source links, publish and update timestamps, every credited author with a profile link, the policy sections, and the three parallel tag axes POLITICO files a story under — topics, countries and named people.

How to use it

Fetch one POLITICO article, newsletter issue or live-blog entry. Accepts the numeric article id or a politico.eu URL. Returns one item with article_title, dek, text, html, published_at, updated_at, edition, authors[], sections[], tags[] and the topics[]/countries[]/people[] tag axes, image and image_caption, section_path and post_types. Ids and URLs come from politico/articles/search; for the editions outside politico.eu pass the id rather than the URL, and html, dek and the three tag axes are then not filled. A search card whose web_url ends in a #{id} anchor is a live-blog entry: pass that whole web_url, because its numeric id is also a valid ordinary article id and the id alone resolves to the article. A live-blog entry returns its own headline, text, html, authors and timestamps; dek, image, section_path and the three tag axes stay empty for it, because those belong to the parent article the entry sits in and not to the entry.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• article string required — POLITICO article id, or a politico.eu article, newsletter or live-blog-entry URL (the live-blog entry is the #{id} anchor a search card carries) (examples: "8841940", "https://www.politico.eu/article/spain-ceuta-migrant-crisis-africa-territories-morocco-melilla/", "https://www.politico.eu/newsletter/brussels-playbook/the-eus-other-top-diplomat/", "https://www.politico.eu/article/andy-burnham-to-become-uk-prime-minister/#1328634"; minLength: 1)

Response

• @type string (default: "PoliticoArticle")
• id string required
• article_title string required
• web_url string required
• alias string nullable
• edition string nullable
• dek string nullable
• text string nullable
• html string nullable
• published_at integer nullable
• updated_at integer nullable
• post_types array (default: [])
• image string nullable
• image_caption string nullable
• section_path array (default: [])
• authors array (default: [])
  • @type string (default: "PoliticoAuthor")
  • id string nullable
  • name string required
  • alias string nullable
  • profile_url string nullable
• sections array (default: [])
  • @type string (default: "PoliticoSection")
  • alias string required
  • name string nullable
• tags array (default: [])
  • @type string (default: "PoliticoTag")
  • id string required
  • name string required
• topics array (default: [])
  • @type string (default: "PoliticoTaxonomyTag")
  • name string required
  • alias string nullable
  • web_url string nullable
• countries array (default: [])
  • @type string (default: "PoliticoTaxonomyTag")
  • name string required
  • alias string nullable
  • web_url string nullable
• people array (default: [])
  • @type string (default: "PoliticoTaxonomyTag")
  • name string required
  • alias string nullable
  • web_url string nullable

Errors

• 422 — The request body did not validate 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 — Article not found (well-formed but nonexistent article id or politico.eu URL), or the URL resolved to a different article 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.