bet365 APIbet365.com.au ↗
Access live and upcoming betting markets with odds from bet365 Australia, plus a full sports category list. 2 endpoints, no auth setup required.
What is the bet365 API?
The bet365 Australia API covers 2 endpoints that return live and upcoming betting market data from bet365.com.au. The get_live_games endpoint delivers an array of market selections — each with odds, handicap values, fixture IDs, and selection names — while get_sports_list returns every sport and navigation category available on the platform, including path data and icon identifiers.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/c0fe2c86-eadf-4f33-b1b0-c76efe87f962/get_live_games' \ -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 bet365-com-au-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.
from parse_apis.bet365_australia_api import Bet365, Market, Sport
client = Bet365()
# List all available sports
for sport in client.sports.list():
print(sport.sport_name, sport.icon)
# List live betting markets
for market in client.markets.list(limit=20):
print(market.selection_name, market.odds, market.fixture_id)
Get all live and upcoming betting markets with odds across all sports from bet365 Australia. Returns selections with their current odds, handicap values, and fixture identifiers. Results represent a point-in-time snapshot of all available markets; the set changes frequently as fixtures start, end, and odds move.
No input parameters required.
{
"type": "object",
"fields": {
"markets": "array of market selection objects with selection_id, selection_name, odds, handicap, fixture_id",
"total_markets": "integer - total number of betting market selections returned"
},
"sample": {
"data": {
"markets": [
{
"odds": "2/7",
"handicap": "",
"fixture_id": "185941957",
"selection_id": "118262488",
"selection_name": "Brazil"
},
{
"odds": "4/5",
"handicap": "",
"fixture_id": "192256430",
"selection_id": "964809461",
"selection_name": "Netherlands"
}
],
"total_markets": 2591
},
"status": "success"
}
}About the bet365 API
What the API Returns
The get_live_games endpoint returns all currently live and upcoming betting markets across every sport on the bet365 Australia homepage. Each item in the markets array includes a selection_id, selection_name, current odds, a handicap value where applicable, and a fixture_id tying the selection to a specific event. The response also includes a total_markets integer giving the count of all selections returned in the payload.
Sports and Navigation Coverage
The get_sports_list endpoint returns every sport and category currently listed on bet365.com.au. Each entry in the sports array carries a sport_name, a path_data value used for navigation, and an icon identifier. A total_sports count is included at the top level. This endpoint is useful for discovering which sports have active markets before querying odds data.
Inputs and Freshness
Neither endpoint accepts query parameters — both return a full snapshot of the current state of the bet365 Australia homepage at the time of the request. Because odds on live markets change frequently, repeated polling is the standard pattern for tracking movement. There is no built-in filtering by sport, event type, or time window within the API itself.
Data Shape Notes
Odds are returned per selection, not per event, so a single fixture will typically produce multiple markets entries — one for each betting option (e.g. home win, draw, away win). The fixture_id field is the consistent join key if you want to group selections belonging to the same event.
The bet365 API is a managed, monitored endpoint for bet365.com.au — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when bet365.com.au 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 bet365.com.au 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?+
- Monitor real-time odds movement across live bet365 Australia markets using repeated calls to
get_live_games - Build a sport-specific odds dashboard by filtering
marketsresults by sport after cross-referencingget_sports_listoutput - Track handicap values over time for specific fixtures using the
fixture_idandhandicapfields - Aggregate selection counts per sport to identify which categories have the most active in-play markets
- Alert on odds changes for a watched
fixture_idby diffing successiveget_live_gamesresponses - Enumerate available sports and their path data from
get_sports_listto drive navigation in a betting aggregator UI
| 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 bet365 Australia offer an official developer API?+
What does the `get_live_games` endpoint actually return for each selection?+
markets array contains five fields: selection_id (unique identifier for that betting option), selection_name (the label shown to bettors), odds (current decimal or fractional odds as returned), handicap (the line value, present where applicable), and fixture_id (links the selection to its parent event). The total_markets integer at the top level gives the total count of selections in the response.Can I filter results by a specific sport or event when calling `get_live_games`?+
selection_name or fixture_id fields. You can cross-reference sport categories returned by get_sports_list to build a mapping. If you need server-side filtering, you can fork the API on Parse and revise it to add a sport or fixture filter parameter.Does the API cover historical odds or settled markets?+
How fresh is the odds data, and does the API support streaming updates?+
get_live_games returns a point-in-time snapshot. Odds on live markets can shift within seconds, so the data reflects what was available at the moment of the request. The API does not support push or streaming updates; continuous polling is required to track changes over time.