Racing data designed for product teams, not generic sport feeds
Australian racing has its own data shape. Meetings, race ordering, runners, results and market movement need a model that fits racing rather than forcing every event into a generic sports schema. PuntersEdge keeps racing in its own endpoint family so developers can build around racing-specific workflows cleanly.
Use the API as a data source for comparison products, analytical tools, dashboards and model pipelines. The focus is structured information for software products, with dedicated endpoints for next-to-go racing, results, best odds and movers.
- Racing-specific endpoint family
- Structured meeting and runner data
- Results and best-odds workflows
- Price-movement analysis
- Developer-first JSON responses
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"