Table-ready data for front-end odds widgets
Odds widgets need consistent JSON that maps cleanly into cards, tables and best-price badges. PuntersEdge focuses on Australian bookmaker data so you can build local comparison components without maintaining individual integrations.
Use the API for racing comparison tables, next-to-go modules, best-odds badges and pre-match sport widgets. Showing prices to your own users is the Display licence on the Plus plan, with a visible Prices by PuntersEdge credit on every surface that shows them. The racing comparison table guide below walks through the build with its real output, and the free embeddable widget is the no-code option.
- Embed bookmaker prices
- Best-odds badges
- Sports and racing widgets
- JSON for front-end components
- Pricing and examples linked
Example API calls
# Racing — its own endpoint family, NOT a sport_key
curl "https://api.puntersedge.online/v1/racing/next-to-go?categories=horse&num_races=5" \
-H "X-API-Key: YOUR_API_KEY"
# Sports — best price per outcome across the books quoting it
curl "https://api.puntersedge.online/v1/best-odds/nrl" \
-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"