/imdb/names

POST /api/imdb/names

Price: 1 credit

Get full IMDb person details by ID or URL: name, birth name, nicknames, birth/death dates and places, height, biography, photo, popularity rank, professions, awards summary, known-for titles and spouses.

How to use it

Fetch a single IMDb person by nm-ID or name URL. Returns one item with name, birth_name, nicknames, birth_date, death_date, death_cause, birth_location, death_location, height_cm, bio, image, meter_rank, professions, award_summary, known_for (titles) and spouses. Optional country/language set the display locale.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• name string required — IMDb person ID (e.g. 'nm0000209') or a name URL (examples: "nm0000209", "https://www.imdb.com/name/nm0000151/"; minLength: 1)
• country string nullable — ISO country code for localized display
• language string nullable — Locale for localized display

Response

• @type string (default: "ImdbName")
• id string required
• url string required
• name string nullable
• birth_name string nullable
• nicknames array (default: [])
• birth_date string nullable
• death_date string nullable
• death_cause string nullable
• birth_location string nullable
• death_location string nullable
• height_cm number nullable
• bio string nullable
• image string nullable
• image_caption string nullable
• meter_rank integer nullable
• professions array (default: [])
• award_summary object nullable
  • @type string (default: "ImdbAwardSummary")
  • name string nullable
  • wins integer nullable
  • nominations integer nullable
• known_for array (default: [])
  • @type string (default: "ImdbTitleRef")
  • id string required
  • title_text string required
  • url string nullable
  • type_id string nullable
  • year integer nullable
  • rating number nullable
  • vote_count integer nullable
  • image string nullable
• spouses array (default: [])
  • @type string (default: "ImdbSpouse")
  • name string nullable
  • name_id string nullable
  • current boolean (default: false)
  • attributes array (default: [])

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 IMDb 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.