POST /api/rfi/articles
Price: 10 credits
Get one RFI story by its URL: headline, standfirst, body text, publication and update times, section breadcrumb, keywords and topic tags, bylines with the role RFI credits each contributor under, lead image with its caption and photo credit, in-body images, and — on the radio material RFI is built around — the broadcast audio with its MP3 address, running time, programme and episode identity. Works for news articles, agency wire copy, radio editions and video pages, in every one of RFI's seventeen language editions.
Fetch one RFI story by its full URL or by the path after the host; the language and section segments are part of the address, so a bare slug does not resolve. audios carries the story's own broadcast — the MP3, its running time and the programme it went out under — and is empty on text-only news, so read it rather than inferring radio material from the section; a whole programme's back catalogue of MP3s comes from rfi/podcasts/episodes rather than from resolving each episode here. A broadcast bulletin can publish audio and a standfirst with no written body at all, so a null text is the source saying so, not a parse failure. Each tag carries its own language for rfi/tags/articles — pass the tag's language rather than the story's, because some editions file their stories under another edition's tags. The id here is RFI's content id and is not the guid rfi/feeds returns for the same story. Get URLs from rfi/feeds, rfi/sections/articles, rfi/tags/articles or rfi/podcasts/episodes.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)article string required — RFI article URL, or the same path without the host (examples: "https://www.rfi.fr/en/international/20260824-mediterranean-migrant-rescue-ships-threatened-by-libyan-groups-warns-ngo", "en/culture/20190124-who-stole-goyas-head-new-documentary-asks-questions-about-treatment-artists", "https://www.rfi.fr/fr/afrique/20260826-guinée-six-corps-découverts-dans-une-fosse-commune"; minLength: 1)@type string (default: "RfiArticle")id string nullablearticle_title string requireddescription string nullabletext string nullableweb_url string requiredlanguage string requiredcontent_type string nullablepublished_at integer nullableupdated_at integer nullablesection string nullablesections array (default: [])@type string (default: "RfiSection")name string requiredweb_url string requiredtags array (default: [])@type string (default: "RfiTag")name string requiredalias string requiredweb_url string requiredlanguage string nullablekeywords array (default: [])authors array (default: [])@type string (default: "RfiAuthor")name string requiredrole string nullableprofile_url string nullabledateline string nullablereading_time integer nullableword_count integer nullableimage string nullableimage_caption string nullableimage_credit string nullableimages array (default: [])@type string (default: "RfiImage")image string requiredcaption string nullablecredit string nullablealt string nullableaudios array (default: [])@type string (default: "RfiAudio")id string nullableaudio_url string requiredduration integer nullableaudio_title string nullablecontent_id string nullablecontent_type string nullableprogram_id string nullableprogram_title string nullableprogram_url string nullableprogram_genre string nullableseason string nullableseason_episode string nullableepisode_id string nullableepisode_title string nullablepublished_at integer nullablepublished_label string nullableweb_url string nullablevideos array (default: [])@type string (default: "RfiVideo")video_url string nullablethumbnail string nullableduration integer nullablevideo_title string nullablevideo_description string nullableuploaded_at integer nullablerelated_articles array (default: [])@type string (default: "RfiRelatedArticle")article_title string requiredweb_url string requiredis_free boolean nullable422 — Not an RFI content URL 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 RFI story at this URL, or the URL is a listing page rather than a story 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.