---
updatedAt: 2026-10-05T19:19:35.000Z
agentTools:
  siteIndex: https://developer.sportradar.com/llms.txt
  projectIndex: https://developer.sportradar.com/odds/llms.txt
---

# FAQs

Browse by category below. Select any group or question to jump straight to it. Use your browser's find (**Ctrl/Cmd + F**) to search the page.

## Table of Contents

<div style={{
  display: "flex",
  flexWrap: "wrap",
  gap: "16px",
  margin: "20px 0 8px 0"
}}>
  <div style={{
    flex: "1 1 240px",
    minWidth: "220px",
    border: "1px solid var(--md-code-background, #e1e4e8)",
    borderRadius: "8px",
    padding: "16px 18px"
  }}>
    <p style={{ marginTop: 0, marginBottom: "10px", fontSize: "1rem", fontWeight: 600 }}>
      <a href="#getting-started" style={{ textDecoration: "none" }}>Getting Started</a>
    </p>
    <ul style={{ listStyle: "none", paddingLeft: 0, margin: 0 }}>
        <li style={{ margin: "0 0 6px 0" }}><a href="#coverage">Coverage</a></li>
        <li style={{ margin: "0 0 6px 0" }}><a href="#integration">Integration</a></li>
        <li style={{ margin: "0 0 6px 0" }}><a href="#pagination">Pagination</a></li>
    </ul>
  </div>

  <div style={{
    flex: "1 1 240px",
    minWidth: "220px",
    border: "1px solid var(--md-code-background, #e1e4e8)",
    borderRadius: "8px",
    padding: "16px 18px"
  }}>
    <p style={{ marginTop: 0, marginBottom: "10px", fontSize: "1rem", fontWeight: 600 }}>
      <a href="#odds-data" style={{ textDecoration: "none" }}>Odds Data</a>
    </p>
    <ul style={{ listStyle: "none", paddingLeft: 0, margin: 0 }}>
        <li style={{ margin: "0 0 6px 0" }}><a href="#bookmakers">Bookmakers</a></li>
        <li style={{ margin: "0 0 6px 0" }}><a href="#odds-availability">Odds Availability</a></li>
        <li style={{ margin: "0 0 6px 0" }}><a href="#mapping">Mapping</a></li>
    </ul>
  </div>
</div>

***

# Getting Started

<div id="coverage" />

## Coverage

<br />

### 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](https://developer.sportradar.com/odds/reference/oc-live-odds-sports) endpoint.

<br />

### What competitions are covered?

The competition coverage varies depending on configured bookmakers offering in that particular point in time. To get a list of all the competitions for a sport call the [Sport Competitions](https://developer.sportradar.com/odds/reference/oc-live-odds-sport-competitions) endpoint.

Discovering the sports and competitions with odds, and reading the per-competition coverage flags, is walked through on [API Basics](https://developer.sportradar.com/odds/docs/oc-ig-api-basics) in the Odds Comparison Integration Guide.

<br />

### What markets are available?

All in-game markets which bookmakers make available in the [Prematch](https://developer.sportradar.com/odds/reference/oc-prematch-overview) and [Player Props](https://developer.sportradar.com/odds/reference/oc-player-props-overview) packages will be available in the Live Odds game endpoints.

Currently we guarantee that Moneyline, Spread and Total will be available.

[Tracking Live Odds](https://developer.sportradar.com/odds/docs/oc-ig-tracking-live-odds) in the Odds Comparison Integration Guide follows the live board market by market through a game, from the pre-game board to the final.

<br />

***

<div id="integration" />

## Integration

<br />

### 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](https://api.sportradar.com/oddscomparison-liveodds/production/v2/openapi/swagger/index.html).

<br />

### What format are date fields presented in?

Date values are presented in the [ISO 8601](https://en.wikipedia.org/wiki/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"`

Timestamps across the API are covered on [API Basics](https://developer.sportradar.com/odds/docs/oc-ig-api-basics) in the Odds Comparison Integration Guide; the date window of the Daily Sport Event Schedule feed is on [Tracking Live Odds](https://developer.sportradar.com/odds/docs/oc-ig-tracking-live-odds).

<br />

### 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`

Every feed's TTL, with recommended polling cadences and the bookmaker price refresh cycle per package, is charted on [Update Frequencies](https://developer.sportradar.com/odds/docs/oc-ig-update-frequencies) in the Odds Comparison Integration Guide.

<br />

***

<div id="pagination" />

## Pagination

<br />

### How do I access all games in the Competition Player Props or Daily Player Props endpoints?

The [Competition Player Props](https://developer.sportradar.com/odds/reference/oc-live-odds-competition-player-props-schedule) and [Daily Player Props](https://developer.sportradar.com/odds/reference/oc-live-odds-daily-player-props) endpoints return one (1) `sport_event` per request.

Reference the **x-max-results** header to locate the number of sport events available for each, then make additional requests using the `start` parameter to obtain each available event.

In the below [Competition Player Props](https://developer.sportradar.com/odds/reference/oc-live-odds-competition-player-props-schedule) response, the header specifies 1 sport event is returned (`x-result`), but 15 sport events are available (`x-max-results`). Make additional API requests – appending `&start=1`, `&start=2`, etc. to the end of your call – to obtain additional events.

```text
Response Header Sample
< HTTP/2 200 
< content-type: application/xml
< content-length: 517078
< date: Tue, 11 Feb 2025 19:04:27 GMT
< x-amzn-requestid: 28294a6b-3a7f-4c71-87c1-6feecec8b02d
< x-offset: 0
< x-amz-apigw-id: F1XRQGH1liAEKgQ=
< cache-control: no-cache, private
< x-result: 1
< etag: "e128f66ea2b55555e7923e0f863b3b29"
< x-max-results: 15
< x-amzn-trace-id: Root=1-67ab9f3a-56e9db0b3d7122cb23aa65fc
< x-amzn-remapped-date: Tue, 11 Feb 2025 19:04:27 GMT
< vary: Accept-Encoding
< x-cache: Miss from cloudfront
```

[Back to top ↑](#table-of-contents)

***

# Odds Data

<div id="bookmakers" />

## Bookmakers

<br />

### What bookmakers are included?

Request the [Books](https://developer.sportradar.com/odds/reference/oc-live-odds-books) endpoint for a complete list of your available bookmakers. Current bookmakers are:

* MGM
* DraftKings
* FanDuel
* SugarHouseNJ
* PointsBet
* WilliamHillNewJersey
* FoxBetNewJersey

<br />

### What happens if a bookmaker suspends/removes a market or outcome?

Markets that have been suspended/removed are indicated as `removed="true"` at the `book` level.

Outcomes that have been suspended/removed are indicated by `removed="true"` at the `outcome` level.

How `removed` flips per book from poll to poll during play is shown on [Tracking Live Odds](https://developer.sportradar.com/odds/docs/oc-ig-tracking-live-odds) in the Odds Comparison Integration Guide.

<br />

***

<div id="odds-availability" />

## Odds Availability

<br />

### What is the refresh rate of the Live Odds data?

We check for changes to the data every 15-30 seconds.

The refresh cycle for each package, and a polling cadence for events in play, are on [Update Frequencies](https://developer.sportradar.com/odds/docs/oc-ig-update-frequencies) in the Odds Comparison Integration Guide.

<br />

### Why do some outcomes show nonsensical odds?

If an outcome is flagged as `removed="true"` and is displaying decimal odds of `1.00`, then the selection was never offered for betting by the bookmaker. This will often happen on "under" selections where the bookmaker does not want to offer the "under" side of the bet.

The `removed` lifecycle at book and outcome level is explained on [Odds Comparison Fundamentals](https://developer.sportradar.com/odds/docs/oc-ig-fundamentals) in the Odds Comparison Integration Guide.

<br />

***

<div id="mapping" />

## Mapping

<br />

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

The <Anchor label="Mapping API" target="_blank" href="https://developer.sportradar.com/odds/reference/mapping-overview">Mapping API</Anchor> 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](https://developer.sportradar.com/odds/reference/oc-live-odds-competition-mappings) are also available. These feeds provide ID mappings for players, competitions, sport events, teams, and stages between General Sport IDs and League Specific IDs.

[ID Handling](https://developer.sportradar.com/odds/docs/oc-ig-id-handling) in the Odds Comparison Integration Guide walks through joining odds to the League Specific APIs, and the [Mapping API Integration Guide](https://developer.sportradar.com/odds/docs/mapping-ig-overview) covers the entity-level lookups.

<br />

### 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 UFL APIs.

<br />

***

[Back to top ↑](#table-of-contents)

***

<Callout icon="🙋" theme="default">
  ### More questions?
  Reach out to **[mediasupport@sportradar.com](mailto:mediasupport@sportradar.com)** for further assistance.
</Callout>

<br /><br />