# /axios/topics/articles

`POST /api/axios/topics/articles`

Price: 20 credits

Browse published Axios stories filed under given topics, subtopics or audiences, walking the archive in publication order. Each story carries the headline, the Smart Brevity summary, publish and update timestamps, the Go deeper reading estimate, credited authors, the primary topic, the audience it belongs to and the lead image with its caption.

## How to use it

List Axios stories by taxonomy. Give at least one of topic_ids, subtopic_ids or audience_ids — the identifiers published by axios/topics and axios/audiences — and set count for how many stories to return. order walks the archive newest_first or oldest_first. Each item has id, article_title, web_url, alias, summary, published_at, first_published_at, updated_at, reading_time_minutes, rubrics[], authors[], topic, audience, image and the is_sponsored/is_live flags. Pass id or web_url to axios/articles for the full body.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `topic_ids` (array, nullable) — Only stories filed under these topic identifiers. The example is the national Business topic; the Axios Local topic of the same alias is a different identifier (examples: ["785d3ff8-a512-4319-9efd-ef40bab1d26b"])
- `subtopic_ids` (array, nullable) — Only stories filed under these subtopic identifiers
- `audience_ids` (array, nullable) — Only stories written for these audiences — the national desk or an Axios Local city (examples: ["4970ae44-6974-43aa-b21b-3858b622de55"])
- `order` (string) — Publication order the stories are walked in (default: "newest_first"; one of: "newest_first", "oldest_first")
- `count` (integer, required) — Max number of stories to return (min: 1)

## Response

### 200 — Successful Response

- `@type` (string) (default: "AxiosArticleCard")
- `id` (string, required)
- `article_title` (string, required)
- `web_url` (string, required)
- `alias` (string, nullable)
- `summary` (string, nullable)
- `published_at` (integer, nullable)
- `first_published_at` (integer, nullable)
- `updated_at` (integer, nullable)
- `reading_time_minutes` (integer, nullable)
- `image_caption` (string, nullable)
- `rubrics` (array) (default: [])
- `is_sponsored` (boolean, nullable)
- `is_live` (boolean, nullable)
- `paywall_status` (string, nullable)
- `image` (object, nullable)
  - `@type` (string) (default: "AxiosCardImage")
  - `url` (string, nullable)
  - `alt_text` (string, nullable)
  - `caption` (string, nullable)
  - `width` (integer, nullable)
  - `height` (integer, nullable)
- `authors` (array) (default: [])
  - `@type` (string) (default: "AxiosAuthor")
  - `alias` (string, required)
  - `name` (string, nullable)
  - `image` (string, nullable)
  - `profile_url` (string, nullable)
- `topic` (object, nullable)
  - `@type` (string) (default: "AxiosTopic")
  - `id` (string, required)
  - `alias` (string, required)
  - `name` (string, nullable)
  - `page_title` (string, nullable)
  - `description` (string, nullable)
  - `is_local` (boolean, nullable)
  - `nav_position` (integer, nullable)
  - `show_in_nav` (boolean, nullable)
- `audience` (object, nullable)
  - `@type` (string) (default: "AxiosAudience")
  - `id` (string, required)
  - `alias` (string, nullable)
  - `name` (string, nullable)
  - `audience_type` (string, nullable)
  - `timezone` (string, nullable)

## Errors

### 422 — Validation Error

The request body did not validate

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

The entity was not found, or a precondition failed

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.