/xinhua/sections/articles

POST /api/xinhua/sections/articles

Price: 20 credits

List the articles of a Xinhua channel or list page in the channel's own order: headline, summary, publication time, author, editors, source, keywords, images, video file, follow-up links and URL

How to use it

https://english.news.cn/list/latestnews.htm is the English wire's latest-news list. Pass a row url to xinhua/articles for the full text.

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 articles to return (min: 1; max: 1000)
• section string required — Xinhua channel or list page URL (examples: "https://english.news.cn/list/latestnews.htm", "https://english.news.cn/china/index.htm", "https://www.news.cn/world/index.html", "https://www.news.cn/politics/index.html"; minLength: 1)

Response

• @type string (default: "XinhuaSectionArticle")
• id string required
• entry_id string nullable
• url string required
• summary string nullable
• subtitle string nullable
• published_at integer nullable
• author string nullable
• editor string nullable
• responsible_editor string nullable
• source string nullable
• source_url string nullable
• keywords array (default: [])
• image string nullable
• images array (default: [])
• video_url string nullable
• entry_type string nullable
• cnml_id string nullable
• xhs_doc_id string nullable
• linked_articles array (default: [])
  • @type string (default: "XinhuaLinkedArticle")
  • url string required
• section_id string nullable
• section_name string nullable

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 — No article list at that URL 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.