Harness racing data shaped for racing workflows
Harness racing products need race ordering, runner context, market information and results to work together cleanly. PuntersEdge keeps racing in its own endpoint family so a harness workflow can use the same racing-oriented structure as other supported racing codes.
Use the data for race lists, comparison interfaces, internal monitoring, research and model inputs. Developers can combine next-to-go discovery with best-odds, movers and results workflows as the product moves from pre-race views into post-race analysis.
- Harness racing workflows
- Upcoming race discovery
- Market comparison inputs
- Results integration
- Analysis-ready racing data
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"