Data, logic and responsible-use notes for odds comparison
Intro: odds comparison needs event IDs, market names, selections, bookmaker identifiers, current prices and timestamps.
What data you need: head-to-head, lines, totals and racing runner odds from multiple Australian bookmakers in a consistent schema.
How the API works: request a sport or racing endpoint with an API key, receive JSON, normalise selections and calculate the best available price per outcome.
Code concept: fetch markets, group by event and selection, sort bookmaker prices, then render the best odds with update timestamps.
AU bookmaker coverage matters because Australian users expect local brands such as Sportsbet, TAB, Neds, Ladbrokes, Unibet and PointsBet.
Responsible gambling note: present data as information, not guaranteed profit, and keep 18+ and help messaging visible.
- Market IDs
- Bookmaker prices
- Best-price logic
- REST/JSON
- CTA: get a free API key
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" \
-H "X-API-Key: YOUR_API_KEY"