/rfi/podcasts

POST /api/rfi/podcasts

Price: 10 credits

Get one RFI radio programme by its slug: the programme title, the standfirst describing the format and broadcast slot, its cover art, the presenters RFI credits on the programme page, the RFI content id, the programme's editorial genre and current season, how many episodes the archive holds, the address of its podcast feed, and the newest episode's playable audio. Available in the sixteen editions that publish a programme catalogue.

How to use it

Look up one RFI radio programme. podcast takes the programme slug ('spotlight-africa', 'international-report', 'culture-france', 'mid-east-junction', 'sound-kitchen'), or the full programme URL, in which case lang is ignored. Each edition files its programmes under its own path segment and lang picks it for you, so pass the bare slug rather than a hand-built path. Note the slug is not always the display name, and the episodes' own URLs usually sit under a different slug again. episode_count is RFI's own count of the whole archive, so read it before choosing a count for rfi/podcasts/episodes. feed_url is the programme's podcast RSS, which rfi/feeds reads directly, and latest_audio is the newest episode's MP3. The Mandenkan edition (ma) publishes no programme catalogue at all, so any slug there is a 422 rather than a 412.

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)
• 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: "RfiProgram")
• id string nullable
• program_title string required
• description string nullable
• web_url string required
• alias string required
• language string required
• image string nullable
• hosts array (default: [])
  • @type string (default: "RfiAuthor")
  • name string required
  • role string nullable
  • profile_url string nullable
• feed_url string nullable
• genre string nullable
• season string nullable
• episode_count integer nullable
• first_published_at integer nullable
• latest_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.