/imdb/titles/reviews

POST /api/imdb/titles/reviews

Price: 5 credits

User reviews of an IMDb title with sorting (helpfulness, newest, top rated, total votes) and optional author-rating and spoiler filters: summary, full text, author, rating, date and helpful votes.

How to use it

Fetch user reviews of an IMDb title by tt-ID or URL. Each review has id, summary, text, author, author_id, rating, submitted_date, up_vote_count, down_vote_count and is_spoiler. Sort by helpfulness, submission date, total votes or user rating; optionally filter by author rating or exclude spoilers. Set count to control how many reviews to return.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• title_id string required — IMDb title ID (e.g. 'tt0111161') or a title URL (examples: "tt0111161", "https://www.imdb.com/title/tt0903747/"; minLength: 1)
• sort string — Review ordering (default: "HELPFULNESS_SCORE"; one of: "HELPFULNESS_SCORE", "SUBMISSION_DATE", "TOTAL_VOTES", "USER_RATING", "SUBMITTER_REVIEW_COUNT")
• sort_order string — Sort direction (default: "DESC"; one of: "ASC", "DESC")
• rating integer nullable — Keep only reviews with this author rating (1-10) (min: 1; max: 10)
• spoilers boolean nullable — Include spoiler reviews; set false to exclude them
• count integer required — Max number of reviews to return (min: 1)

Response

• @type string (default: "ImdbReview")
• id string required
• summary string nullable
• text string nullable
• author string nullable
• author_id string nullable
• rating integer nullable
• submitted_date string nullable
• up_vote_count integer nullable
• down_vote_count integer nullable
• is_spoiler boolean (default: false)

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 — Title not found (well-formed but nonexistent IMDb title 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.