/xinhua/articles/search

POST /api/xinhua/articles/search

Price: 1 credit

Search Xinhua news articles by keyword in one language edition, newest first or by relevance, in the full text or the headline only, with optional any-of words, excluded words and a site restriction; each result has headline, summary, image, publication time, site name and URL

How to use it

Pass a result 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: 500)
• keyword string required — Words to search for (examples: "china", "经济"; minLength: 1)
• language string — Language edition to search (default: "zh"; one of: "zh", "en", "fr", "es", "ru", "ar", "de", "ja", "ko")
• search_in string — Where the keyword must appear (default: "full_text"; one of: "full_text", "headline")
• sort string — Result order (default: "newest"; one of: "newest", "relevance")
• any_keywords string nullable — Space-separated words of which at least one must appear (examples: "cool")
• exclude_keywords string nullable — Space-separated words that must not appear (examples: "亚运")
• site string nullable — Only articles whose address contains this host or path (examples: "english.news.cn")

Response

• @type string (default: "XinhuaSearchArticle")
• id string required
• url string required
• summary string nullable
• image string nullable
• published_at integer nullable
• site_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 — 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.