---
updatedAt: 2026-10-05T19:19:37.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>
    </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="#closing-lines">Closing Lines</a></li>
    </ul>
  </div>
</div>

***

# Getting Started

<div id="coverage" />

## Coverage

<br />

### What sports are covered?

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-player-props-sports) endpoint.

Possible sports in the Core package can be viewed <Anchor label="here" target="_blank" href="https://developer.sportradar.com/odds/reference/oc-core-overview#sports-coverage">here</Anchor>.

<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 <Anchor label="Sport Competitions" target="_blank" href="https://developer.sportradar.com/odds/reference/oc-prematch-sport-competitions">Sport Competitions</Anchor> endpoint.

<br />

***

<div id="integration" />

## Integration

<br />

### How can I access Odds Comparison Core?

OC Core is an expanded package which must be configured at the API key level. Reach out to your account representative or <Anchor label="Sportradar Support" target="_blank" href="mailto:support@sportradar.com">Sportradar Support</Anchor> to trial.

The OC US and OC Core access tiers, and what differs between them, are summarized on the [Odds Comparison v2 Overview](https://developer.sportradar.com/odds/docs/oc-ig-overview) in the Odds Comparison Integration Guide.

<br />

### How can I find what access I have, OC US or OC Core?

Each OC API response returns an `X-Origin-Id` header that identifies the bookmaker pipeline your key is configured for:

| `X-Origin-Id` Value            | Access Level |
| :----------------------------- | :----------- |
| `MARKET_ORIGIN_CORE_CRAWLERS`  | OC Core Key  |
| `MARKET_ORIGIN_MAGIC_CRAWLERS` | OC US Key    |

Reading the tier from the `X-Origin-Id` header is covered on the [Odds Comparison v2 Overview](https://developer.sportradar.com/odds/docs/oc-ig-overview) in the Odds Comparison Integration Guide.

<br />

### Are IDs consistent between OC US and OC Core?

All bookmaker IDs and event IDs are consistent across pipelines.

Futures IDs can differ depending on mapping.

ID consistency across tiers and across the Sportradar API families is covered on [ID Handling](https://developer.sportradar.com/odds/docs/oc-ig-id-handling) in the Odds Comparison Integration Guide.

<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 sections of the OpenAPI specifications <Anchor label="here" target="_blank" href="https://developer.sportradar.com/odds/reference/oc-core-overview#openapi-specs">here</Anchor>.

<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.

<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 />
[Back to top &uarr;](#table-of-contents)

***

# Odds Data

<div id="bookmakers" />

## Bookmakers

<br />

### What bookmakers are included?

140+ bookmakers are available in OC Core. Reach out to Sportradar Support for configuration.

Request the **Books** endpoint to view all configured bookmakers on your key.

<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.

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="odds-availability" />

## Odds Availability

<br />

### Are consensus lines available?

For OCv2 Core, consensus must be explicitly configured by Sportradar Support.

Consensus is calculated as the median of a selection of strong bookmakers, and based on the pipeline being used.

<br />

### What is the event lifecycle?

Events appear when odds become available. Event odds are removed *2 weeks after the event*.

The event lifecycle, including the two-week retention of completed events, is on [Odds Comparison Fundamentals](https://developer.sportradar.com/odds/docs/oc-ig-fundamentals) in the Odds Comparison Integration Guide.

<br />

### What if a bookmaker has no odds?

The event can still appear in our endpoints, but no odds will be shown for that bookmaker.

A 400 response may also be returned in some no-odds scenarios.

<br />

***

<div id="closing-lines" />

## Closing Lines

<br />

### How do I tell what the closing odds/line was?

When a game goes live and the pre-match markets have been removed by the bookmaker, we add a `removed="true"` attribute at the `book` level and continue to display the last known odds which can be interpreted as the closing line.

[Pulling Prematch Odds](https://developer.sportradar.com/odds/docs/oc-ig-pulling-prematch-odds) in the Odds Comparison Integration Guide shows the retained prices read as closing lines.

<br />

***

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

***

***

<br />

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

<br /><br />