POST /api/lemonde/archives/articles
Price: 10 credits
List everything Le Monde published on one calendar day, back to 19 December 1944. Returns listing entries with headline, standfirst, publication and update times, byline, editorial genre label, section and a subscriber-only flag.
Walk Le Monde day by day. day takes DD-MM-YYYY or YYYY-MM-DD and covers 19-12-1944 to today. Each entry carries id, article_title, description, web_url, published_at, updated_at, byline, label, section, content_type, is_premium, is_live, video_duration and image; feed web_url into lemonde/articles for the body. Rows come back newest first within the day. Every pre-2000 archive article is subscriber-only, and about half of those pages carry no body element at all while the rest return only the truncated opening extract, so this endpoint is the way to inventory historic coverage rather than to read it. A day outside the archive range returns 412 rather than another day's edition.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)day string required — Day of the Le Monde edition to list, as DD-MM-YYYY or YYYY-MM-DD; the archive starts on 19-12-1944 (examples: "19-12-1944", "2015-06-15"; minLength: 1)count integer required — Max number of articles to return (min: 1)@type string (default: "LemondeArticleCard")id string requiredarticle_title string requireddescription string nullableweb_url string requiredpublished_at integer nullableupdated_at integer nullablelanguage string requiredcontent_type string requiredsection string requiredlabel string nullablebyline string nullableauthors array (default: [])@type string (default: "LemondeAuthor")name string requiredalias string nullableprofile_url string nullablejob_title string nullableis_premium boolean (default: false)is_live boolean (default: false)video_duration string nullableimage string nullable422 — Not a valid calendar day 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 archive page for this day 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.