# /france24/feeds

`POST /api/france24/feeds`

Price: 1 credit

Read a France 24 RSS feed: the newest stories of the whole edition, of one news section or of one topic tag, with headline, summary, publication time, section, lead image and the photo credit France 24 attaches to it. A programme's podcast feed is served on the same endpoint and adds the episode's media file, its running time and its keywords. The cheapest way to see what France 24 published in the last few hours, in any of the four language editions.

## How to use it

Cheapest France 24 endpoint and the usual starting point. Leave feed empty for the edition's front feed, or pass a section path relative to the language ('france', 'africa', 'middle-east', 'americas', 'europe', 'asia-pacific', 'business', 'sport', 'culture', 'earth', 'health'), a topic feed as 'tag/donald-trump', a TV show as 'tv-shows/debate', or a full feed URL, in which case lang is ignored. A France 24 feed holds only the newest few dozen stories, so a large count simply returns all of them. Each item carries id, article_title, description, web_url, alias, published_at, language, section, creator, image and image_credit. Ending the path with 'podcast' instead of the default 'rss' reads a programme's podcast feed ('tv-shows/debate/podcast', 'émissions/podcast-avec-judith/podcast' on fr, 'programas/áfrica-7-días/podcast' on es, 'برامج/أخبار-الصحة/podcast' on ar); those items additionally carry media_url and media_type (the episode's own mp4), duration in seconds, keywords, author, subtitle, episode_type and is_explicit, and in exchange carry no section, creator, image or image_credit, which France 24 prints only on the rss form. To reach further back use france24/sections/articles or france24/tags/articles, and feed web_url into france24/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) — France 24 section or tag path whose RSS feed to read, or the feed URL itself (default: ""; examples: "", "africa", "tag/donald-trump", "tv-shows/debate/podcast", "https://www.france24.com/en/sport/rss")
- `count` (integer, required) — Max number of items to return (min: 1)
- `lang` (string) — Language edition to read; ignored when feed is a full URL (default: "en"; one of: "fr", "en", "es", "ar")

## Response

### 200 — Successful Response

- `@type` (string) (default: "France24FeedItem")
- `id` (string, nullable)
- `article_title` (string, required)
- `description` (string, nullable)
- `web_url` (string, required)
- `alias` (string, required)
- `published_at` (integer, nullable)
- `language` (string, required)
- `section` (string, nullable)
- `creator` (string, nullable)
- `image` (string, nullable)
- `image_credit` (string, nullable)
- `author` (string, nullable)
- `subtitle` (string, nullable)
- `keywords` (array) (default: [])
- `duration` (integer, nullable)
- `episode_type` (string, nullable)
- `is_explicit` (boolean, nullable)
- `media_url` (string, nullable)
- `media_type` (string, nullable)

## Errors

### 422 — Validation Error

Not a France 24 section path, tag path, podcast path or feed URL

What to do: Check the fields against this schema. A URN with the wrong prefix is the most common cause.

- `detail` (array)
  - `loc` (array, required)
  - `msg` (string, required)
  - `type` (string, required)
  - `input` (any)
  - `ctx` (object)

### 408

The request ran past its time limit

What to do: 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

France 24 publishes no feed at this path

What to do: 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

What to do: 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

What to do: 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

What to do: Wait at least 30 seconds, then retry.

## Response envelope

Success: Array of objects (may be empty if no results)

Error: Error may coexist with partial results if it occurs mid-execution. Check X-Error header and status code.

Every response carries these 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.