/hk01/zones

POST /api/hk01/zones

Price: 1 credit

List the HK01 (香港01) site navigation: every top-level zone (港聞, 娛樂, 體育, 國際, 中國, 經濟, 健康, 教育 …) with its id, name, URL and the channels published under it. Use it to discover the zone and channel values accepted by hk01/zones/articles and hk01/categories/articles.

How to use it

Directory of HK01 zones and their channels, taken from the live site navigation. Each zone has id, name, menu_label (the shorter wording the site prints in its navigation bar, when it differs), web_url and channels[] with channel id/name/menu_label/web_url. Feed a channel id into hk01/categories/articles, or a zone name into hk01/zones/articles.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of zones to return (min: 1)
• locale string — Host used to build the returned URLs (default: "zh-HK"; one of: "zh-HK", "zh-CN")

Response

• @type string (default: "Hk01Zone")
• id integer required
• name string required
• menu_label string nullable
• web_url string required
• channels array (default: [])
  • @type string (default: "Hk01ZoneChannel")
  • id integer required
  • name string required
  • menu_label string nullable
  • web_url string required

Errors

• 422 — The request body did not validate 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 — The entity was not found, or a precondition failed 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.