JSON responses that fit modern product architectures
Structured JSON makes odds data easier to pass between services, store in application databases and transform for front-end components. PuntersEdge is suited to teams building APIs, dashboards, scheduled jobs and analytical services that need consistent machine-readable inputs.
Sports data can be requested using the sports endpoint family and sport keys, while racing uses dedicated racing routes. That separation helps products keep two different market structures clear in code and data models.
- Machine-readable JSON
- Web and service integration
- Data-pipeline input
- Sport-key workflows
- Racing model separation
Example API calls
# Swap {sport_key} for a key from /v1/sports
curl "https://api.puntersedge.online/v1/sports/{sport_key}/odds" \
-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"