> For the complete documentation index, see [llms.txt](https://docs.thesports.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thesports.com/help-center/football/how-to-use-odd-data.md).

# How to use odd data？

### Odds API endpoint comparison

1. [**Real-time odds**](/thesports-docs/odds-data/real-time-odds.md): Returns odds updates generated within the past 60 seconds. 
   * Use this API endpoint to retrieve real-time odds changes.
2. [**Single match odds**](/thesports-docs/odds-data/single-match-odds.md): Returns the complete odds data for the match specified by the `match id` parameter. 
   * Use this API endpoint to retrieve any odds data missing from **Real-time odds** API endpoint.

### Recommended usage

For all completed matches and selected upcoming matches, preferably those scheduled within the next two weeks, first use **Single match odds** API endpoint to retrieve the complete odds data for each match. Then use **Real-time odds** API endpoint to retrieve subsequent odds changes.

### Identifying Initial, Instant, and Rolling Ball odds

The odds list is sorted in reverse chronological order, with the newest record first.

#### **Initial**

Initial is the first odds record published for a match. Because the list is in reverse chronological order, the last record in the list is the Initial odds.

```
List: [1, 2, 3, 4]
Initial odds: 4
```

#### **Instant**

Instant refers to all odds records published after the Initial odds and before the match starts.

```
List: [1 (first half), 2 (not started), 3 (not started), 4 (Initial)]
Instant odds: 2 and 3
```

#### **Rolling Ball**

Rolling Ball refers to all odds records published after the match starts.

```
List: [1 (first half), 2 (first half), 3 (not started), 4 (not started), 5 (Initial)]
Rolling Ball odds: 1 and 2
```

<figure><img src="/files/pdy4GDF3PmIJJQD1Z7Bq" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/sk0tZtlVFhVoZhCLlxtp" alt=""><figcaption></figcaption></figure>

### How to use the Odds update API endpoint

Odds data may occasionally be corrected after publication. Neither **Real-time odds** nor **Single match odds** API endpoint provides correction notifications.

[**Odds update**](/thesports-docs/odds-data/odds-update.md) API endpoint returns corrections made within the past 60 seconds, including the odds `company_id`, `match_id`, and correction time. Use the returned odds `company_id` and `match_id` to retrieve the corrected data from **Single match odds** API endpoint.

### How to set a unique key for the Real-time odds API endpoint

The same odds data may change multiple times at the same timestamp. To prevent duplicate records, combine all returned fields into a composite unique key.

### Mapping between odds types and values

| Odds type | Values                       |
| --------- | ---------------------------- |
| `asia`    | Home win, handicap, away win |
| `eu`      | Home win, draw, away win     |
| `bs`      | Over, handicap, under        |
| `cr`      | Over, handicap, under        |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.thesports.com/help-center/football/how-to-use-odd-data.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.