/imdb/charts

POST /api/imdb/charts

Price: 5 credits

IMDb charts: Top 250 movies, Top 250 TV, Top 250 English/India, Bottom 100, regional Top 50 lists and the most-popular MOVIEmeter/TVmeter rankings. Returns ranked titles with position and ratings.

How to use it

Fetch an IMDb chart by its enum (e.g. top250_movies, top250_tv, bottom100, moviemeter, tvmeter). Each entry has position, id, url, title_text, type_id, year, rating, vote_count, chart_rating, chart_vote_count and image. Set count to control how many titles to return.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• chart string required — Which IMDb chart to fetch (one of: "top250_movies", "top250_tv", "top_english_movies", "top250_india", "bottom100", "top50_tamil", "top50_telugu", "top50_malayalam", "top50_bengali", "moviemeter", "tvmeter")
• count integer required — Max number of titles to return (min: 1)

Response

• @type string (default: "ImdbChartEntry")
• position integer nullable
• id string required
• url string required
• title_text string nullable
• original_title string nullable
• type_id string nullable
• type_name string nullable
• year integer nullable
• rating number nullable
• vote_count integer nullable
• chart_rating number nullable
• chart_vote_count integer nullable
• runtime_minutes 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 — 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.