/rottentomatoes/celebrities

POST /api/rottentomatoes/celebrities

Price: 10 credits

Get a Rotten Tomatoes celebrity by slug or URL: name, photo, birthday, birthplace, highest/lowest rated titles, biography and full filmography (movies and TV) with per-title scores, credits and roles.

How to use it

Fetch a single Rotten Tomatoes celebrity by slug (from /celebrity/{slug}) or URL. Returns one item with name, image, birthday, birthplace, highest_rated, lowest_rated, bio and filmography (each with work_title, slug, url, media_type, year, credits, characters, tomatometer, popcornmeter, image). Use filmography_type to restrict to movies or TV, filmography_sort to order and filmography_count for depth.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• celebrity string required — Rotten Tomatoes celebrity slug or full celebrity URL (examples: "timothee_chalamet", "https://www.rottentomatoes.com/celebrity/timothee_chalamet"; minLength: 1)
• filmography_type string nullable — Restrict filmography to movies or TV; omit to include both (one of: "movie", "tv")
• filmography_sort string — Filmography ordering (default: "newest"; one of: "newest", "oldest", "critic_highest")
• filmography_count integer — Max number of filmography credits to include (default: 50; min: 1; max: 1000)

Response

• @type string (default: "RottentomatoesCelebrity")
• id string nullable
• media_type string (default: "celebrity")
• slug string required
• url string required
• name string nullable
• image string nullable
• birthday string nullable
• birthplace string nullable
• highest_rated string nullable
• lowest_rated string nullable
• bio string nullable
• filmography array (default: [])
  • @type string (default: "RottentomatoesFilmographyItem")
  • work_title string nullable
  • slug string nullable
  • url string nullable
  • media_type string nullable
  • year string nullable
  • credits string nullable
  • characters string nullable
  • tomatometer integer nullable
  • popcornmeter integer nullable
  • image 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 — Celebrity not found (well-formed but nonexistent slug) 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.