POST /api/kr36/investors/search
Price: 1 credit
Search 36Kr's investor directory (VC, PE, CVC, angel and other funds) by name, type, industry and founding year: name, type, location, number of investments, capital under management and latest investment. Returns at most 1,000 investors per filter combination
Each filter combination yields at most 1,000 investors, so narrow by type or industry to reach more. Pass a row's `id` to kr36/investors for the profile and kr36/investors/investments for its portfolio.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)count integer required — Max number of investors to return (min: 1; max: 1000)query string nullable — Investor name to search for; omitted for every investor (examples: "红杉", "高瓴"; minLength: 1)types array — Investor types; any of them matches (default: []; one of: "angel", "vc", "pe", "cvc", "fa", "lp", "incubator", "fund_of_funds", "government_guidance_fund", "other")industries array — Industries invested in; 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")founded_years array — Founding years; any of them matches, 2010 stands for 2010 and earlier (default: []; examples: [2015])@type string (default: "Kr36InvestorRow")id string requiredurl string nullablename string nullableimage string nullabletypes array (default: [])location string nullablefounded_year integer nullableinvestment_count integer nullablemanaged_capital string nullablelatest_project_name 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.