Integration Scenarios
Each scenario in this section is a self-sufficient walkthrough of one integration goal: the feeds involved, the workflow, a worked example built on responses from the API, and the refresh strategy that keeps it current. They all build on the same foundations, so read API Basics and Odds Comparison Fundamentals first if you have not already.
The Scenarios
| Scenario | Package | Build this when you need |
|---|---|---|
| Pulling Prematch Odds | Prematch | An odds board for upcoming games: money lines, spreads, totals, and their period splits, compared across bookmakers |
| Retrieving Player Props | Player Props | Player-level markets (total bases, strikeouts, receptions) grouped per player, with lines and prices per book |
| Tracking Futures Odds | Futures | Championship, division, and award odds that update through a season |
| Tracking Live Odds | Live Odds | In-play prices per bookmaker that refresh through the game, from the pre-game board to the final |
Monitoring Odds Changes is the cross-cutting companion to the Prematch and Player Props scenarios: it covers the change logs and the refresh loop they rely on; Live Odds polls its event feeds directly. Feed TTLs and polling cadences are on Update Frequencies.
Where to Start
| If you are building | Start with | Then add |
|---|---|---|
| An odds comparison site or widget | Pulling Prematch Odds | Monitoring Odds Changes for the refresh loop |
| A props board or best-line tool | Retrieving Player Props | ID Handling to join props to stats |
| Season-long futures content | Tracking Futures Odds | The other scenarios for game-day coverage |
| An in-play odds board or line-movement tracker | Tracking Live Odds | Pulling Prematch Odds for the pre-game board and closing lines |
| Line movement or closing-line tracking | Pulling Prematch Odds | Odds Comparison Fundamentals for the removed lifecycle |
Before You Build
- Confirm coverage for your competitions with the Sport Competitions feed's
markets,player_props, andfuturesflags before assuming a package has data for them (see API Basics) - Decide your ID strategy up front: URNs as primary keys, mappings for joins to other Sportradar products (see ID Handling)
- Plan polling around the change logs and pagination limits rather than fixed timers (see Monitoring Odds Changes)
- Check the Update Frequencies chart before choosing polling cadences
- If you also need win probabilities rather than bookmaker prices, pair these scenarios with the Probabilities API, which shares its sport event IDs with Odds Comparison
Updated 15 days ago
Did this page help you?
