> For the complete documentation index, see [llms.txt](https://docs.sportmonks.com/v3/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportmonks.com/v3/tutorials-and-guides/guides/historical-odds.md).

# Historical odds

Choose the right endpoint for odds on older fixtures or Premium pre-match price history, and understand access and retention.

“Historical odds” can mean odds for an older fixture or the record of how a pre-match price changed. Choose the endpoint that matches the data you need.

### Premium pre-match price history

The [GET All Historical Odds](https://docs.sportmonks.com/v3/endpoints-and-entities/endpoints/premium-odds-feed/premium-pre-match-odds/get-all-historical-odds) endpoint returns the historical Premium pre-match odds available in your subscription. It includes opening odds and subsequent price updates.

**Premium Odds history is available until seven days after the fixture’s starting\_at time.** It is not an unlimited archive of past seasons. Access requires the appropriate Premium Odds subscription and coverage.

```
GET https://api.sportmonks.com/v3/football/odds/premium/history?api_token=YOUR_TOKEN&include=odd&per_page=50&page=1
```

Replace YOUR\_TOKEN with your API token. This is a request template, not a captured API response. The endpoint is paginated: follow pagination.has\_more and request the next page until it is false. The maximum per\_page value is 50.

Use the odd include for the associated Premium odd. Do not request include=fixture: fixture is not a valid include on PremiumOddHistory. Each history record contains fixture\_id; retrieve fixture details separately when needed:

```
GET https://api.sportmonks.com/v3/football/fixtures/{fixture_id}?api_token=YOUR_TOKEN
```

Replace {fixture\_id} with the ID from a history record. Fixture access is subject to your subscription’s fixture coverage. See the [endpoint reference](https://docs.sportmonks.com/v3/endpoints-and-entities/endpoints/premium-odds-feed/premium-pre-match-odds/get-all-historical-odds) for the full response fields and request options.

### Odds for an older fixture

For available Standard pre-match odds attached to a known fixture, use [Get Odds by Fixture ID](https://docs.sportmonks.com/v3/endpoints-and-entities/endpoints/standard-odds-feed/pre-match-odds/get-odds-by-fixture-id):

```
GET https://api.sportmonks.com/v3/football/odds/pre-match/fixtures/{fixture_id}?api_token=YOUR_TOKEN
```

The [Standard Odds Feed](https://docs.sportmonks.com/v3/endpoints-and-entities/endpoints/standard-odds-feed) documents no age cutoff for its odds-by-fixture-ID endpoints, with available coverage going back to approximately 2018. Availability depends on the league’s odds coverage and your odds access; this is not a guarantee that every older fixture has odds.

Odds attached to an older fixture and the full record of Premium price changes are different data. Use Premium history when you need opening prices and subsequent updates within its retention window.

### Does the Historical Data add-on extend odds history?

No. The Historical Data add-on unlocks older football seasons beyond the default three most recent seasons per league. It does not grant odds access, extend Premium Odds history retention, or restore expired price history. Access to older fixtures through the fixtures endpoints and access to odds are governed separately.

**Historical data is always included in all Special Plans and Enterprise Plans.** These plans do not require a separate Historical Data add-on. Odds access and Premium history retention still apply separately.

### Before requesting historical odds

* Check whether you need odds for a fixture or Premium price-change history.
* Confirm the required odds access and league coverage in your subscription.
* For Premium history, check the fixture’s starting\_at time against the seven-day retention limit.
* Use only the includes supported by that endpoint and follow its pagination.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sportmonks.com/v3/tutorials-and-guides/guides/historical-odds.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
