Changelog
Since the release of API3 and onwards, we will list any additions and changes made in the API on this page, in chronological order (YYYY-MM-DD format)
2025-03-10
Two new filters have been added to the API for enhanced flexibility and customization:
HavingPremiumOdds filter Allows users to filter out any fixtures not having premium odds available. Similar to the havingOdds filter for out default odds field. The filter can be applied on fixture entities.
Gender filter Enables users to filter teams or players based on a specific gender (
male
,female
, ornull
). If a player's gender is (yet) unknown, it is assigned a default value ofnull
.
2025-01-22
With the release of our new data-processing logic, we’ve introduced new types to better distinguish between extra time periods and their individual halves.
Previously, there was only a single period type for extra time: ET (type_id: 3). Now, extra time has been separated into two distinct types:
ET_1ST_HALF (type_id: 5314)
ET_2ND_HALF (type_id: 39).
To take advantage of these improvements, a new API include called detailedPeriods
has been added. This include provides detailed information about periods, including the separation of extra time into its two halves.
In addition, events now include a detailed_period_id
, which points to the corresponding detailedPeriod
.
We strongly encourage all users to adopt this new structure to ensure greater consistency and accuracy in your applications. In the near future, we will make every effort to back populate historical fixtures with these detailed periods, to provide a more seamless experience with periods.
2024-11-04
We've introduced a new metadata type, Prediction Status, to the Fixture entity. This metadata provides an indicator named predictable to indicate if the prediction model could accurately make fixture predictions.
If the model can't make accurate fixture predictions, the value of predictable will be false, and there will be no predictions available for that fixture.
2024-09-30
A new include call rankings has been added to the API. You may use this include on a Team to get information about the coefficient rankings for the desired team. We continue to expand our coverage regarding these rankings.
2024-09-10
By assigning a unique sort order to each event within a type, users can more easily organize and display events in a sequential manner based on their occurrence. This feature allows for a more intuitive and efficient way to identify, browse and filter events.
2024-08-11
We're excited to announce new enhancements to our xG statistics, now available at the season level!
2024-05-12
We're excited to announce the launch of Expected Goals (xG) metrics in the Sportmonks API! With the addition of xG data, users can now access valuable insights into goal-scoring probabilities, enhancing their football analysis and decision-making processes.
What's New?
2024-04-05
2024-03-21
Periods now show the elapsed minute and seconds even though a period is no longer ticking.
2024-02-26
Introducing the ability to perform custom sorting on Sportmonks API3 endpoints! With this enhancement, users can now include the
sortBy
parameter to sort base entities in ascending or descending order. The feature supports sorting on fields likestarting_at
andname
for fixtures, providing users with greater flexibility in organising and retrieving data.
2023-11-27
Periods now contain a has_timer attribute. It marks whether we have detailed timer information for minutes and seconds attributes available.
Minor updates and optimisations to our back-end infrastructure.
2023-11-13
2023-10-30
2023-09-21
A new event type has been implemented which tracks VAR checks related to cards. From today onwards all VAR events that are related to cards are covered under the VAR_CARD event type.
2023-09-13
2023-09-06
Both Referee and Coach entities now offer the possibility to add the latest include. The include providers their latest fixtures records from the past 6 months.
2023-09-04
When available, a code field has been added to the API error response, these errors include a link to our documentation pages where the errors are explained more briefly. The code corresponds to one of the entries in the listed table.
When using the statistics include on a Season, using the nested Type include caused the original type field for the object to be overridden. To prevent this behaviour from happening, the relational Type object will now be available under the statistic_type attribute.
2023-08-15
TV station BT Sport has been renamed to TNT Sports due to rebranding. (affecting ID 46 and 860). TNT Sports 2, 3, 4 are newly added under ID 928, 929, 930.
2023-07-18
An is_captain indicator has been added for Squads. Showing true if the player is currently the default captain for the regarding squad.
Using filters that allow you to pass id's, now support a maximum of 50 records. This reflects the maximums (per_page) we allow on default paginated endpoints.
2023-06-08
A new include called 'currentPeriod' has been added. It allows for retrieval of the inplay period in a more convenient way compared to using the periods include. Please note the include may return NULL. For example when the match has not yet started, is in half-time, or has ended.
The PlayerStatistic entity now contains a has_values field, indicating whether a Player has any statistics available for the given season.
We have renamed the BEATS type to SUCCESSFUL_DRIBBLES to better reflect the type of statistic.
2023-05-31
2023-05-30
We have added the currentPeriod include. You can use this as a more convenient way to get the current inplay period for a fixture. Note that the result can be null, for example when the fixture itself is not inplay or the fixture is currently in half-time break.
2023-05-17
2023-04-28
The developer name of Type "Screwsnails Removal" (id: 830) has been renamed to SCREWS_NAILS_REMOVAL for naming convention.
2023-04-18
As per an earlier announcement, we have released some changes to the API on this date.
Removed fields:
State: is_live, is_pending, is_period_end, is_final_state, is_cancelled, is_final_standing_state, is_completed, type_id, is_deleted, is_notstarted, period_length_setting, deactivate_inplay
Period: period_length_internal, final_minute, home_score, away_score
Fixture: last_processed_at
Renamed fields:
Squad: yersey_number was renamed to jersey_number
Added fields:
League: category (basic tier like indicator for the size / popularity of the league. Ranges from 1-4, where 1 are the most 'popular' leagues.
Ordering on endpoints:
Threshold adjustments:
Last updated
Was this helpful?