Skip to content

Live Odds From Oddschecker, Collected on Request

Oddschecker pages combine JavaScript-rendered markets, rotating bookmaker offers and bot-detection layers.

OUTPUT FORMATSHTMLJSONMarkdown

Doing that yourself means owning a headless browser fleet, a proxy pool and a fingerprint strategy. This page explains how a managed scraping API collapses that work into a single request, what each request option does, and how to estimate cost before you scale a line-monitoring or historical-trends job.

What the API returns from an Oddschecker page

You send an Oddschecker URL plus your API key. The service rotates proxies, spoofs browser fingerprints and renders JavaScript server-side, then returns a response you can parse. The fields the product targets are match details, odds across bookmakers, sport, event date, market type and bookmaker promo flags. If you would rather not parse HTML at all, extraction rules or an AI extraction spec can return parsed JSON directly.

Typical jobs fall into three groups:

  • Line monitoring — poll a market and compare prices across bookmakers to support dynamic pricing.
  • Live odds feeds — keep a strategy current as markets move during play.
  • Historical trend collection — build a dataset of past prices for model training or backtesting.

All three share the same request shape; what changes is polling frequency, which markets you target, and whether you need geo-specific content.

Request options and when to use them

The API exposes a small set of parameters that map directly to the obstacles Oddschecker presents. Use this as a control map rather than a full reference — exact syntax lives in the documentation.

  • render_js — runs the page in a real headless browser and returns post-render HTML. Needed for markets that only appear after client-side scripts execute.
  • country_code — routes the request through a residential IP in the chosen country. Use it when odds, bookmaker availability or promotions differ by region.
  • extract_rules — CSS selectors mapped to field names, returning parsed JSON.
  • ai_extract_rules — a natural-language spec for the fields you want, also returning parsed JSON.
  • stealth_proxy — a higher-assurance proxy tier for pages that challenge standard requests with CAPTCHAs.

A practical default: start with render_js and extract_rules. Add country_code only if you have confirmed that content varies for your target market. Escalate to stealth_proxy when standard requests are consistently challenged rather than intermittently blocked.

How credits translate into monthly cost

Credits are consumed per successful request, and the amount depends on which options are enabled. The published rules are: 1 credit for a base request, 5 credits when JS rendering is on, 10 or 25 credits for premium proxies depending on whether JS rendering is also enabled, and 75 credits for stealth_proxy. Credits are valid for one month and do not roll over.

Worked example. Suppose you monitor 200 events, polling each once every 10 minutes during a 12-hour window. That is 200 × 72 = 14,400 requests per day. With JS rendering at 5 credits each, that is 72,000 credits per day — far beyond the Hobby tier's 75,000 monthly credits. Either widen the polling interval, narrow the event list, or move to a plan sized for the volume. Running the arithmetic before choosing a plan is the single most useful step in this workflow.

The plan table below lists every tier with its credit allowance and concurrency. Prices are exclusive of VAT; confirm current pricing before purchase.

Concurrency limits versus target throttling

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

Concurrency limits are enforced by the API per plan. If you exceed the number of simultaneous requests your plan allows, requests queue or are rejected at the API boundary. The fix is to reduce parallelism or upgrade the plan.

Target throttling happens on Oddschecker's side when a pattern of requests looks aggressive. The API does not impose a per-target rate limit, so a burst that stays within your concurrency allowance can still be throttled upstream. The fix is to space requests out or distribute them across multiple sessions.

If you see errors, check which side produced them before changing anything. Raising concurrency will not help with upstream throttling, and slowing requests will not help with a plan-level concurrency cap.

Languages and setup

SDKs are published for Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works for any stack. Documentation includes examples in Python, Node.js and cURL, plus a request builder. The setup sequence is: create an account to get an API key and free test credits, install the SDK for your language or skip it and call the endpoint directly, then send a request with your key and an Oddschecker URL.

If your team already has an HTTP client and a scheduler, the cURL path is the shortest route to a first successful response. Reach for an SDK when you want typed responses and less boilerplate in a larger codebase.

Decision checklist before you commit

Use this to decide whether a managed API fits your job.

  1. Volume — estimate requests per day and multiply by the credit cost of your chosen options. Compare against the plan tiers.
  2. Freshness — decide how often each market must be re-checked. Line monitoring needs tighter intervals than historical collection.
  3. Geo-dependency — confirm whether your target markets differ by country. If not, skip country_code and save complexity.
  4. Rendering need — test whether the markets you want appear without JS rendering. If they do, you cut credit cost per request substantially.
  5. Extraction approach — prefer CSS extraction rules when the page structure is stable; use AI extraction when it changes often or when you want a natural-language spec.
  6. Compliance — confirm your use of the data meets the source site's terms and your own regulatory obligations.

If most answers point to high volume, geo-varied content and frequent polling, a managed API removes the proxy and browser maintenance that would otherwise dominate the project.

Plan tiers, credits and concurrency
PlanPriceAPI CreditsConcurrent requestsPriority supportAccount managerTeam management
Hobby$19 /mo75,00025Not includedNot includedNot included
Freelance$49 /mo250,00050Not includedNot includedNot included
Startup$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$2,399 /mo41,000,000700IncludedIncludedIncluded
Enterprise 69$3,599 /mo69,000,000800IncludedIncludedIncluded
Enterprise 120$5,799 /mo120,000,000900IncludedIncludedIncluded

All prices are exclusive of VAT. Credits are valid for one month and do not roll over. Requests start at 1 credit each. JavaScript rendering costs 5 credits per successful request. Premium proxies cost 10 or 25 credits depending on whether JS rendering is enabled. Stealth proxy costs 75 credits. Confirm current pricing and plan features before purchase.

Frequently asked questions

How do I handle JavaScript when scraping Odds?

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.

Can I scrape Odds from a specific country?

Yes. Pass country_code to route the request through a residential IP in that country. This is useful when odds or bookmaker content varies by geography.

What's the rate limit for scraping Odds?

The API enforces concurrency limits per plan rather than per-target rate limits. If the target site throttles aggressive request patterns, space out requests or use multiple sessions.

How do I get structured JSON from Odds?

You have two routes to parsed JSON. One is extract_rules, where you supply CSS selectors keyed to the field names you want. The other is ai_extract_rules, where you describe the fields in plain language and the service maps them for you. Either way, the response arrives already parsed rather than as raw HTML.

Which programming languages can I use to scrape Odds?

Any language works. SDKs are published for Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works as well. Choose whatever your stack already uses.

How much does it cost to scrape Odds?

New accounts receive 1,000 free credits with no card required. Paid plans start at $19 per month for higher volume and concurrency. Credit cost per request depends on options: 5 credits for JS rendering, 25 for premium_proxy with JS, and 75 for stealth_proxy.