REST endpoints for product-focused odds integrations
A REST API is often the simplest fit for web backends, scheduled data jobs and service-to-service integrations. PuntersEdge exposes sports discovery and sport-key odds endpoints so teams can request only the data their application needs.
The interface works well for prototypes that need to become production services because the data layer can sit behind your own cache, database, model service or user-facing application. Racing remains separate in its own endpoint family rather than being treated as another sport key.
- REST endpoint access
- Sport-key request pattern
- Backend integration
- Service-to-service workflows
- Separate racing family
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"