POST /api/kr36/investors/investments
Price: 5 credits
List the startup investments of one 36Kr investor, newest first: the startup, its industries, the round, month, amount and the news report. Returns at most 1,000 investments per investor
Pass a row's `project_id` to kr36/projects for the startup's profile.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)investor string required — 36Kr investor id or URL (examples: "1713096318380553", "https://pitchhub.36kr.com/organization/1713096318380553")count integer required — Max number of investments to return (min: 1; max: 1000)@type string (default: "Kr36Investment")investor_id string nullableproject_id string nullableproject_name string nullableproject_url string nullableproject_image string nullableproject_tagline string nullableindustries array (default: [])round string nullablecurrent_round string nullablefunded_year integer nullablefunded_month integer nullableamount string nullablenews_url 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 — No investor with that id 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.