A backend layer for racing market products
Teams building racing products often end up maintaining several separate data workflows: upcoming races, comparison views, movement analysis and completed results. PuntersEdge keeps those workflows within a dedicated racing API family so the product layer can rely on a consistent integration approach.
That makes the API suitable as a backend dependency for racing research tools, internal trading analysis, customer dashboards and data products. Your application remains responsible for its own presentation, business rules and analytical interpretation.
- Unified racing data layer
- Market comparison workflows
- Movement and result context
- Product-backend integration
- Analytical use cases
Example API calls
# Training data: the last price each book showed before the jump, with the
# result beside it — the denominator for closing-line value.
curl "https://api.puntersedge.online/v1/racing/closing-lines?from=2026-08-01&to=2026-08-31&category=horse&resulted_only=true" \
-H "X-API-Key: $PUNTERSEDGE_API_KEY"
# Score your own bets against that close (Plus and above):
curl -X POST "https://api.puntersedge.online/v1/racing/clv" \
-H "X-API-Key: $PUNTERSEDGE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"bets":[{"venue":"Flemington","meeting_date":"2026-09-20","race_number":5,"runner_ref":"h:example","price":4.20,"stake":50}]}'
curl "https://api.puntersedge.online/v1/racing/next-to-go?num_races=5&country=AU" \
-H "X-API-Key: YOUR_API_KEY"