Results data that fits downstream product workflows
Racing results are useful far beyond a results screen. Product teams use them to close analytical loops, label historical datasets, evaluate model outputs and reconcile what happened after a market was observed. A dedicated endpoint makes those workflows easier to automate.
PuntersEdge keeps results inside the racing endpoint family, allowing applications to connect race identity and outcome data with other racing views. The API is designed for informational and analytical use rather than bet placement or account settlement.
- Structured race outcomes
- Automated backend ingestion
- Historical dataset labelling
- Dashboard result views
- Racing-family consistency
Example API calls
# Settle only against status=final
curl "https://api.puntersedge.online/v1/racing/results?categories=horse" \
-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"