Changelog
Changelog
Sample entriesNew endpoints, fields and sports. Each endpoint carries its own version; a breaking change ships under a new version path.
Changed
The API now follows the BetsAPI format
- Endpoints are split into the Events API and the Bet365 API, with BetsAPI paths such as
/v3/events/inplay,/v1/event/viewand/v4/bet365/prematch. - Pass your token as
token=in the query string. Responses carrysuccessas1or0, and errors use the R-Errors codes. - Events have our
idand the bet365 fixture id inbet365_id. - Sectors are gone. Everything that plays is a team: esoccer pairings such as
Liverpool (Marlin) Esportsare teams withis_esports, andskip_esportsleaves them out.
- Endpoints are split into the Events API and the Bet365 API, with BetsAPI paths such as
Added
Leagues, teams, squads and players
/v3/league,/v3/league/tableand/v1/league/toplist./v3/team,/v1/team/squad,/v1/playerand/v1/tennis/ranking.
Added
Incremental odds
since_timeon/v2/event/oddsreturns only lines added after a UTC epoch.- Each odds line now includes the score in
ssand the minute intime_str.
Added
Merge History
/v1/event/merge_historylists duplicated events we merged. Both ids return the same data in Event View.
Added
Raw bet365 data
raw=1on the Bet365 API returns the data before parsing. Horse Racing and Greyhounds are available this way.
Released
Odds Data API
- In-play, upcoming and ended events, odds and results from bet365.
- 3,600 requests per hour by default, with volume add-ons.
