/rfi/podcasts/episodes

POST /api/rfi/podcasts/episodes

Price: 1 credit

List the episodes of one RFI radio programme, newest first, as deep into the archive as the requested count needs. Long-running programmes hold years of broadcasts. Each entry carries the episode title, its teaser, publication time, cover art, the page URL, whether RFI publishes a player for it and — this being radio — the episode's own playable MP3 with its running time in seconds and the full broadcast record behind it.

How to use it

Walk the archive of one RFI radio programme, and the only RFI listing that returns playable audio: a whole back catalogue of MP3s comes back without a second call per episode. podcast takes the programme slug ('spotlight-africa', 'international-report', 'culture-france'), or the full programme URL, in which case lang is ignored; rfi/podcasts reports how many episodes the archive holds, so read that before choosing a count. Each edition files its programmes under its own path segment and lang picks it, so pass the bare slug rather than a hand-built path. An episode usually sits under a different slug from the programme page, so follow the returned web_url and never compose one. Read is_playable rather than inferring from a null audio_url: RFI publishes no player for some older episodes and says so. Feed web_url into rfi/articles for the episode's written body, tags and images. 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)
• podcast string required — RFI radio programme slug, or the URL of the programme page (examples: "spotlight-africa", "international-report", "https://www.rfi.fr/en/podcasts/culture-france/", "algo-que-decir"; minLength: 1)
• count integer required — Max number of episodes to return (min: 1)
• lang string — Language edition the programme slug belongs to; ignored when podcast 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

• @type string (default: "RfiEpisodeCard")
• id string nullable
• episode_title string required
• description string nullable
• web_url string required
• alias string required
• language string required
• published_at integer nullable
• published_label string nullable
• duration integer nullable
• duration_label string nullable
• image string nullable
• program string nullable
• is_playable boolean (default: false)
• audio_url string nullable
• audio object nullable
  • @type string (default: "RfiAudio")
  • id string nullable
  • audio_url string required
  • duration integer nullable
  • audio_title string nullable
  • content_id string nullable
  • content_type string nullable
  • program_id string nullable
  • program_title string nullable
  • program_url string nullable
  • program_genre string nullable
  • season string nullable
  • season_episode string nullable
  • episode_id string nullable
  • episode_title string nullable
  • published_at integer nullable
  • published_label string nullable
  • web_url string nullable

Errors

• 422 — Not an RFI programme slug or programme URL, or an edition with no programme catalogue 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 — RFI publishes no programme page at this slug in this language edition 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.