/guardian/feeds

POST /api/guardian/feeds

Price: 5 credits

Read the Guardian feed for any taxonomy path — section, keyword tag, series, contributor or edition front. Returns the newest articles with headline, a multi-paragraph excerpt, publish time, authors, the article's topic tags and a full-size image with photographer credit.

How to use it

Cheapest way to get the latest Guardian articles on a topic. tag takes any Guardian taxonomy path: a section ('world'), a keyword tag ('technology/artificialintelligenceai'), a series, a contributor ('profile/rafaelbehr') or an edition front ('uk', 'us', 'au', 'international'). Returns richer trailing text than the listing endpoint but only the most recent items — use guardian/tags/articles when you need to go further back.

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 read the feed for: a section (world), 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)
• count integer required — Max number of items to return (min: 1)

Response

• @type string (default: "GuardianFeedItem")
• id string required
• article_title string required
• web_url string required
• excerpt string nullable
• published_at integer nullable
• authors array (default: [])
• tags array (default: [])
  • @type string (default: "GuardianFeedItemTag")
  • id string required
  • name string required
  • web_url string required
• image string nullable
• image_credit 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 Guardian feed at this taxonomy path 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.