/cninfo/announcements

POST /api/cninfo/announcements

Price: 10 credits

Resolve one CNINFO announcement id to its disclosure file: the PDF link (an HTML page for some announcements up to 2003), file type and publication day

How to use it

Returns the file link and day; for announcements whose file is an HTML page or an image it also returns the title, company, exact publication time, board and category codes, and the page text. For the rest, the title, company and category come with the announcement's row in cninfo/announcements/search or cninfo/companies/announcements.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• announcement string required — CNINFO announcement id or announcement URL (examples: "1225475868", "https://www.cninfo.com.cn/new/disclosure/detail?stockCode=300750&announcementId=1225475868"; minLength: 1)

Response

• @type string (default: "CninfoAnnouncementFile")
• id string required
• url string required
• pdf_url string required
• published_date integer nullable
• file_type string nullable
• published_at integer nullable
• company_code string nullable
• company_name string nullable
• org_id string nullable
• board string nullable
• board_code string nullable
• type_codes array (default: [])
• column_codes array (default: [])
• text string nullable

Errors

• 422 — announcement is not a CNINFO announcement id or URL 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 announcement under that id 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.