# /rfi/feeds

`POST /api/rfi/feeds`

Price: 1 credit

Read an RFI 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 RFI attaches to it. A radio programme's podcast feed is served on the same endpoint and adds the episode's MP3, its running time and its keywords. A feed carries only the newest few dozen items, so it shows what RFI published in the last few hours, in any of its seventeen language editions.

## How to use it

The usual starting point for seeing what RFI has just published. Leave feed empty for the edition's front feed, or pass a path relative to the language — a section as 'africa', a topic as 'tag/sahel', a radio programme as 'podcasts/spotlight-africa/podcast' — or a full feed URL, in which case lang is ignored. An RFI feed holds only the newest few dozen stories, so a large count simply returns all of them; for anything older use rfi/tags/articles or rfi/sections/articles. The two shapes carry disjoint fields: a path ending in 'podcast' rather than the default 'rss' returns the episode's MP3 and the iTunes metadata around it and, in exchange, none of the section, creator and image RFI prints only on the rss form, so read the fields rather than inferring audio from the path. The id here is the feed's own guid and is not the RFI content id rfi/articles returns for the same story, so match the two by web_url.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `feed` (string) — RFI section or tag path whose RSS feed to read, or the feed URL itself (default: ""; examples: "", "africa", "tag/sahel", "podcasts/spotlight-africa/podcast", "https://www.rfi.fr/fr/afrique/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", "pt", "br", "cn", "tw", "vi", "km", "ro", "sw", "ha", "fa", "ru", "ff", "uk", "ma")

## Response

### 200 — Successful Response

- `@type` (string) (default: "RfiFeedItem")
- `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)
- `season` (string, nullable)
- `season_episode` (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 an RFI 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

RFI 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.