Next-to-go racing data and runner odds workflows
Intro: racing products need fast next-to-go views and runner-level bookmaker prices.
What data you need: meeting, race number, jump time, runners, odds, scratches where available, bookmaker IDs and timestamps.
How the API works: call a racing next-to-go endpoint, receive the next races in order and render runner price tables.
Code concept: fetch the next five races, sort by jump time and show best price per runner across supported bookmakers.
AU bookmaker coverage note: racing is year-round in Australia, so local bookmaker and racing-code support matters more than generic sport breadth.
Responsible gambling note: racing moves quickly; show timestamps, terms and responsible-gambling messages clearly.
- Next-to-go
- Runner odds
- Horse racing
- Bookmaker comparison
- Free key
Example API calls
# Racing — its own endpoint family, NOT a sport_key
curl "https://api.puntersedge.online/v1/racing/next-to-go?categories=horse&num_races=5" \
-H "X-API-Key: YOUR_API_KEY"
# Sports — best price per outcome across the books quoting it
curl "https://api.puntersedge.online/v1/best-odds/nrl" \
-H "X-API-Key: YOUR_API_KEY"
curl "https://api.puntersedge.online/v1/racing/next-to-go?num_races=5" \
-H "X-API-Key: YOUR_API_KEY"