Categories

Coverage
Odds Availability
Value Types

Odds Info
Integration
Mapping

.

Coverage

What sports are covered?

The sports coverage varies depending on configured bookmakers offering in that particular point in time. To get a list of available sports call the Sports endpoint.

What tournaments are covered?

The tournament coverage varies depending on configured bookmakers offering in that particular point in time.

To get a list of all the tournaments call the Tournaments endpoint. Alternatively, you may call the Sport Tournaments endpoint to get a list of all the tournaments for a given sport.

Which sports/leagues feature consensus bet percentage outcomes?

Bet percentage outcomes (bet_percentage_outcomes) are currently available for:

NFL
NHL
NBA
MLB

Odds Info

What is an outright?

Outrights (also known as Futures) are a flexible odds type that covers any variety of events where you have two or more competitors trying to win the same event.

The event does not have to be a physical match of any kind. For instance: “Who will win the Formula 1 Drivers Championship this year?” for which there is a long list of competitors, each with their odds for winning this outright.

What is a consensus line?

Consensus line is the most balanced line, calculated from the primary lines from configured bookmakers. There are six consensus lines that we calculate (Spread, Spread Live, Total, Total Live, Moneyline, and Moneyline Live). Each of these will display information about the opening and the current consensus line.

Consensus lines are available across all sports but their presence depends on availability of primary lines from configured bookmakers. For instance, when none of the configured bookmakers is offering “Spread” odds for a particular match, the opening and current consensus spread line will not be present.

Consensus lines are sport-dependent, which means that for Soccer the Moneyline is calculated based on 3-way odds and will have three outcomes for home, draw and away odds. For Basketball, the Moneyline is calculated based on 2-way odds and will have only two outcomes for home and away odds.

Consensus spread line in Ice Hockey is generally known as the “puck line” and in Baseball it’s known as the “run line”. In the API it will be named accordingly.

What is a consensus pick?

Consensus pick shows a percentage of bets placed on each side of the primary line. Having primary line odds does not automatically guarantee that a pick will be present. Consensus picks are included when Sportradar has information about bets being placed on a specific primary line

Odds Availability

Does it have live odds?

Yes, there are live consensus odds available, and pre-match odds data.

What markets are currently available?

Only main markets (2way, 3way, total, spread, handicap, and asian handicap), exchange odds, and outright odds are currently available. Special bet markets will become available at a later time.

How long are odds stored and provided?

Odds are removed from all endpoints after 24 hours of their completion. This will include competition and sport event information.

How do you indicate when a bookmaker withdraws a match odds or outright competitor odds?

Removed markets are indicated with a removed flag as shown below:

<market name="total" group_name="regular">
  <book id="sr:book:988" removed="true"/>
</market>

Integration

How frequently are the odds updated?

Update frequency varies between different bookmakers. The API checks for odds changes every 60 seconds and updates them as soon as changes are found in our system.

Note that we will not update the last_updated timestamp if there are no odds changes found when running the check.

What endpoint should be used to retrieve odds?

There are several endpoints through which you can retrieve odds - their usage depends on the particular use case.

Tournament Schedule - returns a list of scheduled sport events and main markets for a given tournament ID. To get a list of all tournaments call the Tournaments or Sports Tournaments endpoint.
Daily Sport Schedule - returns a list of scheduled sport events and main markets for a given sport ID and date. To get a list of all sports call the Sports endpoint.
Sport Event Markets - returns all available markets for a given match ID. To get a list of sport events call the Tournament Schedule or Sport Schedule endpoints.
Category Outrights - returns a list of outrights, outright competitors and their winning odds for a given category ID. To get a list of all the categories containing outright odds, call the Sport Categories endpoint.
Sport Event Change Log - returns a list of all the sport events where odds have changed including changed odds values and possible sport event changes.

How do I use the Change Log endpoint?

The Sport Event Change Log endpoint returns a list of all the sport events where odds have changed, including the changed odds values. It takes a Unix timestamp in UTC as a URL input parameter and must be between current UTC time -5min and current UTC time.

To avoid empty responses it's suggested to request this endpoint with regular frequency. The frequency should not be less than 60 seconds and should be a few seconds smaller than Unix timestamp, so as not to miss any odds changes and to account for the document generation time.

ex: Requesting Sport Event Change Log endpoint every 110 seconds with Unix timestamp of current UTC time - 120 seconds.

This endpoint also displays newly published matches, removed markets, and possible match scheduled time and status changes. It will not include matches and/or markets where odds values have remained unchanged.

What format are date fields presented in?

Date values are presented in the ISO 8601 standard format.

Timestamp fields are in UTC. These could include scheduled start times or play-by-play event timestamps. Examples: scheduled="2024-02-11T23:30:00+00:00", created_at="2024-02-11T23:43:20+00:00"

Date-only fields reflect local league convention and are not UTC-adjusted. These could include season start dates and birth dates. Examples: start_date="2024-08-16", date_of_birth="1984-09-22"

How do I locate the TTL (Time to Live)/cache on an API endpoint?

The cache (in seconds) can be accessed in the returned header information on each RESTful API call, under cache-control.

ex. cache-control: max-age=1, public, s-maxage=1 or
cache-control: public, must-revalidate, max-age=120

Value Types

What are the possible values for `line` – `name`?

Line names can vary by sport, and not all values may be available for all sports or events. The possible values for line– name are:

moneyline_current
moneyline_live
moneyline_open
puck_line_current
puck_line_open
run_line_current
run_line_open
spread_current
spread_live
spread_open
total_current
total_live
total_open

What are the possible values for `sport_event` - `status`?

not_started – The match is scheduled to be played
started - The match has begun
live – The match is currently in progress
postponed – The match has been postponed to a future date
suspended - The match has been suspended
match_about_to_start - The match is about to begin
delayed – The match has been temporarily delayed and will be continued
interrupted - The match began, but coverage has stopped for a short time. Note that match scores may not be updated during this period, the last recorded match score will be displayed instead
cancelled – The match has been cancelled and will not be played
ended – The match is over
closed – The match results have been confirmed

Mapping

How do you retrieve all possible results from the mapping feeds?

The mapping feeds have a limit of 30,000 results per page. To get additional results you need to use the optional query string parameters start and limit.

Optional query string parameters must be added with an ampersand (&).

For example:

curl --request GET \
     --url 'https://api.sportradar.com/oddscomparison-ust1/en/us/sport_events/id_mappings.json?start=30000&limit=30000' \
     --header 'accept: application/json' \
     --header 'x-api-key: {your_api_key}'

Why would a player ID (ex. `sr:player:830531`) appear more than once in the Player Mappings endpoint?

A player may appear in multiple APIs with a separate ID unique to that API. For example, multiple ID mapping entries could occur from the American Football API to the NFL, NCAA Men’s Football, or USFL APIs.