IMDb Scraper — Titles, Cast, Ratings, Reviews & Search

What is IMDb Scraper for Titles, People, Reviews, Search, and Discovery?

Turn IMDb title IDs, person IDs, public URLs, keywords, or discovery filters into structured dataset records for entertainment research, catalog enrichment, audience analysis, and AI workflows. Each result represents a title, person, or review and can include canonical IMDb identity, ratings, votes, cast, genres, plot, review text, and image URLs.

Best fit for this Actor

Choose this Actor when a workflow begins with IMDb identifiers, public IMDb URLs, title or person names, or a discovery brief based on genre, title type, release year, and rating. Its automatic mode is designed for mixed input lists and routes each value to the matching title, person, or search workflow.

Focused standalone workflow

This Actor is designed as a focused standalone workflow for IMDb title, person, search, discovery, and review data through one consistent input and dataset contract.

A practical catalog scenario

A streaming catalog analyst starts with a mixed list of IMDb title IDs and film names. The Actor resolves the inputs, returns canonical IDs, titles, release years, ratings, genres, directors, stars, plots, and image URLs, and the analyst then joins those records to an internal catalog for enrichment and editorial review.

Quick start input

Use auto for a mixed list of IDs, URLs, names, and keywords.

{
  "queries": ["tt1375666", "nm0000138", "Breaking Bad"],
  "mode": "auto",
  "maxResults": 10
}

Discovery mode uses the filter fields as a research brief:

{
  "mode": "discover",
  "genres": ["Sci-Fi"],
  "titleType": "movie",
  "minRating": 7,
  "sortBy": "RATING",
  "maxResults": 10
}

What data you receive

Field	Meaning
type	Dataset entity: title, person, or review
id, url	IMDb identifier and canonical public URL
title, name, year, titleType	Title or person identity fields
rating, votes, certificate, runtimeMinutes	Public title metrics and classification
plot, genres, directors, stars	Editorial and credit fields
authorRating, reviewText	Public review fields on review records
imageUrl	Primary public poster or profile image

{
  "type": "title",
  "id": "tt1375666",
  "url": "https://www.imdb.com/title/tt1375666/",
  "title": "Inception",
  "year": 2010,
  "titleType": "Movie",
  "rating": 8.8,
  "genres": ["Action", "Sci-Fi"],
  "directors": ["Christopher Nolan"],
  "imageUrl": "https://m.media-amazon.com/images/example.jpg"
}

Run through the Apify API

curl -X POST "https://api.apify.com/v2/acts/khadinakbar~imdb-scraper/runs" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"queries":["tt1375666","Christopher Nolan"],"mode":"auto","maxResults":10}'

Read the run's default dataset for the structured records.

Use with AI agents through Apify MCP

Example prompt:

Research these IMDb titles and people. Return canonical IDs, URLs, title or person names, ratings, genres, directors, stars, and image URLs. Read the dataset after completion and preserve IMDb URLs as source provenance.

Give the agent the mode, query list, and result scope. Ask it to read the dataset, group records by type, retain canonical URLs, and summarize the outcome with the collection cost shown by Apify.

Pricing

Startup billing and empty runs

The apify-actor-start event costs $0.00005 per startup unit. Apify charges one startup unit per GB of allocated memory, with a minimum of one unit, so a 2 GB run incurs two units. This startup charge still applies when input is invalid, no results are found, or an upstream request fails. Statements about free, unbilled, or skipped results refer only to the corresponding result event; they do not waive the startup charge. Apify platform usage is included in the event prices and is not passed through as an additional customer charge. Check the live Pricing tab for current events, tiers, and rates. Result limits cap result events, not the entire run cost.

This Actor uses Pay per event with Apify platform usage included. Title, person, search, discovery, and review records use the events configured for the Actor. Open the live Pricing tab for current billing details and use maxResults or Apify run cost controls to keep the scope aligned with your budget.

Best results

Provide canonical IMDb IDs when identity precision matters, use auto for mixed research lists, and choose discover for a focused genre or title-type brief. Keep maxResults aligned with the decision you plan to make from the dataset.

Builder's note

I designed automatic input routing because IMDb research often begins with a mixed collection of title IDs, person IDs, URLs, and names. A single normalized contract makes that mixed research easier to call from an agent and easier to join downstream.

Responsible use

Collect public data you are authorized to access and follow applicable laws, IMDb terms, and your organization's data-use requirements.