/guardian/articles

POST /api/guardian/articles

Price: 10 credits

Get a full Guardian article by URL or path: headline, standfirst, full body text, authors with their profile links and portraits, publish and last-modified timestamps, section and pillar, typed tags, series, images with caption and credit, podcast audio, video, word count and content flags. Works for news, opinion, interactive, video, gallery, cartoon, podcast and live blog pages.

How to use it

Fetch one Guardian article by its URL (or the path part, e.g. 'uk-news/2026/aug/04/mi6-top-european-foreign-intelligence-service-peer-review'). Returns a single item with article_title, standfirst, text (plain-text body), published_at and updated_at (unix seconds — they differ when the piece was edited), authors, tags (id, type and browse url you can feed into guardian/tags/articles), images with caption and credit, audio_url for podcasts, video_url for video pieces, and short_url_id which guardian/articles/comments accepts. is_live_blog marks live coverage — use guardian/articles/updates for its individual updates.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• article string required — Guardian article URL or its path (section/year/month/day/slug) (examples: "https://www.theguardian.com/uk-news/2026/aug/04/mi6-top-european-foreign-intelligence-service-peer-review", "commentisfree/2026/aug/05/ai-regulation-donald-trump-artificial-intelligence"; minLength: 1)

Response

• @type string (default: "GuardianArticle")
• id string required
• article_title string required
• standfirst string nullable
• text string nullable
• web_url string required
• short_url string nullable
• short_url_id string nullable
• published_at integer nullable
• updated_at integer nullable
• section string nullable
• section_name string nullable
• pillar string nullable
• content_type string nullable
• publication string nullable
• production_office string nullable
• byline string nullable
• authors array (default: [])
  • @type string (default: "GuardianArticleAuthor")
  • name string required
  • alias string nullable
  • profile_url string nullable
  • image string nullable
• tags array (default: [])
  • @type string (default: "GuardianArticleTag")
  • id string required
  • name string required
  • type string nullable
  • web_url string nullable
• tones array (default: [])
• series string nullable
• series_id string nullable
• blog string nullable
• blog_id string nullable
• commissioning_desks array (default: [])
• tracking_names array (default: [])
• atom_types array (default: [])
• references array (default: [])
  • @type string (default: "GuardianArticleReference")
  • type string required
  • value string required
• rich_link_url string nullable
• image string nullable
• images array (default: [])
  • @type string (default: "GuardianArticleImage")
  • image string required
  • caption string nullable
  • credit string nullable
  • role string nullable
  • ratio number nullable
• gallery_image_count integer nullable
• audio_url string nullable
• video_id string nullable
• video_url string nullable
• video_duration integer nullable
• word_count integer nullable
• internal_link_count integer nullable
• external_link_count integer nullable
• is_live boolean (default: false)
• is_live_blog boolean (default: false)
• is_commentable boolean (default: false)
• is_podcast boolean (default: false)
• is_embeddable boolean (default: false)
• is_paid_content boolean (default: false)
• is_immersive boolean (default: false)
• is_photo_essay boolean (default: false)
• is_numbered_list boolean (default: false)
• is_column boolean (default: false)
• is_sensitive boolean (default: false)
• is_hosted boolean (default: false)
• is_accessible_for_free boolean 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, or the path points at a section/tag/profile page rather than an 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.