/france24/sections/articles

POST /api/france24/sections/articles

Price: 1 credit

List the stories France 24 publishes on any of its listing pages, newest first: a news section, the rolling live-news feed, a TV-show page, an author page or a monthly archive. Each entry carries headline, section, editorial genre label, thumbnail, whether the story is a video and, on the listings that print one, the publication time; it goes as deep into the listing as the requested count needs.

How to use it

Browse France 24 by page. section takes the path of any listing page, with the language segment first: a news section ('en/france', 'en/africa', 'en/middle-east', 'en/americas', 'en/europe', 'en/asia-pacific', 'en/business', 'en/sport', 'en/culture', 'en/environment'), the rolling wire feed 'en/live-news', a TV show 'en/tv-shows/debate', an author page 'en/author/france-24', or a monthly archive 'en/archives/2015/06'. A full page URL is accepted too, and any page number in it is ignored so the answer always starts at the newest. A section France 24 has renamed or localised is followed to the front it serves today and the stories come back from there: 'en/business' and 'en/economy' both answer with the stories on 'en/business-tech', 'fr/economie' with 'fr/éco-tech', 'fr/planete' with 'fr/environnement' and 'ar/middle-east' with the Arabic-slugged Middle East front, and each card's web_url and section show where it actually came from. A path France 24 serves nowhere is still a 412. For a topic use france24/tags/articles instead. Results are newest first and carry article_title, web_url, alias, published_at, published_label, language, section, label, program, image and is_video; feed web_url into france24/articles for the body. A news section front page is curated and holds about thirty stories, while tag, author, show and archive pages reach thousands. Dates are not printed everywhere: a news section front renders none at all, so published_at and published_label are both empty there; on the rolling wire feed France 24 prints only a clock, so published_at is empty and published_label carries it; author, show and archive listings do carry a stamp. A monthly archive gives title and link only, with the day in published_label, and holds nothing before 2008 in the English edition. The walk stops after 400 listing pages, so a count beyond that comes back short rather than erroring.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• section string required — France 24 listing page path, or the URL of that page (examples: "en/france", "en/live-news", "https://www.france24.com/en/tv-shows/debate/", "fr/archives/2020/06", "ar/middle-east"; minLength: 1)
• count integer required — Max number of articles to return (min: 1)

Response

• @type string (default: "France24ArticleCard")
• article_title string required
• web_url string required
• alias string required
• published_at integer nullable
• published_label string nullable
• language string required
• section string nullable
• label string nullable
• program string nullable
• image string nullable
• is_video boolean (default: false)

Errors

• 422 — Not a France 24 listing path 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 France 24 listing page 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.