/lemonde/authors

POST /api/lemonde/authors

Price: 10 credits

Get one Le Monde author by alias: display name, portrait, author page URL and how many articles Le Monde currently lists under that byline in the requested edition.

How to use it

Resolve a Le Monde byline to its canonical author record. alias is the slug used in /signataires/ URLs ('eric-albert'), which lemonde/articles and the listing endpoints return in authors[].alias; a full author page URL is accepted too, and an 'en/' prefix switches to the author's page in Le Monde in English. Returns name, image, web_url, language and articles_count (the exact number of articles on that author page right now). Use lemonde/authors/articles to read the articles themselves. Collective bylines Le Monde does not link (for example 'Le Monde avec AFP') have no alias and cannot be resolved here.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• alias string required — Le Monde author alias, or the URL of the author page; prefix with en/ for Le Monde in English (examples: "eric-albert", "en/eric-albert", "https://www.lemonde.fr/signataires/sylvie-kauffmann/"; minLength: 1)

Response

• @type string (default: "LemondeAuthorProfile")
• alias string required
• name string required
• web_url string required
• language string required
• image string nullable
• articles_count integer nullable

Errors

• 422 — Not a Le Monde author alias or author page 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 — No Le Monde author page for this alias 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.