Oddschecker APIoddschecker.com ↗
Access betting odds from Oddschecker via API. Compare bookmaker prices for football matches, horse races, and more across 7 endpoints.
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.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/f34bb573-963f-4e6e-9222-1c47647686b0/get_sports_list' \ -H 'X-API-Key: $PARSE_API_KEY'
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")
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.
No input parameters required.
{
"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.
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.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- 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_oddson 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_meetingsandget_horse_race_odds - Populate a league picker UI by fetching all competitions from
get_football_leaguesand mapping slugs to league paths - Search for a specific team or event by name with
search_eventsand 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
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 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.
Does Oddschecker have an official developer API?+
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?+
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`?+
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.