/lemonde/feeds

POST /api/lemonde/feeds

Price: 1 credit

Read a Le Monde RSS feed: the newest articles of a section or of the front page, with headline, summary, publication time, section and a lead image carrying its caption and photo credit.

How to use it

Cheapest way to get the very latest Le Monde articles. feed takes a section path ('international', 'economie', 'sport', 'pixels', 'cinema', 'football'), the English edition with the en/ prefix ('en/international'), one of the four site-wide codes 'une' (front page), 'en_continu' (rolling news), 'plus-lus' (most read) or 'plus-partages' (most shared), or a full rss_full.xml URL. Feeds hold only the newest few dozen items and cannot be paged — use lemonde/sections/articles to go further back. Each item carries id, article_title, description, web_url, published_at, updated_at, language, section, content_type and image with image_caption and image_credit; updated_at is the last editorial change and is present on about two thirds of items. Items are not strictly newest first, so sort on published_at. Feed web_url into lemonde/articles for the body.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• feed string required — Le Monde section path, feed code or feed URL (examples: "une", "international", "en/international", "https://www.lemonde.fr/pixels/rss_full.xml"; minLength: 1)
• count integer required — Max number of items to return (min: 1)

Response

• @type string (default: "LemondeFeedItem")
• id string required
• article_title string required
• description string nullable
• web_url string required
• published_at integer nullable
• updated_at integer nullable
• language string required
• content_type string required
• section string required
• image string nullable
• image_caption string nullable
• image_credit string nullable

Errors

• 422 — Not a Le Monde section path, feed code or feed URL 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 — Le Monde publishes no feed at this 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.