# /lemonde/articles

`POST /api/lemonde/articles`

Price: 10 credits

Get one Le Monde article by its URL: headline, standfirst, body text, publication and update times, authors, section breadcrumb, keywords, lead image with caption and credit, in-body images, embedded video ids, related links and, on live pages, the timeline of live updates. Works for the French site and for Le Monde in English, and for article, live, video and podcast pages. Le Monde is metered: for subscriber-only articles the body is the free opening extract and the share of the text withheld is reported.

## How to use it

Fetch one Le Monde article by its full URL or by the bare numeric id inside that URL — both resolve, and the id is the cheaper form because it needs no slug or date. Returns article_title, description, text, published_at/updated_at (unix), language (fr or en), content_type (article, live, video, podcast), authors with their /signataires/ alias and job_title, sections (breadcrumb), keywords, image with caption and credit, images, videos (player id and provider), audio_url, related_articles and live_updates for live pages. is_premium marks subscriber-only articles; for those, text holds only the free opening extract, is_truncated is true and remaining_percent gives the share of the body withheld. Pre-2000 archive articles are all subscriber-only and about half of them carry no body element at all, so text is null there; when a body is present it is the truncated extract. On live pages text is null and the content is in live_updates. Podcast pages return metadata and audio_url but no transcript. translation_url links the same story in the other edition when Le Monde published one.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `article` (string, required) — Le Monde article URL or the numeric article id inside it (examples: "https://www.lemonde.fr/international/article/2026/08/13/guerre-en-ukraine-face-a-moscou-les-allies-de-kiev-sont-entres-dans-une-phase-accrue-d-incertitude_6745505_3210.html", "https://www.lemonde.fr/en/international/article/2026/08/13/with-russia-s-strikes-in-ukraine-and-hybrid-war-in-europe-kyiv-s-allies-face-heightened-uncertainty_6756460_4.html", "6745505"; minLength: 1)

## Response

### 200 — Successful Response

- `@type` (string) (default: "LemondeArticle")
- `id` (string, required)
- `article_title` (string, required)
- `description` (string, nullable)
- `text` (string, nullable)
- `web_url` (string, required)
- `published_at` (integer, nullable)
- `updated_at` (integer, nullable)
- `language` (string, required)
- `content_type` (string, required)
- `label` (string, nullable)
- `section` (string, nullable)
- `sections` (array) (default: [])
  - `@type` (string) (default: "LemondeTerm")
  - `name` (string, required)
  - `alias` (string, nullable)
  - `web_url` (string, nullable)
- `keywords` (array) (default: [])
- `byline` (string, nullable)
- `dateline` (string, nullable)
- `authors` (array) (default: [])
  - `@type` (string) (default: "LemondeAuthor")
  - `name` (string, required)
  - `alias` (string, nullable)
  - `profile_url` (string, nullable)
  - `job_title` (string, nullable)
- `image` (string, nullable)
- `image_caption` (string, nullable)
- `image_credit` (string, nullable)
- `images` (array) (default: [])
  - `@type` (string) (default: "LemondeImage")
  - `image` (string, required)
  - `caption` (string, nullable)
  - `credit` (string, nullable)
  - `alt` (string, nullable)
- `videos` (array) (default: [])
  - `@type` (string) (default: "LemondeVideo")
  - `id` (string, required)
  - `provider` (string, nullable)
- `video_duration` (string, nullable)
- `audio_url` (string, nullable)
- `is_premium` (boolean) (default: false)
- `is_truncated` (boolean) (default: false)
- `remaining_percent` (number, nullable)
- `reading_time` (integer, nullable)
- `translation_url` (string, nullable)
- `related_articles` (array) (default: [])
  - `@type` (string) (default: "LemondeRelatedArticle")
  - `id` (string, nullable)
  - `article_title` (string, required)
  - `web_url` (string, required)
  - `is_premium` (boolean) (default: false)
- `live_updates` (array) (default: [])
  - `@type` (string) (default: "LemondeLiveUpdate")
  - `id` (string, required)
  - `update_title` (string, nullable)
  - `text` (string, nullable)
  - `label` (string, nullable)
  - `published_at` (integer, nullable)
  - `images` (array) (default: [])
    - `@type` (string) (default: "LemondeImage")
    - `image` (string, required)
    - `caption` (string, nullable)
    - `credit` (string, nullable)
    - `alt` (string, nullable)

## Errors

### 422 — Validation Error

Not a Le Monde article URL

What to do: Check the fields against this schema. A URN with the wrong prefix is the most common cause.

- `detail` (array)
  - `loc` (array, required)
  - `msg` (string, required)
  - `type` (string, required)
  - `input` (any)
  - `ctx` (object)

### 408

The request ran past its time limit

What to do: 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 at this URL, or the URL redirected to a different article

What to do: 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

What to do: 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

What to do: 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

What to do: Wait at least 30 seconds, then retry.

## Response envelope

Success: Array of objects (may be empty if no results)

Error: Error may coexist with partial results if it occurs mid-execution. Check X-Error header and status code.

Every response carries these 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.