Table of Contents

Getting Started

Coverage

What sports are covered?

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

What competitions are covered?

The competition coverage varies depending on what configured bookmakers are offering in that particular point in time. To get a list of all the competitions for a sport call the Sport Competitions endpoint.

Integration

How can I find the values for various enum data points within the API?

For the most up-to-date values, please see the Schema section of the OpenAPI specification here.

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

Back to top ↑

Odds Data

Odds Availability

How long are odds stored and provided?

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

Mapping

What is the best method to map IDs from the Odds Comparison API to other Sportradar APIs?

The Mapping API is the recommended solution for linking entity IDs across Sportradar products. It supports mapping for competitions, competitors, players, seasons, and sport events, and is designed to scale across multiple APIs without the need to paginate through large feeds.

If you need to map IDs specifically within the Odds Comparison API, dedicated Mapping feeds are also available. These feeds provide ID mappings for players, competitions, sport events, teams, and stages between General Sport IDs and League Specific IDs.

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.

Back to top ↑