# /hk01/zones/articles

`POST /api/hk01/zones/articles`

Price: 10 credits

List the newest HK01 (香港01) articles inside a top-level zone (港聞 Hong Kong, 娛樂 entertainment, 體育 sport, 國際 world, 中國 China, 經濟 economy and 18 more). Returns the same article objects as hk01/articles minus the body: headline, lead, zone, channel, tags, images, video, reactions and dates.

## How to use it

Newest-first feed of one HK01 zone. Pick zone by its Chinese name (港聞, 娛樂, 體育, 國際, 中國, 熱話, 經濟, 健康, 教育, 01TV …). The feed keeps roughly the last thousand items of the zone; use hk01/articles/search with published_before to reach older material. Pass any returned id to hk01/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)
- `zone` (string, required) — HK01 top-level zone (one of: "港聞", "娛樂", "體育", "國際", "中國", "女生", "熱話", "生活", "藝文格物", "社區", "科技玩物", "觀點", "影像", "經濟", "活動購票", "會員資訊", "好食玩飛", "形而", "01TV", "其他", "教育", "健康", "01深圳", "01創科")
- `count` (integer, required) — Max number of articles to return (min: 1)
- `locale` (string) — Content language variant (default: "zh-HK"; one of: "zh-HK", "zh-CN")

## Response

### 200 — Successful Response

- `@type` (string) (default: "Hk01ArticleCard")
- `id` (integer, required)
- `article_title` (string, required)
- `description` (string, nullable)
- `web_url` (string, nullable)
- `authors` (array) (default: [])
- `zone` (object, nullable)
  - `@type` (string) (default: "Hk01ArticleZone")
  - `id` (integer, required)
  - `name` (string, required)
  - `web_url` (string, nullable)
  - `image` (string, nullable)
- `main_category_id` (integer, nullable)
- `main_category` (string, nullable)
- `categories` (array) (default: [])
  - `@type` (string) (default: "Hk01Category")
  - `id` (integer, required)
  - `name` (string, required)
  - `web_url` (string, nullable)
  - `image` (string, nullable)
- `tags` (array) (default: [])
  - `@type` (string) (default: "Hk01Tag")
  - `id` (integer, required)
  - `name` (string, required)
  - `web_url` (string, nullable)
  - `is_sponsored` (boolean) (default: false)
- `is_featured` (boolean) (default: false)
- `is_sponsored` (boolean) (default: false)
- `image` (string, nullable)
- `original_image` (string, nullable)
- `thumbnails` (array) (default: [])
  - `@type` (string) (default: "Hk01Image")
  - `image` (string, required)
  - `media_id` (integer, nullable)
  - `width` (integer, nullable)
  - `height` (integer, nullable)
  - `caption` (string, nullable)
- `image_count` (integer, nullable)
- `video_count` (integer, nullable)
- `video` (object, nullable)
  - `@type` (string) (default: "Hk01Video")
  - `id` (string, required)
  - `duration` (integer, nullable)
  - `source_type` (string, nullable)
  - `video_type` (string, nullable)
  - `width` (integer, nullable)
  - `height` (integer, nullable)
  - `image` (string, nullable)
- `reactions` (array) (default: [])
  - `@type` (string) (default: "Hk01Reaction")
  - `name` (string, required)
  - `reaction_count` (integer, required)
- `published_at` (integer, nullable)
- `updated_at` (integer, 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.