POST /api/kr36/funding_events/search
Price: 1 credit
Search 36Kr's database of startup funding rounds, newest first, by industry, round, year, currency and region: the startup, round, date, amount and investors. Returns at most 1,000 events per filter combination
Each filter combination yields at most 1,000 events, so split a broad request by year or round to reach more. Pass `project_id` to kr36/projects for the startup's full funding history.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)count integer required — Max number of funding events to return (min: 1; max: 1000)industries array — Industries of the funded startup; any of them matches (default: []; one of: "culture_entertainment", "consumer_ecommerce", "automotive_mobility", "education", "finance", "enterprise_services", "industrial_upgrading", "frontier_technology", "healthcare", "advanced_manufacturing", "telecom_semiconductors", "iot_hardware", "software_tools", "social_networks", "agriculture", "energy_environment", "local_services", "sports_gaming", "cross_border", "real_estate", "travel", "advertising_marketing", "smart_hardware", "logistics", "blockchain", "traditional_manufacturing", "metaverse", "other")rounds array — Funding rounds; any of them matches (default: []; one of: "unfunded", "seed", "angel", "pre_a", "a", "a_plus", "pre_b", "b", "b_plus", "c", "c_plus", "d", "d_plus", "e", "f", "g", "h", "equity", "strategic", "private_placement", "pre_ipo", "cornerstone", "listed", "ipo", "neeq", "delisted", "acquisition", "other")years array — Years the round closed; any of them matches, 2010 stands for 2010 and earlier (default: []; examples: [2024])currencies array — Currencies of the round; any of them matches (default: []; one of: "cny", "usd", "hkd", "eur", "gbp", "inr", "jpy", "other")provinces array — Province of the funded startup; any of them matches (default: []; one of: "anhui", "beijing", "chongqing", "fujian", "gansu", "guangdong", "guangxi", "guizhou", "hainan", "hebei", "heilongjiang", "henan", "hong_kong", "hubei", "hunan", "inner_mongolia", "jiangsu", "jiangxi", "jilin", "liaoning", "macau", "ningxia", "qinghai", "shaanxi", "shandong", "shanghai", "shanxi", "sichuan", "taiwan", "tianjin", "tibet", "xinjiang", "yunnan", "zhejiang")location string nullable — Startups based in China or overseas; omitted for both (one of: "china", "overseas")@type string (default: "Kr36FundingEvent")project_id string nullableproject_name string nullableproject_url string nullableproject_image string nullableproject_tagline string nullableindustries array (default: [])round string nullablefunded_date integer nullableamount string nullableinvestors_text string nullable422 — 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.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.