Integration GuidesDocs
Coverage MatrixDocumentationChange LogLog InContact Us
Integration Guides

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

ScenarioPackageBuild this when you need
Pulling Prematch OddsPrematchAn odds board for upcoming games: money lines, spreads, totals, and their period splits, compared across bookmakers
Retrieving Player PropsPlayer PropsPlayer-level markets (total bases, strikeouts, receptions) grouped per player, with lines and prices per book
Tracking Futures OddsFuturesChampionship, division, and award odds that update through a season
Tracking Live OddsLive OddsIn-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 buildingStart withThen add
An odds comparison site or widgetPulling Prematch OddsMonitoring Odds Changes for the refresh loop
A props board or best-line toolRetrieving Player PropsID Handling to join props to stats
Season-long futures contentTracking Futures OddsThe other scenarios for game-day coverage
An in-play odds board or line-movement trackerTracking Live OddsPulling Prematch Odds for the pre-game board and closing lines
Line movement or closing-line trackingPulling Prematch OddsOdds Comparison Fundamentals for the removed lifecycle


Before You Build

  • Confirm coverage for your competitions with the Sport Competitions feed's markets, player_props, and futures flags 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

Did this page help you?