Race discovery
Filter races by type, country, state, status and start time before requesting a full racecard.
GET /v1/racing/events
Get racecards, runners and bookmaker prices from Australia, New Zealand, Ireland and the UK through one documented racing API.
{
"event_id": "AU-FLEM-20260903-R5",
"as_of_ts_ms": 1788411600000,
"items": [
{
"bookmaker_name": "sportsbet",
"runners": [{
"runner_number": "4",
"runner_name": "Example Runner",
"win_odds": 3.40,
"place_odds": 1.65
}]
}
],
"resume": "1788411600000-0"
}
Use one event ID to connect the racecard, runner market, bookmaker snapshots and live price updates.
Filter races by type, country, state, status and start time before requesting a full racecard.
GET /v1/racing/events
Read the venue, race number, start time, distance, active runners and canonical event ID.
GET /v1/racing/events/{event_id}
Compare bookmaker, runner number, runner name, win_odds and place_odds in one timestamped snapshot.
GET /v1/racing/events/{event_id}/odds
Apply racing price changes over SSE or WebSockets and reconnect from the latest resume token.
GET /v1/racing/events/{event_id}/odds/stream
Request thoroughbred horse, greyhound and harness racing across Australia, New Zealand, Ireland and the UK.
Compare current prices across eight active racing bookmaker integrations.
Filter the race list, load the runner market and keep bookmaker prices current with SSE or WebSockets.
Choose horse, greyhound or harness, then narrow the list by AU, NZ, IE or GB and keep the returned event ID.
GET /v1/racing/events?race_type=horse-racing&race_country=AU&status=fetching&limit=25
Use the event ID to load bookmaker snapshots, runner-level win and place prices, timestamps and the resume token.
GET /v1/racing/events/{event_id}/odds
Continue from the snapshot resume token, apply price changes, and reload the snapshot after a resync event.
SSE or WebSocket
Use typed SDKs, Postman and OpenAPI. Connect coding agents through MCP or add live prices with SSE and WebSockets.
Start with typed clients, racing request models and API-key authentication.
Generate a client from the public racing event, odds and stream schemas.
Run working racing requests with your own API key and event ID.
Connect supported coding agents to racing events, odds and streams.
Start with a snapshot, then receive supported runner price changes.
Use a persistent connection for richer live racing products.
Download a complete local app with country filters, racecards, runner prices and stream reconnect handling.
Run the next-to-jump racing tutorialRace types, country filters, returned fields and live odds updates.
Race records include the venue, race number, start time, country, state, distance, active runners and status. Odds snapshots add bookmaker names, runner numbers and names, win and place prices, timestamps and a resume token.
Use the canonical values race_type=horse-racing, race_type=greyhound-racing and race_type=harness-racing. Legacy shorthand remains normalized for backward compatibility.
The racing catalog covers Australia, New Zealand, Ireland and the United Kingdom. Filter them with the country codes AU, NZ, IE and GB.
The active racing integrations are Sportsbet, Ladbrokes, PlayUp, PointsBet, Dabble, BetRight, Betr and Unibet. Some Ladbrokes prices may also appear under Neds, Betcha or TAB NZ through shared odds mappings; these are not counted as separate integrations.
GET /v1/racing/events accepts race_type, race_country, race_state, status, start_from, start_to, cursor and limit. This lets you request the race window your application needs.
Yes. Load an odds snapshot first, then connect to the matching SSE or WebSocket endpoint. Reconnect with the latest resume token and reload the snapshot after a resync event.
Choose a plan by request volume, streaming hours, rate limits and support.
Scale
Connect odds and bet feeds to your product.
Choose a paid plan and start building with real odds data.