# /france24/tags/articles

`POST /api/france24/tags/articles`

Price: 1 credit

List every France 24 story filed under one topic tag, newest first. Tags are France 24's own controlled vocabulary of people, places, organisations and themes, and the tag archive reaches back years: popular tags carry over ten thousand stories. Each entry carries headline, publication time, section, editorial genre label, thumbnail and whether the story is a video.

## How to use it

The deepest way into the France 24 archive by subject. tag takes a slug as it appears in a /tag/ URL ('donald-trump', 'gaza-strip', 'climate-change'), or the full tag URL, in which case lang is ignored. The vocabulary is closed — an invented slug returns 412, so take slugs from the tags field of france24/articles rather than guessing. lang selects the edition (fr, en, es, ar) and each edition keeps its own tag vocabulary. Results are newest first and paginate deeply; each entry carries article_title, web_url, alias, published_at, published_label, language, section, label, program, image and is_video, with no teaser, so feed web_url into france24/articles for the body. 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)
- `tag` (string, required) — France 24 tag slug, or the URL of the tag page (examples: "donald-trump", "gaza-strip", "https://www.france24.com/en/tag/israel-hamas-war/", "climate-change"; minLength: 1)
- `count` (integer, required) — Max number of articles to return (min: 1)
- `lang` (string) — Language edition the tag slug belongs to; ignored when tag is a full URL (default: "en"; one of: "fr", "en", "es", "ar")

## Response

### 200 — Successful Response

- `@type` (string) (default: "France24ArticleCard")
- `article_title` (string, required)
- `web_url` (string, required)
- `alias` (string, required)
- `published_at` (integer, nullable)
- `published_label` (string, nullable)
- `language` (string, required)
- `section` (string, nullable)
- `label` (string, nullable)
- `program` (string, nullable)
- `image` (string, nullable)
- `is_video` (boolean) (default: false)

## Errors

### 422 — Validation Error

Not a France 24 tag slug or tag 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 has no tag page with this slug in this language edition

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.