Skip to content

Google Showtimes Results as Structured JSON

Google Showtimes pages are useful for cinema listings, theater addresses and schedule checks, but they are rendered client-side and change often.

OUTPUT FORMATSHTMLJSONMarkdown

This page explains how a managed scraping API turns a public Showtimes URL into structured JSON, which request parameters control rendering, proxies and geo-routing, and what each capability costs in API credits.

What a Showtimes request returns

A single request to a public Google Showtimes URL can return the movie title, theater name, theater address, the list of showtimes, the booking URL and the movie rating. You choose the output shape: raw post-render HTML, or structured JSON produced by CSS/XPath extraction rules or by AI-driven extraction rules.

Typical uses fall into three patterns:

  • Cinema listings — collect structured listings to compare what is playing where.
  • Theater locations — capture addresses for logistics or regional planning.
  • Schedule checks — re-request the same page to see how showtimes change over time.

Because the underlying page is rendered by JavaScript, a plain HTTP fetch usually returns an empty shell. The API runs the page in a real headless browser, executes the scripts server-side, and returns the post-render HTML.

Request parameters and what each one changes

The API accepts a target URL plus optional parameters. The table below maps the parameter to the behavior it controls and the credit cost it triggers. Credit costs are per successful request and stack according to the rules shown.

A worked example: one Showtimes request with render_js enabled and stealth_proxy on costs 25 credits. The same request with render_js off and stealth_proxy on costs 10 credits. A request with only render_js enabled costs 5 credits. Base requests start at 1 credit each.

Credit rules you should know before sizing a job

Two rules shape how many requests a plan actually supports:

  1. Credits expire monthly. API credits are valid for one month and do not roll over. A plan sized for a busy release week cannot bank unused credits for a quiet month.
  2. Costs stack by capability. A request that only fetches HTML starts at 1 credit. Enabling JS rendering adds 5. Enabling premium proxies adds 10 (without JS) or 25 (with JS). The total for a request is the sum of the capabilities it uses.

For a schedule-monitoring job, the practical sizing question is: how many URLs per day, times how many credits per request, times the days in the month. A job that requests 1,000 Showtimes URLs daily with JS rendering enabled consumes roughly 5,000 credits per day, or about 150,000 per 30-day month — before any premium-proxy uplift.

Plan tiers and what changes between them

Plans differ on three axes: monthly credit allowance, concurrent request limit, and support/team features. JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots/extraction rules are included from the entry tier upward. Priority email support, a dedicated account manager and team management appear only from the Business tier.

Should you use a managed API or run your own browser fleet?

Use this checklist to decide before you build.

  • You need JavaScript rendering. Google Showtimes pages are client-rendered. If you cannot run a headless browser, a managed API removes that dependency.
  • You need proxy rotation. If your target rate is high enough that a single IP gets throttled, rotating residential proxies matter.
  • You need geo-routing. If showtimes differ by country, you need a way to route requests through an IP in that country.
  • You need structured output. If you want JSON rather than raw HTML, extraction rules or AI extraction save you a parsing layer.
  • You are willing to pay per request. Managed APIs charge credits per request; self-hosted browsers cost engineering time and infrastructure instead.

If most of those boxes are unchecked, a self-hosted headless browser may be cheaper. If most are checked, a managed API removes the operational burden.

Three failure modes that look the same but are not

A request that returns no showtimes can fail for three different reasons. Diagnose before you change parameters.

  1. JavaScript not rendered. The page returned HTML but the showtimes block is empty. Fix: enable render_js.
  2. Bot blocking. The request is challenged or returns a CAPTCHA page. Fix: enable stealth_proxy.
  3. Geo-restricted content. The page loads but shows the wrong region's listings, or none. Fix: pass country_code for the target country.

Each fix has a different credit cost, so identifying the actual failure first avoids paying for capabilities you do not need.

Getting from a URL to a JSON record

The workflow has four steps. Each step below is a generic account-setup pattern; the exact free-credit allowance and any trial terms depend on the current plan documentation, so treat the credit figure as a placeholder to confirm before you rely on it for budgeting. A worked example: if a plan grants a fixed number of trial credits, divide that number by the per-request credit cost to estimate how many test requests you can make before the allowance runs out. For instance, a request with JS rendering enabled costs 5 credits, so a 1,000-credit allowance would cover roughly 200 such requests — but confirm the actual allowance on the current pricing page rather than assuming this figure applies here. The four steps are: 1. Create an account. You receive an API key and whatever trial credits the current plan provides. 2. Pick a client. Python, Node, Go, PHP, Ruby and cURL are supported. Each Showtimes scrape becomes a single function call; there is no proxy rotation or headless Chrome to manage. 3. Send the request. Pass the target Google Showtimes URL and your API key. The API renders the page, handles bot bypass, and returns parsed HTML or structured JSON. 4. Add parameters as needed. Use render_js for JavaScript, stealth_proxy for aggressive targets, country_code for geo-targeting, and extract_rules or ai_extract_rules for structured extraction. If you prefer not to write code, the dashboard request builder lets you paste a URL, set parameters, and copy a generated snippet in any of the supported languages.

Request parameters and credit impact
ParameterWhat it changesCredit impact
render_jsRuns the page in a headless browser and returns post-render HTML5 credits per successful request when enabled
stealth_proxyRoutes through premium proxies for aggressive targets10 credits (JS off) or 25 credits (JS on) per successful request
country_codeRoutes through a residential IP in the chosen countryNo separate credit line shown
extract_rulesCSS or XPath selectors that pull structured fieldsUses the extraction capability
ai_extract_rulesNatural-language extraction rules for structured JSONUses the AI extraction capability
screenshotCaptures a full-page screenshotUses the screenshot capability

Credit costs are per successful request and stack by capability. Base requests start at 1 credit each. Credits are valid for one month and do not roll over.

Plan tiers and included features
TierMonthly priceAPI creditsConcurrent requestsPriority support / account manager / team management
Hobby$19/mo75,00025Not included
Freelance$49/mo250,00050Not included
Startup$99/mo1,000,000100Not included
Business$249/mo3,000,000200Included
Business +$599/mo8,000,000400Included
Enterprise 14$999/mo14,000,000500Included
Enterprise 24$1,599/mo24,000,000600Included
Enterprise 41$2,399/mo41,000,000700Included
Enterprise 69$3,599/mo69,000,000800Included
Enterprise 120$5,799/mo120,000,000900Included

Prices are exclusive of VAT. Figures are a dated reference captured from the publisher's pricing page; check the current pricing page before committing.

Frequently asked questions

What data can I extract from Google Showtimes?

Whatever the public page renders can be captured. Target elements with CSS selectors through extract_rules, or state the fields you need in ai_extract_rules and let AI-driven extraction hand back structured JSON. The fields people usually want are movie title, theater name, theater address, showtime list, booking URL and movie rating.

How do I get started scraping Google Showtimes?

Sign up, grab your API key, and send a GET request with the target URL. The API renders the page, rotates proxies, and returns the data. The number of free credits available for testing depends on the current plan terms; check the pricing page for the exact allowance before you start.

Will I get blocked when scraping Google Showtimes?

Each request goes out over rotating residential proxies and a genuine headless browser, which makes the traffic look like a normal visitor. If a site starts pushing back harder, switch on stealth_proxy for that request.

Can I scrape Google Showtimes 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 Google Showtimes?

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

Can I scrape Google Showtimes from a specific country?

Yes. Add country_code to the request and it exits through a residential IP in that country, which matters whenever listings change from one region to another.

How many credits does a Showtimes request cost?

Base requests start at 1 credit each. Enabling render_js adds 5 credits per successful request. Enabling stealth_proxy adds 10 credits with JS rendering off, or 25 credits with JS rendering on. Credits are valid for one month and do not roll over.

What is the difference between a missing showtime and a blocked request?

A missing showtime usually means the JavaScript did not render — enable render_js. A blocked request returns a challenge or CAPTCHA — enable stealth_proxy. A page that loads but shows the wrong region's listings needs country_code. Each fix has a different credit cost, so identify the actual failure first.