Skip to content

Google Sports Results API: Scores, Stats and Schedules in One Call

Google Sports surfaces change minute by minute, and the pages that carry them lean on JavaScript, regional routing and bot checks.

OUTPUT FORMATSHTMLJSONMarkdown

This API takes a Google Sports URL, renders the page in a real headless browser, rotates residential proxies and returns either the rendered HTML or structured JSON. The sections below cover what you can collect, which request parameters do what, how credits are charged per request, and how to choose a plan without over-buying concurrency.

What you can collect from Google Sports

Google Sports SERP pages carry several distinct data types, and most teams end up needing more than one of them:

  • Live and final game scores — for scoreboards, alerts and post-match reporting.
  • Player statistics — performance metrics that feed team strategy and player development reviews.
  • Event schedules by region — fixtures and calendars used for logistics and resource planning.
  • Team standings and league fixtures — table positions and upcoming matches.
  • Tournament brackets — knockout structures and progression.

A single request can return the whole rendered page, so scores, schedules and stats that appear together on the same SERP come back together. If you only need a subset, target it with extraction rules rather than post-processing the full HTML.

How a request flows

The workflow has four stages:

  1. Get an API key. Creating an account issues a key and a starting credit balance for testing.
  2. Pick a client. SDKs are published for Python, Node.js, Go, PHP, Ruby and Java; plain cURL works for anything else. A dashboard request builder lets you test without writing code.
  3. Send the Google Sports URL with POST or GET. The renderer executes the page's JavaScript, handles anti-bot measures, and returns rendered HTML — or parsed JSON when you supply extraction rules.
  4. Add options only when needed. JavaScript rendering, stealth proxies, country targeting and AI extraction are all opt-in parameters, and each affects credit cost.

No proxy pool or headless Chrome fleet is yours to operate; the request is a single call per page.

Parameter map: which control to reach for

GoalParameterWhat it does
Page needs JavaScript to populaterender_js (set true)Runs the page in a real headless browser server-side and returns post-render HTML
Content differs by countrycountry_codeRoutes the request through a residential IP in that country
You want specific fields, not a whole pageextract_rulesMaps CSS selectors to field names; response returns parsed JSON
You want fields described in plain languageai_extract_rulesNatural-language extraction spec; response returns parsed JSON
Bot checks are blocking youstealth_proxyHigher-assurance proxy path, charged at a higher credit rate
You need a visual recordScreenshot optionCaptures a full-page screenshot alongside the scrape

Start with the cheapest option that works. Plain HTML fetching is the baseline; add render_js only when the data is missing from the raw response, and reserve stealth_proxy for targets that keep rejecting rendered requests.

Credit costs per request

Credits are consumed per successful request, and the amount depends on which options are enabled:

  • Baseline request — starts at 1 credit.
  • JavaScript rendering — 5 credits per successful request when render_js is enabled.
  • Premium proxies — 10 credits with JS rendering disabled, 25 credits with JS rendering enabled.
  • Stealth proxy — 75 credits.

Worked example. A daily job that renders 200 Google Sports pages with JavaScript costs 200 × 5 = 1,000 credits per run. The same job routed through premium proxies with rendering on costs 200 × 25 = 5,000 credits per run. If you switch to stealth proxies for a stubborn subset of 20 pages, those 20 cost 20 × 75 = 1,500 credits, and the remaining 180 at 5 credits cost 900 — 2,400 credits total.

Credit validity and rollover follow the plan terms in force at purchase: {{OWNER_CREDIT_EXPIRY_POLICY}}. Size your plan against your monthly request volume rather than your peak day.

When a request fails, which cause is it?

Three different problems look similar in a log but need different fixes:

  • You hit your concurrency ceiling. The API enforces concurrency limits per plan, not per-target rate limits. If requests queue or reject while your target is healthy, you have outgrown the plan's simultaneous-request allowance — raise concurrency or stagger the job.
  • The target is throttling aggressive patterns. Google can slow or challenge rapid repeated queries from one session. Space out requests or spread them across multiple sessions.
  • Bot detection is blocking the render. If the page returns a challenge instead of content, move up to stealth_proxy rather than retrying the same request.

Diagnose in that order: check your own concurrency first, then request pacing, then proxy tier. Changing the proxy tier to solve a concurrency problem wastes credits.

Choosing a plan

Plans differ along four axes: monthly API credits, concurrent requests, support level, and team features. JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots with extraction rules are included from the entry plan upward. Priority email support, a dedicated account manager and team management appear only on higher tiers.

Support channels and response commitments: {{OWNER_SUPPORT_SLA}}. Cancellation terms: {{OWNER_CANCELLATION_TERMS}}.

Use the plan table below to match credits to your monthly request volume and concurrency to your largest simultaneous job. Prices are exclusive of VAT. If your volume exceeds the listed tiers, a sales conversation is the route to more credits and concurrency.

A starting credit balance is available for testing before you commit to a paid tier: {{OWNER_FREE_CREDIT_ALLOWANCE}}.

Compliance and scale notes

Data-handling and compliance posture: {{OWNER_COMPLIANCE_CLAIMS}}. Performance and scale characteristics: {{OWNER_PERFORMANCE_CLAIMS}}.

Proxy rotation and headless browser rendering are the mechanisms used to reduce IP-based blocking and mimic ordinary browsing behaviour. They lower blocking risk; they are not a guarantee that every request succeeds. Your own obligations — acceptable use, data retention, and any league or sports-data licensing — remain yours to confirm before you build a product on top of the output.

Plan comparison: credits, concurrency and features
PlanPriceAPI 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 are exclusive of VAT. JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots with extraction rules are included on every listed plan. Credit validity and rollover follow the plan terms in force at purchase ({{OWNER_CREDIT_EXPIRY_POLICY}}). This is a dated reference to the captured plan structure; confirm current pricing and allowances before purchase.

Frequently asked questions

How do I handle JavaScript when scraping Google Sports results?

Set render_js=true on the request. The page runs in a real headless browser, the JavaScript executes server-side, and you receive the post-render HTML. This costs 5 credits per successful request.

Can I scrape Google Sports results from a specific country?

Yes. Pass country_code on the request to route through a residential IP in that country. This matters when the sports content shown varies by location.

What's the rate limit for scraping Google Sports results?

There is no per-target rate limit. The API enforces concurrency limits per plan — the number of requests that can be sent at the same time. If the target itself throttles aggressive patterns, space out requests or use multiple sessions.

How do I get structured JSON from Google Sports results?

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

Which programming languages can I use to scrape Google Sports results?

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.

How much does it cost to scrape Google Sports results?

Free trial allowance and card requirement: {{OWNER_FREE_CREDIT_ALLOWANCE}}. Paid plans begin at $19/month for higher volume and concurrency. Per-request credit cost depends on options: 5 credits for JS rendering, 10 or 25 for premium proxies depending on whether JS rendering is on, and 75 for stealth proxy.

Should I use the full rendered HTML or extraction rules?

Use the full HTML when you need the whole page or are still exploring its structure. Switch to extract_rules or ai_extract_rules once you know which fields you need — parsed JSON is easier to store, diff and feed into downstream jobs than raw markup.

What happens to unused credits at the end of the month?

Credit validity and rollover follow the plan terms in force at purchase: {{OWNER_CREDIT_EXPIRY_POLICY}}. Size your plan against your monthly request volume, not your busiest single day.