Documentation / Building
One schema, many sports, sports data API
One schema, many sportsWrite your code once. Every sport answers the same way.
- The same address shape:
/v1/{sport}/{endpoint}. - The same answer:
dataandmeta, with the same meta fields. - The same ids: stable, ours, and opening their own endpoint.
- The same errors and the same limits headers.
- The same paths by kind of sport: team sports share one set, one-against-one sports another, and racing its own.
Where sports differ
The fields inside a row follow the sport: football has goals, cricket overs and wickets, racing draws and prices. Each endpoint page lists its fields from a real, current answer.
Sports serving now
Football, horses, greyhounds, cricket, basketball, rugby, darts, boxing, volleyball, table tennis, badminton. Being connected: tennis, ice hockey, baseball, cycling, handball.