Build meeting-aware racing products without a generic event model
Race meeting interfaces often sit above several downstream product views: the next races, runner markets, price comparison and completed results. A racing-first API makes it easier to keep those workflows connected without translating every race into a generic sports abstraction.
Use PuntersEdge as the data layer behind meeting pages, internal race monitors, research tools and product backends. The same racing family can support upcoming-event discovery and then feed best-odds, mover and result views where the application needs them.
- Meeting-oriented race discovery
- Upcoming race workflows
- Market view inputs
- Results handoff
- Product-friendly racing structure
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"