Skip to content

Rotten Tomatoes Scraper API for Movie Ratings Data

A hosted scraping API is useful when you need Rotten Tomatoes movie-page fields on a schedule and do not want to run your own headless browsers or proxy pool.

OUTPUT FORMATSHTMLJSONMarkdown

You send a movie URL, the service renders the page in a real browser, rotates the IP, and returns the response your code can parse. This page explains what the endpoint reads, which request controls change the output, and how the credit rules affect cost.

What the endpoint returns from a Rotten Tomatoes movie page

The scraper targets public movie pages. According to the supplied product description, a single call can return the movie title, Tomatometer score, audience score, cast, runtime, genre and review count. The response can be raw HTML, clean Markdown, or structured JSON when you supply extraction rules. Anything visible on the public page is in scope, but the field list above is the one the product explicitly names. If a field is missing from the response, check whether the page variant you requested actually renders that field before assuming the scraper failed.

Request controls and what each one changes

Four controls matter most for Rotten Tomatoes work. render_js=true runs the page in a headless browser and returns post-render HTML, which is what you want when scores or cast lists load after the initial document. stealth_proxy is the escalation path when a target gets aggressive about blocking; the default already rotates residential proxies and uses a real browser. country_code routes the request through a residential IP in a specific country, which is useful when Rotten Tomatoes shows different content by region. extract_rules takes CSS selectors and returns structured JSON; ai_extract_rules does the same job with natural-language instructions instead of selectors. The dashboard request builder lets you paste a URL, set these parameters, and copy a generated snippet in Python, Node, Go, PHP, Ruby or cURL, so you can test the shape of the response before writing production code.

Credit cost: a decision checklist before you scale

Credits are consumed per successful request, and the optional features multiply the base cost. Use this checklist to estimate a run:

  • Base request: starts at 1 credit.
  • JavaScript rendering enabled: 5 credits per successful request.
  • Premium proxies without JS rendering: 10 credits per successful request.
  • Premium proxies with JS rendering: 25 credits per successful request.
  • Credits are valid for one month and do not roll over.

A typical Rotten Tomatoes movie page needs JavaScript rendering, so budget 5 credits per page unless you also enable premium proxies. If you are collecting 10,000 movie pages a month with JS rendering only, that is 50,000 credits before any retries. The supplied plan table shows the credit allowance for each tier; pick the tier whose allowance covers your monthly page count plus a retry buffer.

Field-to-control map

Use this map to decide which controls you actually need for the fields you care about:

  • Title, Tomatometer score, audience score, runtime, genre, review count: usually present in the rendered HTML, so render_js=true is the main requirement.
  • Cast list: often rendered after the initial document; render_js=true is required, and extract_rules or ai_extract_rules helps isolate the cast block.
  • Audience review text: needs render_js=true plus extraction rules to pull review bodies out of the page.
  • Region-specific content: add country_code when the page differs by market.
  • Blocked responses: escalate to stealth_proxy only after the default rotation fails.

This map reflects the fields the product names and the controls the product documents; it is not a guarantee that every page variant exposes every field.

Telling failures apart

Three failure modes look similar in a log but need different fixes. A blocked request usually returns a challenge page or an error status instead of the movie content; the fix is stealth_proxy or a slower request rate. A missing field usually means the page rendered but the selector did not match; the fix is to inspect the post-render HTML and adjust extract_rules. A field that is present in the browser but absent from the response usually means JavaScript did not run; confirm render_js=true is set on that request. Separating these three before changing parameters saves credits, because each escalation step costs more than the base request.

Example: one movie page to structured JSON

Suppose you want the Tomatometer score, audience score and cast for a single film. Send a GET request with the movie URL, render_js=true, and an extract_rules payload that maps three CSS selectors to three JSON keys. The service renders the page, runs the selectors against the post-render HTML, and returns a JSON object with those three keys. If the cast selector returns empty, switch that one field to ai_extract_rules with a plain-language instruction such as 'return the cast list as an array of actor names' and compare the output. This two-step approach keeps the deterministic fields on selectors and uses AI only where the page structure is unstable.

Common workflows this endpoint supports

Three workflows recur in the supplied product description: fetching movie ratings for content or scheduling decisions, pulling cast lists to study talent trends, and extracting audience reviews for sentiment analysis. Each maps to the same endpoint with different extraction rules. Ratings work is the simplest because the scores are usually in the rendered HTML. Cast work benefits from ai_extract_rules when the cast block changes layout. Review sentiment work needs both rendering and extraction, and is the most sensitive to page structure changes over time.

Setup path

Create an account to get an API key. The supplied product description offers 1,000 free credits to test with and says no credit card is required for that trial. Install the SDK for your stack, or use cURL, and send a GET request with the target URL and your key. The dashboard request builder is the fastest way to confirm the response shape before writing code. Code samples are available for Python, Node.js, Ruby, PHP, Go and cURL.

Plan comparison

The table below reproduces the plan tiers, credit allowances, concurrency limits and feature availability exactly as supplied. Prices are monthly and exclusive of VAT. Treat the figures as a dated reference and confirm current pricing before committing to a tier.

Plan tiers, credits and features
PlanPrice /moAPI CreditsConcurrent requestsJavaScript renderingRotating & Premium ProxiesGeotargetingScreenshots & Extraction RulesPriority Email SupportDedicated Account ManagerTeam Management
Hobby$1975,00025IncludedIncludedIncludedIncludedNot includedNot includedNot included
Freelance$49250,00050IncludedIncludedIncludedIncludedNot includedNot includedNot included
Startup (Recommended)$991,000,000100IncludedIncludedIncludedIncludedNot includedNot includedNot included
Business$2493,000,000200IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Business +$5998,000,000400IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 14$99914,000,000500IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 24$1,59924,000,000600IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 41 (Recommended)$2,39941,000,000700IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 69$3,59969,000,000800IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 120$5,799120,000,000900IncludedIncludedIncludedIncludedIncludedIncludedIncluded

Prices are monthly, exclusive of VAT, and reflect the supplied product page. Confirm current pricing before purchase.

Frequently asked questions

What data can I extract from Rotten Tomatoes?

Whatever is visible on the public page is fair game. To get structured JSON back, choose one of two routes: extract_rules, where you supply CSS selectors yourself, or ai_extract_rules, where you describe the data in plain language and AI finds it. The named fields the product reads are title, Tomatometer score, audience score, cast, runtime, genre and review count.

How do I get started scraping Rotten Tomatoes?

Sign up, grab your API key, and send a GET request with the target URL. The service renders the page, rotates proxies, and returns the data. The supplied product description offers 1,000 free credits to test with.

Will I get blocked when scraping Rotten Tomatoes?

The default request rotates residential proxies and uses a real headless browser, so traffic looks like a normal visit. If a target gets aggressive, enable stealth_proxy on that request.

Can I scrape Rotten Tomatoes without writing code?

Yes. The dashboard request builder lets you paste a URL, set parameters, and copy the generated snippet in Python, Node, Go, PHP, Ruby or cURL.

How do I handle JavaScript when scraping Rotten Tomatoes?

Pass render_js=true on the request. The page runs in a real headless browser, the JavaScript executes server-side, and the post-render HTML is returned.

Can I scrape Rotten Tomatoes from a specific country?

Yes. Pass country_code on the request to route through a residential IP in that country. This is useful when content varies by geo.