POST /api/bse/announcements/search
Price: 1 credit
Search announcements published on the Beijing Stock Exchange by its listed companies: by title keyword, company, publication window and category (periodic reports, interim announcements, resolutions, dividends, buybacks, offerings and more). Each row is the announcement's id, title, publication day, company, type codes and PDF link.
Newest first. For one company's complete filing history use bse/companies/announcements.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)count integer required — Max number of announcements to return (min: 1; max: 5000)keyword string nullable — Words to find in announcement titles (examples: "年度报告", "回购"; minLength: 1)company string nullable — Six-digit stock code of the company (examples: "920021"; minLength: 1)published_from integer nullable — Earliest publication day, as unix seconds; day-granular (examples: 1767225600)published_to integer nullable — Latest publication day, as unix seconds; day-granular (examples: 1790812800)categories array nullable — Announcement categories to keep (one of: "periodic_reports", "interim_announcements", "annual_report", "interim_report", "q1_report", "q3_report", "earnings_forecasts", "public_offering", "board_resolutions", "supervisory_board_resolutions", "shareholder_meeting_resolutions", "dividends", "equity_incentives", "employee_stock_plans", "use_of_proceeds", "share_buybacks", "operations"; minItems: 1)@type string (default: "BseDisclosure")id string requiredpdf_url string nullablefile_format string nullablepublished_date integer nullableupdated_at integer nullablecompany_code string nullablecompany_name string nullabletype_code string nullablesubtype_code string nullablerevision_count integer nullable422 — company is not a six-digit code, published_to is before published_from, or an unknown category 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.