Sport IDs

The {sportId} path parameter on the Odds API, and how the Statistics API identifies sports instead.

Odds API — Cricket, Soccer, Tennis

Each sport has its own section of the Odds API reference, with the sport ID already filled in. Follow a sport’s name to see every endpoint for it.

Fancy and bookmaker markets are cricket only

Three Odds API endpoints cover fancy and bookmaker markets: /api/betfair/fancy-bookmaker-odds/{eventId}, /api/betfair/fancy-all-bookmaker-odds-v2/{eventId} and /api/betfair/fancy-all-bookmaker-odds-v3/{eventId}. These markets only exist for cricket, so all three return data for Cricket (sportId 4) alone. Passing an event ID from any other sport returns an empty result rather than an error, which is worth knowing before you debug the response.

Odds API — Racing

Note that the Statistics API identifies Horse Racing as 6, not 7. The two product lines use different ID spaces; use the value from the section you are calling.

Odds API — Other Sports

“Other” covers every sport that is not listed above, so it is not a closed list. The IDs below are common ones to get you started — the field accepts any valid sport ID, not only these.

IDSport
7522Basketball
3Golf
7524Ice Hockey
1477Rugby League
5Rugby Union
6Boxing
8Motor Sport
27454571Esports
998917Volleyball
11Cycling
61420Australian Rules
468328Handball
3503Darts
2152880Gaelic Games
26420387Mixed Martial Arts
2378961Politics
6422Snooker
7511Baseball
6423American Football

All of them share the Other Sports Odds API pages, where you enter the sport ID yourself.

Statistics API

Statistics endpoints do not take a {sportId} parameter — the sport is part of the path itself. These IDs are listed for cross-reference only.

IDSportPath prefix
4Cricket/api/live-score
2Tennis/api/tennis
6Horse Racing/api/horse-racing
4339Greyhound Racing/api/greyhound-racing

Test the API with live data

Run real requests in the Sportbex trial panel and see live responses.

Try it(opens in a new tab)