A racing-first backend for app product teams
Racing apps often combine several experiences in one product: what is racing next, how markets compare, what has moved and what happened after the race. Those workflows are easier to build when the upstream data model is designed around racing.
PuntersEdge keeps racing separate from generic sport keys and exposes dedicated workflows for next-to-go races, best odds, movers and results. App teams can use that data behind mobile, web or internal products while keeping their own interface and business logic.
- Racing-first app backend
- Next-to-go race data
- Best-odds views
- Market movement inputs
- Results workflows
Example API calls
# Racing is its own endpoint family, not a sport_key
curl "https://api.puntersedge.online/v1/racing/next-to-go?num_races=5" \
-H "X-API-Key: YOUR_API_KEY"
curl "https://api.puntersedge.online/v1/racing/next-to-go?num_races=5&country=AU" \
-H "X-API-Key: YOUR_API_KEY"