POST /api/bse/companies/search
Price: 1 credit
List the companies listed on the Beijing Stock Exchange by stock code, CSRC industry division and province: code, short and English names, ISIN, industry, region, listing date, total and float shares, sponsor broker, trading mode and the day's price limits
Matches stock codes only, not names. Industry codes are CSRC divisions such as C36 (automobile manufacturing). Pass `company_code` to bse/companies for the profile.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)count integer required — Max number of companies to return (min: 1; max: 400)stock_code string nullable — Six-digit stock code to match (examples: "920021"; pattern: ^\d{6}$)industry_codes array nullable — CSRC industry division codes (examples: ["C36"], ["C36","C35"]; minItems: 1)regions array nullable — Provinces of the companies (one of: "beijing", "tianjin", "hebei", "shanxi", "inner_mongolia", "liaoning", "jilin", "heilongjiang", "shanghai", "jiangsu", "zhejiang", "anhui", "fujian", "jiangxi", "shandong", "henan", "hubei", "hunan", "guangdong", "guangxi", "hainan", "chongqing", "sichuan", "guizhou", "yunnan", "tibet", "shaanxi", "gansu", "qinghai", "ningxia", "xinjiang"; minItems: 1)sort string — Result order (default: "code"; one of: "code", "listed_newest", "listed_oldest")@type string (default: "BseListedCompany")company_code string requiredname string nullablename_en string nullableisin string nullableindustry string nullableregion string nullablelisted_date integer nullableneeq_listed_date integer nullabletotal_shares integer nullablefloat_shares integer nullablesponsor_broker string nullabletransfer_mode string nullablelimit_up_price_cny number nullablelimit_down_price_cny number nullableas_of_date integer nullable422 — stock_code is not six digits, an industry code is not a CSRC division, or an unknown region 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.