/guardian/tags/articles

POST /api/guardian/tags/articles

Price: 20 credits

List Guardian articles filed under any taxonomy path — a section, a keyword tag, a series, a contributor profile or an edition front. Returns cards with headline, kicker, byline, publish time, image and the article url, newest first for sections, tags, series and contributors. An edition front (uk, us, au, international, europe) has no chronological archive, so it returns the front page in its editorial order and nothing beyond it. Pass date to get everything published under that path on a single day instead.

How to use it

Browse Guardian coverage of a topic. tag takes any Guardian taxonomy path: a section ('world', 'football'), a keyword tag ('technology/artificialintelligenceai' — these come back in the tags list of guardian/articles, and guardian/tags/search lists them all), a series, a contributor ('profile/rafaelbehr') or an edition front ('uk', 'us', 'au', 'international', 'europe'). For everything except edition fronts the order is newest first and count can reach as far back as the path goes; an edition front is a curated home page, so it comes back in the editors' order and a count above its size simply returns everything it holds. Add date (YYYY-MM-DD) to switch to that day's archive, which also carries a standfirst per card. Feed web_url or id into guardian/articles for the full piece.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• tag string required — Guardian taxonomy path to browse: a section (world, football, commentisfree), a keyword tag (technology/artificialintelligenceai), a series, a contributor (profile/rafaelbehr) or an edition front (uk, us, au, international). Full URLs are accepted too (examples: "world", "technology/artificialintelligenceai", "profile/rafaelbehr"; minLength: 1)
• date string nullable — Return only articles published on this day (YYYY-MM-DD) instead of the newest-first feed (examples: "2026-08-05")
• count integer required — Max number of articles to return (min: 1)

Response

• @type string (default: "GuardianArticleCard")
• id string required
• article_title string required
• web_url string required
• short_url_id string nullable
• kicker string nullable
• standfirst string nullable
• byline string nullable
• published_at integer nullable
• image string nullable
• card_type 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 — No such taxonomy path, or no articles published under it on the requested date 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.