/kinopoisk/persons

POST /api/kinopoisk/persons

Price: 10 credits

Get full Kinopoisk person details by ID or URL: names (ru/original), gender, photo, professions, birth/death dates and places, age, height, zodiac, main genres and acting/crew roles.

How to use it

Fetch a single Kinopoisk person (actor/director/etc.) by numeric ID or a name URL. Returns one item with name/original_name, gender, image (photo), job_titles, birth_date/death_date, age, birth_place/death_place, height, zodiac_sign, main_genres, filmography_year_start/end and roles (slug/title/movie_count).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• person string required — Kinopoisk person ID (e.g. '9144') or full person URL (examples: "9144", "https://www.kinopoisk.ru/name/9144/"; minLength: 1)

Response

• @type string (default: "KinopoiskPerson")
• id integer required
• url string required
• name string nullable
• original_name string nullable
• gender string nullable
• image string nullable
• job_titles array (default: [])
• birth_date string nullable
• death_date string nullable
• age integer nullable
• birth_place string nullable
• death_place string nullable
• height integer nullable
• zodiac_sign string nullable
• main_genres array (default: [])
• filmography_year_start integer nullable
• filmography_year_end integer nullable
• roles array (default: [])
  • @type string (default: "KinopoiskPersonRole")
  • slug string required
  • movie_count integer nullable

Errors

• 422 — 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 — Person not found (well-formed but nonexistent person 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.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-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.