/tmdb/people

POST /api/tmdb/people

Price: 5 credits

Get full TMDB person details by ID or URL: name, also known as, gender, known-for department, birthday/deathday, place of birth, biography, photo, external links and full filmography credits.

How to use it

Fetch a single TMDB person (actor/director/crew) by numeric ID or person URL. Returns one item with name, also_known_as, gender, known_for_department, known_credits, birthday, deathday, place_of_birth, biography, job_titles, image (photo), homepage and social links, and credits (full filmography: each with id, media_type, department, document_title, year, role and url). Use language to localize the biography.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• language string — Localization language for titles, overviews and biographies. (default: "en-US"; one of: "ar-SA", "bg-BG", "ca-ES", "cs-CZ", "da-DK", "de-AT", "de-DE", "el-GR", "en-US", "es-ES", "es-MX", "et-EE", "eu-ES", "fa-IR", "fi-FI", "fr-CA", "fr-FR", "he-IL", "hi-IN", "hr-HR", "hu-HU", "hy-AM", "id-ID", "is-IS", "it-IT", "ja-JP", "ka-GE", "kk-KZ", "ko-KR", "lt-LT", "lv-LV", "ml-IN", "nb-NO", "nl-NL", "no-NO", "pl-PL", "pt-BR", "pt-PT", "ro-RO", "ru-RU", "sk-SK", "sl-SI", "sr-RS", "sv-SE", "th-TH", "tr-TR", "uk-UA", "uz-UZ", "vi-VN", "zh-CN", "zh-HK", "zh-TW")
• person string required — TMDB person ID (e.g. '3084') or a person URL (examples: "3084", "https://www.themoviedb.org/person/3084-marlon-brando"; minLength: 1)

Response

• @type string (default: "TmdbPerson")
• id integer required
• url string required
• name string nullable
• also_known_as array (default: [])
• gender string nullable
• known_for_department string nullable
• known_credits integer nullable
• birthday string nullable
• deathday string nullable
• place_of_birth string nullable
• biography string nullable
• job_titles array (default: [])
• image string nullable
• homepage string nullable
• facebook string nullable
• twitter string nullable
• instagram string nullable
• credits array (default: [])
  • @type string (default: "TmdbCredit")
  • id integer required
  • media_type string required
  • department string nullable
  • document_title string nullable
  • year integer nullable
  • role string nullable
  • url string 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.