/cninfo/companies/announcements

POST /api/cninfo/companies/announcements

Price: 1 credit

List one listed company's announcements and filings on CNINFO — periodic reports, board and shareholder meeting notices, financing, equity changes and more — by title keyword, publication window and category, each with title, publication time and PDF link

How to use it

Without dates the whole archive back to 1995 is searched, newest first. `kind=investor_relations` lists the company's investor-relations activity records instead of announcements.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• company string required — A-share stock code or CNINFO company page URL (examples: "300750", "600519", "https://www.cninfo.com.cn/new/disclosure/stock?stockCode=300750&orgId=GD165627"; minLength: 1)
• count integer required — Max number of announcements to return (min: 1; max: 3000)
• keyword string nullable — Words to find in announcement titles (examples: "年度报告"; minLength: 1)
• published_from integer nullable — Earliest publication day, as unix seconds; day-granular (examples: 1735689600)
• published_to integer nullable — Latest publication day, as unix seconds; day-granular (examples: 1790812800)
• kind string — Kind of disclosure (default: "announcements"; one of: "announcements", "investor_relations", "sponsor_supervision")
• categories array nullable — Announcement categories to keep (one of: "annual_report", "semi_annual_report", "q1_report", "q3_report", "earnings_forecast", "dividend_distribution", "board_of_directors", "supervisory_board", "shareholders_meeting", "daily_operations", "corporate_governance", "intermediary_report", "ipo", "secondary_offering", "equity_incentive", "rights_issue", "lock_up_expiry", "corporate_bond", "convertible_bond", "other_financing", "equity_change", "correction", "clarification", "risk_warning", "special_treatment_delisting", "delisting_arrangement_period"; minItems: 1)
• sort string — Result order (default: "newest"; one of: "newest", "oldest")

Response

• @type string (default: "CninfoAnnouncement")
• id string required
• short_title string nullable
• url string nullable
• pdf_url 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: [])
• file_type string nullable
• file_size_kb integer nullable

Errors

• 422 — company is not a six-digit stock code, or categories given with a kind other than announcements 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 listed company under that stock code 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.