Skip to content

IMDb Scraper API for Titles, Ratings and Metadata

Collecting public IMDb data usually starts as a small script and turns into a maintenance job: headless browsers, proxy pools, anti-bot challenges and pages that only render after JavaScript runs.

OUTPUT FORMATSHTMLJSONMarkdown

This API takes those pieces off your plate. You send an IMDb URL, the service renders the page in a real browser, rotates the IP and returns a response your code can parse. The sections below cover the three common IMDb jobs, the request parameters that matter, how credits are charged and where the limits actually sit.

Three common IMDb collection jobs

Most IMDb pipelines do one of three things, and the request shape is the same for all of them.

  • Ratings. Pull a title's rating and vote count to track audience response or feed a ranking model.
  • Cast and crew. Collect the people attached to a title to study talent patterns or plan production.
  • Genre lists. Gather genre groupings to see how titles cluster across a catalog.

A single title page carries title, year, cast, plot summary, rating, vote count, runtime, genres and box-office figures, so one request can serve several of these jobs at once.

Request options that change the result

The base call is a URL plus your API key. Four parameters cover most IMDb edge cases:

  • render_js — execute the page's JavaScript before returning it.
  • stealth_proxy — route through a stealth proxy when a page pushes back.
  • country_code — send the request through a residential IP in a chosen country, useful when content varies by geography.
  • ai_extract_rules — describe the fields you want in natural language instead of writing selectors.

For deterministic output, extract_rules maps CSS selectors to field names and returns parsed JSON. ai_extract_rules is the alternative when the page structure is awkward or you would rather describe fields than locate them.

What comes back from an IMDb title page

A title-page response can include:

  • title and release year
  • cast
  • plot summary
  • rating and vote count
  • runtime
  • genres
  • box-office figures

If you need a subset, name only those fields in your extraction rules; the API returns the parsed JSON rather than the raw HTML.

How credits are charged

The plan tooltip states that requests start at one credit each, and the published option costs are listed per successful request:

  • JavaScript rendering: 5 credits
  • Premium proxy without JS rendering: 10 credits
  • Premium proxy with JS rendering: 25 credits
  • stealth_proxy: 75 credits

Credits are valid for one month and do not roll over. New accounts get 1,000 free credits with no card required, and paid plans begin at $19 per month. All prices exclude VAT.

Worked example: costing a small crawl

Suppose you want to refresh 200 IMDb title pages each day with JavaScript rendering on. At 5 credits per successful request, that is 1,000 credits per day, or roughly 30,000 per month. That sits comfortably inside the entry paid tier's 75,000 monthly credits, leaving headroom for retries. If you instead enable stealth_proxy, the published cost for that option is 75 credits per successful request; at the same 200-per-day volume that is 15,000 credits per day, or about 450,000 per month — enough to push you toward a higher tier. The source lists each option's cost separately and does not state how stealth_proxy combines with render_js, so confirm the combined charge for your configuration before scaling volume.

Concurrency limits versus target throttling

These are two different failure modes and they need different fixes.

  • Concurrency limit. The plan caps how many requests can run at once (25 on the entry tier, rising through the tiers). Exceeding it queues or rejects work on your side; the fix is a higher plan or a slower client.
  • Target-side throttling. IMDb itself may slow down aggressive patterns regardless of your plan. The fix is spacing requests out or spreading them across sessions.

There is no per-target rate limit published by the API; the cap is on simultaneous requests.

Languages and SDKs

The service publishes SDKs for Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works for any stack. The documentation includes copy-ready examples in Python, Node.js and cURL plus a request builder, so setup is a matter of pasting a snippet and adding your key.

Decision checklist before you build

Use this to decide whether a managed renderer is the right fit:

  1. Is the data public? Only public IMDb pages are in scope; do not route personal or account data through the pipeline.
  2. Do you need JavaScript? If the fields you want only appear after scripts run, budget for render_js credits.
  3. Does content vary by country? If so, plan for country_code and the residential-IP cost.
  4. How often will you retry? Retries multiply credit use; size your plan against expected retry rate, not just happy-path volume.
  5. Do you need deterministic fields? Prefer extract_rules when you can maintain selectors; use ai_extract_rules when the page changes often.
  6. Do you need screenshots or visual checks? The screenshot option is available and useful for spot-checking rendered pages.
Plan tiers and included limits
PlanMonthly priceAPI creditsConcurrent requestsPriority supportAccount managerTeam management
Hobby$19 /mo75,00025Not includedNot includedNot included
Freelance$49 /mo250,00050Not includedNot includedNot included
Startup (Recommended)$99 /mo1,000,000100Not includedNot includedNot included
Business$249 /mo3,000,000200IncludedIncludedIncluded
Business +$599 /mo8,000,000400IncludedIncludedIncluded
Enterprise 14$999 /mo14,000,000500IncludedIncludedIncluded
Enterprise 24$1,599 /mo24,000,000600IncludedIncludedIncluded
Enterprise 41 (Recommended)$2,399 /mo41,000,000700IncludedIncludedIncluded
Enterprise 69$3,599 /mo69,000,000800IncludedIncludedIncluded
Enterprise 120$5,799 /mo120,000,000900IncludedIncludedIncluded

Prices exclude VAT. Credits are valid for one month and do not roll over. All tiers include JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots and extraction rules.

Per-request credit costs by option
OptionCredits per successful request
JavaScript rendering5
Premium proxy, JS rendering off10
Premium proxy, JS rendering on25
stealth_proxy75

Costs are listed per successful request for each option. The plan tooltip states that requests start at one credit each; the source does not state how options combine, so confirm the total charge for your configuration.

Frequently asked questions

Do I need an IMDb account to use this API?

No. You need an API key from this service, not an IMDb login. Signing up gives you 1,000 free credits with no card required; after that you send the URL and the service handles rendering and proxy rotation.

Can I request IMDb pages as seen from a specific country?

Yes. Set country_code on the request and it routes through a residential IP in that country. This matters when IMDb shows different content or availability by region.

Is there a rate limit per target site?

The published limit is concurrency per plan, not a per-target rate limit. If IMDb throttles aggressive patterns, space requests out or use multiple sessions.

How do I get structured JSON instead of raw HTML?

Pass extract_rules with CSS selectors mapped to field names, or use ai_extract_rules with a natural-language description. The response comes back as parsed JSON.

Which languages can I use?

Any language that can make an HTTP request. SDKs are published for Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works too.

What does it cost to scrape IMDb?

New accounts get 1,000 free credits with no card. Paid plans start at $19 per month. Per-request cost depends on options: 5 credits for JavaScript rendering, 25 for a premium proxy with JS rendering, and 75 for stealth_proxy.