GET Updated Historical Odds Between Time Range

Returns the historical (premium) pre-match odds updated between a range of timestamps. The maximum time range is 5 minutes.

Our Premium Odds Feed provides a history of pre-match odds for fixtures for up to 7 days after the match has started. Additionally, we offer the history of the odd. We document the opening odds for each fixture, and subsequently, all changes and updates are stored and accessible for your use. So, every (historical) odd value is available for a fixture until 7 days after the match has started (the 'starting_at' timestamp of the fixture).

Base URL

https://api.sportmonks.com/v3/football/odds/premium/history/updated/between/{from}/{to}

Example Response

{
  "data": [
  {
        "id": 351780754,
        "odd_id": 1028288850,
        "value": "1.78",
        "probability": "56.18%",
        "dp3": "1.780",
        "fractional": "39/50",
        "american": "78",
        "bookmaker_update": "2023-11-13 21:15:25"
    },
    {
        "id": 351780753,
        "odd_id": 1028288849,
        "value": "1.82",
        "probability": "54.95%",
        "dp3": "1.820",
        "fractional": "41/50",
        "american": "82",
        "bookmaker_update": "2023-11-13 21:15:25"
    },
    {
        "id": 351780750,
        "odd_id": 1019766847,
        "value": "2.16",
        "probability": "46.3%",
        "dp3": "2.160",
        "fractional": "29/25",
        "american": "116",
        "bookmaker_update": "2023-11-13 21:15:25"
    },
]

Field Description

Field	Description	Type
id	Unique id of the Premium Odd entity	int
odd_id	The id of the PremiumOdd entity the records belongs to	int
value	The (historical) value of the referring premium odd	string
probability	Displays the probability odd	string
dp3	Displays the dp3 odd	string
fractional	Displays the fractional odd	string
american	Displays the american odd	string
bookmaker_update	Returns the timestamp of the bookmakers latest update	datetime

Since this endpoint may return lots of data, we recommend using the populate filter to allow a maximum of 1000 results per page to be returned.

Query Parameters

Name	Required?	Description
api_token	YES Another option is to provide the API token in the header.	Your unique API token. Ex. ?api_token=YOUR_TOKEN
include	NO	Enrich the API response with more data by using includes. Ex. &include=fixture;bookmaker;market
select	NO	Select specific fields on the base entity. Read how to select fields in our tutorial.
filters	NO	Filter the API response on multiple related entities. There are static filters and dynamic filters.​ Please find the possibilities in the Static and Dynamic Filter tab.
locale	NO	Translate name fields of the API Response in your selected language. Find more information and which languages are available on our translations page.

Static Filters

Static filters are always the same and filter in one specific way without any custom options. Each static filter is listed below and has a description of how it filters. For more information, please look at our Filters page.

Static Filters	Available on Entity	Description	Example
markets	Odds	Filter the odds on a selection of markets separated by a comma.	&filters=markets:marketIDs &filters=markets:12,14
bookmakers	Odds	Filter the odds on a selection of bookmakers separated by a comma. (e.g: 2,14).	&filters=bookmakers:bookmakerIDs &filters=bookmakers:2,14

Dynamic Filters

The dynamic filters are based on entities and includes. Each dynamic filter uses an entity to filter on and one entity to apply the filter to. Below is an example with an explanation of how filters are set up. For more information, please look at our Filters page.

Using an include? Check their respective filters on their entity page. For example if you use &include=fixtures, you can apply fixture-related filters.

Dynamic Filters	Available on Entity	Description	Examples
N/A	N/A	Not available for this endpoint.	N/A

Filters

More information on how to use filters can be found on our tutorials on how to filter. If you want more information on which filters to use you can check out the following endpoint:

https://api.sportmonks.com/v3/my/filters/entity?api_token=YOUR_TOKEN

Pagination

YES

Parameters

Parameter	Required	Description	Example
order	No	Returns odds ordered by bookmaker_update (asc or desc). Defaults to desc	&order=asc
per_page	No	The amount of results to return per page (max 50.). Defaults to 25.	&per_page=30
page	No	You can paginate using the has_more parameter to determine if you can still propagate through the results.	&page=2

Include depth

You can use a total of 1 nested includes on this endpoint

Include options

odd

Related entities

PremiumOdd

Postman

We also offer detailed postman documentation with examples and a complete up-to-date version of all our endpoints. Below is a button that lets your fork the collection or import it.