/imdb/names/search

POST /api/imdb/names/search

Price: 1 credit

Advanced IMDb people search with filters: name keyword, birth and death date ranges, birthday, gender, titles credited in, and adult-content handling, with sorting.

How to use it

Search IMDb people by name and/or filters (birth_date_from/to, birthday, death_date_from/to, gender, credits, adult) and sort the results. Each result has id, url, name, image, professions and known_for titles. Set count to control how many results to return.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string nullable — Person name to search for
• birth_date_from string nullable — Earliest birth date (YYYY-MM-DD or YYYY)
• birth_date_to string nullable — Latest birth date (YYYY-MM-DD or YYYY)
• birthday string nullable — Born on this day of the year (MM-DD)
• death_date_from string nullable — Earliest death date (YYYY-MM-DD or YYYY)
• death_date_to string nullable — Latest death date (YYYY-MM-DD or YYYY)
• gender array nullable — Gender identities to include (one of: "MALE", "FEMALE", "NON_BINARY", "OTHER")
• credits array nullable — Person appears in these title IDs (tt-IDs)
• adult string nullable — How to treat adult content (one of: "EXCLUDE_ADULT", "INCLUDE_ADULT", "ONLY_ADULT")
• sort string — Result ordering (default: "POPULARITY"; one of: "POPULARITY", "NAME", "LAST_NAME", "BIRTH_DATE", "DEATH_DATE", "RELEVANCE")
• sort_order string — Sort direction (default: "ASC"; one of: "ASC", "DESC")
• country string nullable — ISO country code for localized display
• language string nullable — Locale for localized display
• count integer required — Max number of results to return (min: 1)

Response

• @type string (default: "ImdbNameSearchResult")
• id string required
• url string required
• name string nullable
• image string nullable
• professions array (default: [])
• known_for array (default: [])
  • @type string (default: "ImdbNameSearchTitleRef")
  • id string required
  • title_text string required
  • year 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 — 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.

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.