News monitoring
Mit The Guardian-Endpunkten verwandelst du news monitoring in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Turn The Guardian into structured JSON — full article content and metadata, fresh section headlines from its public RSS feeds, and paginated topic or category archives, all from canonical Guardian URLs.
Get Guardian article content, section headlines, and paginated topic archives as structured JSON from a canonical article URL or RSS section.
Endpunkt-Familien
5
Dokumentierte Parameter
13
Beispiele
5
Live-Katalog-Snapshot
Aktive Endpunkte
5
Methoden
GET
Pflichtparameter
8
Schema-Referenzen
5
{
"platform": "The Guardian",
"endpoint": "guardian-article",
"method": "GET",
"path": "/guardian/article",
"auth": "apiKey"
}Use Cases
Get Guardian article content, section headlines, and paginated topic archives as structured JSON from a canonical article URL or RSS section.
Mit The Guardian-Endpunkten verwandelst du news monitoring in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit The Guardian-Endpunkten verwandelst du topic and archive research in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit The Guardian-Endpunkten verwandelst du content aggregation in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Managed Execution
Jede Zahl unten stammt direkt aus dem Live-The Guardian-Endpunktkatalog — 5 Endpunkte, 13 dokumentierte Request-Parameter und 5 veröffentlichte Response-Schemas — demselben Katalog, gegen den auch Docs und Playground laufen.
5 documented The Guardian endpoints, grouped into 5 request families — Article, Author and Headlines, plus 2 more.
13 request parameters are documented across those The Guardian endpoints, 8 of them required — the full input contract is public before you write any integration code.
5 of the 5 The Guardian endpoints ship a recorded example response, and 5 carry a documented response schema — you can code against the real JSON before the first request.
The Guardian endpoints document their error responses (400, 404, 429 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
4 hosted MCP tools back the The Guardian endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Abdeckungskarte
/guardian/article
/guardian/author
/guardian/headlines
/guardian/live
/guardian/topic
Endpunktkatalog
/guardian/articleReturns a Guardian article by `url`, a canonical `www.theguardian.com` article link. The response has the title, description, section, authors, lead image, publication and update times, and the body as `paragraphs`. Live-blog timelines are not supported.
MCP-Tool guardian_article
/guardian/authorReturns one Guardian contributor's public profile: name, bio, Twitter handle, byline image, and one page of their recent articles. Provide either the contributor's profile slug or the full profile page URL.
MCP-Tool guardian_author
/guardian/headlinesReturns recent Guardian headlines for one section. `section` is optional and defaults to `world`; the other values are `uk-news`, `us-news`, `politics`, `business`, `technology`, `environment`, `science`, `sport`, `culture`, `lifeandstyle` and `commentisfree`. Each item has a title, URL, summary, publication time and author, plus its section when available.
MCP-Tool guardian_headlines
/guardian/liveReturns a bounded text snapshot of one public Guardian live blog: the headline, the key-events timeline, and the update blocks with timestamps, headings, bylines, and body paragraphs. This is a single page fetch of the public page at a canonical live-blog URL — not a live stream or polling feed. URLs must use the dated www.theguardian.com section /live/ path, e.g. https://www.theguardian.com/sport/live/2026/aug/08/<slug>/.
Hinweise zur Response
Returns a bounded text snapshot of the public live-blog page: the headline, the key-events timeline, and the update blocks (newest first) with ISO timestamps, headings, bylines, and body paragraphs. This is a single page fetch of the public page — not a live stream, polling feed, or media source. A missing or non-live URL returns `404`.
/guardian/topicReturns the stories on a public Guardian tag archive (20 per page, newest first, with total pages and results) or section front (a single curated page, is_front true). topic is a Guardian tag or section slug and page defaults to 1. resolved_topic reports the path actually served, which differs for edition-scoped fronts.
Hinweise zur Response
- Tag archives (`is_front: false`) return 20 stories per page, newest first. `pagination.total_pages` and `pagination.total_results` report the archive size; `has_next`/`next_page` are set while another page exists within the `page` limit of `100`. - Section fronts (`is_front: true`, for example `world`) are a single curated page: `total_pages` is `1`, `has_next` is `false`, and `page` values above `1` return an empty `items` list. - `resolved_topic` is the path the Guardian actually served. It differs from `topic` for edition-scoped fronts (for example `technology` resolves to `uk/technology`). - A `page` beyond the end of a tag archive returns an empty `items` list with `has_next: false`. - `published_at` is an RFC 3339 UTC timestamp. `section` is the story's own Guardian section (the first URL segment), which can differ from the requested topic. - Items are always individual stories (articles, live blogs, video, audio); date-archive links are never returned.
MCP-Tool guardian_topic
Verwandte APIs
Media & Streaming
Browse Sportskeeda's sports and entertainment coverage, community wikis, quizzes, and fan games with the catalog's current slugs and filter limits.
Media & Streaming
Research streaming catalogs, title availability, providers, offers, seasons, episodes, and release changes from JustWatch with normalized JSON.
Media & Streaming
Turn Apple Books ebook and audiobook pages into structured data — search, catalog detail, paginated customer reviews, similar titles, author bibliographies, series listings, and chart rankings as normalized JSON. Credential-free.
So scrapst du The Guardian
Crawlora's Guardian endpoints read theguardian.com and return JSON for articles, section headlines, topic archives, and live blogs. Guardian feeds are rich. The technology feed held 35 stories on 2026-09-18, each with a multi-sentence standfirst and the author's name, and articles return an updated_at that often differs from published_at because the Guardian revises stories after publication.
/guardian/headlines accepts world, uk-news, us-news, politics, business, technology, environment, or science. Each item carries title, URL, a long summary (standfirst plus opening text), published_at, and author.
/guardian/article returns title, published_at and updated_at, an authors list, image_url, and the body as paragraphs. One OpenAI story published on 17 September was updated 12 hours later, and the updated_at field captures that.
/guardian/live takes a dated www.theguardian.com …/live/… URL and returns the headline, the key-events timeline, and update blocks, newest first, with timestamps, headings, and bylines. A non-live URL returns 404.
/guardian/topic takes a tag or section slug such as world/ukraine or technology/artificialintelligenceai, plus page. Tag archives return 20 stories per page, newest first, with total_pages and total_results; world/ukraine reported 931 pages and 18,604 stories on 2026-09-18. Section slugs such as world return the curated front as a single page with is_front set to true.
FAQ
Yes. /guardian/live returns a snapshot of a live blog's key events and updates with timestamps and bylines. The URL must use the dated /live/ path.
The Guardian revises stories after publication. updated_at records the latest revision, which is often hours after published_at.
world, uk-news, us-news, politics, business, technology, environment, and science.