Discover/Oddschecker API
live

Oddschecker APIoddschecker.com

Access betting odds from Oddschecker via API. Compare bookmaker prices for football matches, horse races, and more across 7 endpoints.

Endpoint health
verified 3d ago
get_football_leagues
get_football_matches
get_match_odds
get_horse_racing_meetings
get_sports_list
7/7 passing latest checkself-healing
Endpoints
7
Updated
22d ago

What is the Oddschecker API?

The Oddschecker API covers 7 endpoints that expose sports listings, football league and match data, horse racing cards, and bookmaker-by-bookmaker odds comparisons. Starting with get_sports_list to enumerate available sports, you can drill down to individual match markets via get_match_odds, which returns every outcome with odds keyed by bookmaker code, making price comparison straightforward across dozens of bookmakers.

Try it

No input parameters required.

api.parse.bot/scraper/f34bb573-963f-4e6e-9222-1c47647686b0/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X GET 'https://api.parse.bot/scraper/f34bb573-963f-4e6e-9222-1c47647686b0/get_sports_list' \
  -H 'X-API-Key: $PARSE_API_KEY'
Python SDK · recommended

Typed, relational, agent-ready

A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.

  • Fully typed · autocompletes
  • Objects link to objects
  • Typed errors & pagination

Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:

uv add parse-sdk
uv run parse init
uv run parse add --marketplace oddschecker-com-api

uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.

"""Oddschecker SDK — compare betting odds across bookmakers for football and horse racing."""
from parse_apis.oddschecker_api import Oddschecker, MatchNotFound

client = Oddschecker()

# List available sports on Oddschecker
for sport in client.sports.list(limit=5):
    print(sport.name, sport.slug)

# List football leagues and drill into one league's matches
league = client.leagues.list(limit=1).first()
if league:
    print(league.name, league.slug)

# Construct a league and list its matches (World Cup has active events)
wc = client.league(slug="football/world-cup")
match = wc.matches.list(limit=1).first()
if match:
    print(match.event, match.slug)

# Get odds for a match — multiple markets, each with outcomes per bookmaker
if match:
    try:
        odds = match.odds()
        for market in odds.markets[:2]:
            print(market.name)
            for outcome in market.outcomes[:3]:
                print(outcome.name, outcome.odds)
    except MatchNotFound as exc:
        print(f"Match gone: {exc.match_slug}")

# Horse racing: list today's meetings, then get runners for a race
meeting = client.meetings.list(limit=1).first()
if meeting:
    print(meeting.venue)
    for race_item in meeting.races[:2]:
        race = client.race(url=race_item.url)
        for runner in race.runners.list(limit=3):
            print(runner.name, runner.odds)

# Search for events by team name
for event in client.events.search(query="United", limit=3):
    print(event.subevent_dname, event.category_name, event.market_name)

print("exercised: sports.list / leagues.list / league.matches.list / match.odds / meetings.list / race.runners.list / events.search")
All endpoints · 7 totalmissing one? ·

Retrieves all sports available on Oddschecker. Returns sport names and slugs extracted from the site navigation. The slug can be used to construct league or event URLs for further exploration.

Input

No input parameters required.

Response
{
  "type": "object",
  "fields": {
    "sports": "array of sport objects each containing name, url, and slug"
  },
  "sample": {
    "data": {
      "sports": [
        {
          "url": "https://www.oddschecker.com/horse-racing",
          "name": "Horse Racing",
          "slug": "horse-racing"
        },
        {
          "url": "https://www.oddschecker.com/football",
          "name": "Football",
          "slug": "football"
        },
        {
          "url": "https://www.oddschecker.com/tennis",
          "name": "Tennis",
          "slug": "tennis"
        }
      ]
    },
    "status": "success"
  }
}

About the Oddschecker API

Sports and Football Coverage

get_sports_list returns the full navigation of available sports as an array of name, URL, and slug objects. From there, get_football_leagues lists all competitions with their slugs, which feed directly into get_football_matches. That endpoint accepts an optional league_path parameter — for example football/english/premier-league or football/champions-league — and returns upcoming match events with their slugs.

Match Odds Detail

get_match_odds takes a match_slug from the previous step and returns a markets array. Each market object contains a name, an ID, and an outcomes array. Outcomes include the selection name, an ID, and an odds object keyed by bookmaker code (e.g. bet365, williamhill). The response also includes a bookmakers object mapping those codes to metadata, so you can display or filter by bookmaker name without a separate lookup.

Horse Racing

get_horse_racing_meetings returns today's meetings as an array of venue objects, each containing a list of races with their start times and URLs. Those URLs feed into get_horse_race_odds, which returns a runners array — one entry per horse — with fractional odds strings mapped to bookmaker codes. Coverage is limited to today's card; historical results and future race cards are not returned.

Search

search_events accepts a free-text query (team name, competition, or event) and returns a search_results object containing matched events with market_map, start_time, and subevent_dname fields, plus bookmaker offer data and tips where available. This is useful for locating a match slug when you don't already know the league path.

Reliability & maintenanceVerified

The Oddschecker API is a managed, monitored endpoint for oddschecker.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when oddschecker.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.

This isn't an official oddschecker.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.

Last verified
3d ago
Latest check
7/7 endpoints passing
Maintenance
Monitored & self-healing
Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Build a best-odds finder for football matches by comparing prices across bookmakers returned in get_match_odds
  • Track odds movement for Premier League fixtures by polling get_match_odds on a schedule and storing the bookmaker-keyed odds
  • Aggregate today's horse racing runners and their fractional odds from multiple venues using get_horse_racing_meetings and get_horse_race_odds
  • Populate a league picker UI by fetching all competitions from get_football_leagues and mapping slugs to league paths
  • Search for a specific team or event by name with search_events and resolve its market data without needing to navigate the sport hierarchy
  • Monitor which bookmakers consistently offer the best price on a given match outcome by parsing the bookmaker codes in the outcomes array
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo1005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 req/min

One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.

Frequently asked questions
Does Oddschecker have an official developer API?+
Oddschecker does not currently publish a public developer API or documented data feed. Access to their odds data is not offered through any official API portal.
What does `get_match_odds` return and how are bookmaker odds structured?+
get_match_odds returns a markets array where each entry has a market name and ID, plus an outcomes array. Each outcome includes a selection name and an odds object whose keys are bookmaker codes (short identifiers like b365 or pp) and whose values are the odds for that selection. The bookmakers field at the top level maps those same codes to metadata such as the bookmaker's display name.
Are historical odds or past results available?+
No historical odds data or settled results are returned by any of the current endpoints. The API covers upcoming football matches, today's horse racing meetings, and live markets. You can fork this API on Parse and revise it to add endpoints targeting Oddschecker's results pages if historical data is needed.
Does the API cover sports other than football and horse racing in detail?+
get_sports_list enumerates all sports on Oddschecker, and search_events works across all sports. However, dedicated event-listing and odds-comparison endpoints exist only for football and horse racing. Other sports such as tennis, basketball, or golf are not covered by their own endpoints currently. You can fork the API on Parse and revise it to add sport-specific event and odds endpoints for those markets.
How specific can the `league_path` filter be in `get_football_matches`?+
The league_path parameter is optional and accepts path strings like football/english/premier-league or football/champions-league. Slugs for valid paths come from the slug field in get_football_leagues results. If you omit the parameter entirely, the endpoint falls back to a default scope, but filtering by a specific league path is recommended to get targeted match listings.
Page content last updated . Spec covers 7 endpoints from oddschecker.com.
Related APIs in SportsSee all →
oddsportal.com API
Track sports betting odds, matches, and results across multiple sports and leagues in real-time, while viewing team standings and match details to stay informed on upcoming games. Access comprehensive betting data and historical results from OddsPortal to compare odds and analyze sports outcomes.
oddspedia.com API
Find profitable betting opportunities and compare real-time odds across dozens of bookmakers to identify sure bets, value bets, and dropping odds for various sports. Filter matches by sport, league, and region to make informed betting decisions with comprehensive odds comparisons and match information.
unibet.com API
Access live betting odds, browse sports categories and upcoming matches, and search for specific events across multiple leagues in real-time. Get detailed event information including current odds for thousands of sports matchups to inform your betting decisions.
sportybet.com API
Get real-time betting odds and live scores for football, basketball, and other sports from SportyBet. Browse upcoming events with full market odds, monitor live matches as they happen, and view sport listings with event counts across multiple markets.
stake.com API
Get live and detailed betting odds across popular sports fixtures from Stake.com, with the ability to search current odds by sport or dive into specific fixture market data. Monitor real-time odds movements to stay updated on the latest betting lines for your favorite sports events.
sportsbookreview.com API
Compare sportsbooks and their ratings, view real-time betting odds across sports and specific matchups, monitor how lines move over time, and discover expert picks and promotions all in one place. Make more informed betting decisions by accessing comprehensive sportsbook reviews, odds comparisons, and professional analysis.
pinnacle.com API
Access real-time and pre-event sports betting odds, matchups, and markets from Pinnacle. Retrieve data across all available sports and leagues, monitor live events with scores and live odds, and explore political and entertainment betting markets. Covers full market depth including spreads, totals, moneylines, props, and alternate lines.
superbet.ro API
Access sports betting data from Superbet.ro, including the full sports and competition hierarchy, pre-match and live event listings, detailed odds, boosted prices, popular accumulator suggestions, and Bet Builder markets.