/lemonde/articles/search

POST /api/lemonde/articles/search

Price: 20 credits

Search Le Monde articles by keyword, optionally restricted to a publication date range. Returns listing entries with headline, standfirst, publication and update times, byline, editorial genre label, section, thumbnail and a subscriber-only flag, ordered by relevance.

How to use it

Keyword search over Le Monde's French archive, which reaches back to 19 December 1944. Pass published_after and published_before (unix, day granularity in Paris time) to restrict the period. Each entry carries id, article_title, description, web_url, published_at, updated_at, byline, authors (with /signataires/ alias when the byline is linked), label (Décryptage, Reportage, Tribune…), section, content_type (article, live, video, podcast), is_premium, is_live, video_duration and image. Feed web_url into lemonde/articles for the body. Rows are ordered by relevance, not by date, so read published_at rather than the position. Narrow the date range to reach further back than one query can return. This surface covers the French edition only — for Le Monde in English use lemonde/sections/articles on an en/… path.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string required — Search phrase (examples: "ukraine", "intelligence artificielle"; minLength: 1)
• count integer required — Max number of articles to return (min: 1; max: 10000)
• published_after integer nullable — Only articles published on or after this unix timestamp; applied at day granularity in Paris time, and Le Monde's own archive starts on 19/12/1944
• published_before integer nullable — Only articles published on or before this unix timestamp; applied at day granularity in Paris time

Response

• @type string (default: "LemondeArticleCard")
• 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
• label string nullable
• byline string nullable
• authors array (default: [])
  • @type string (default: "LemondeAuthor")
  • name string required
  • alias string nullable
  • profile_url string nullable
  • job_title string nullable
• is_premium boolean (default: false)
• is_live boolean (default: false)
• video_duration string nullable
• image string nullable

Errors

• 422 — Blank keyword, count out of range, or published_after later than published_before 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 — The entity was not found, or a precondition failed 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.