Links

API Changes

States and Types

We introduced states and types to ensure data quality and consistency for specific fields.

States

A fixture moves between several statuses. It has an initial status (NS), can be delayed (DELA), has been finished (FT) or any of the statuses described on the states page. You could also use the states endpoint to retrieve all possible states.

Types

Something has a type, when there are multiple variants of a certain variant.
For example, types for referees. Referees can be the head referee, the assistant referee or the fourth official. Due to types we qualify which variant of the belonging entity the specific referee is.
This was introduced to ensure all sports will follow the exact same structure in API 3.0.
New types: Position ID and detailed position ID are new types. Also, periods, sidelined, referees, events, standings, metadata, formations, colors, injuries, suspensions, predictions, and stats contain fields that belong to a type.

Strict typing

Strictly typed languages enforce typing on all data being interacted with. All data types strictly conform to standard JSON notations. In addition to data types being stricter, we also added types to various entities to ensure higher data consistency.

Scores

In API 2.0 the scores of a fixture are in the default API response. In API 3.0 this is not the case. For API 3 we've introduced the scores include. This has been added to retrieve a score for fixtures more conveniently. The include returns the scores per period and the current score for the regarding fixture.

Participants vs localTeam & visitorTeam include

This might be one of the most important model changes in API 3.0. Previously, localTeam and visitorTeam were the includes to use to get all team data. The previous includes are replaced by our new include: participants.From now on, this is the way to get information about the teams participating in a match.
Both teams that play in the fixture are present in the participants array and their location is located in the meta section of a team. Below is an example of how a fixture with this new include can look.
Example
{
"data": {
"id": 18535517,
"sport_id": 1,
"league_id": 501,
"season_id": 19735,
"stage_id": 77457866,
"group_id": null,
"aggregate_id": null,
"round_id": 274719,
"state_id": 5,
"venue_id": 8909,
"name": "Celtic vs Rangers",
"starting_at": "2022-09-03 11:30:00",
"result_info": "Celtic won after full-time.",
"leg": "1/1",
"details": null,
"length": 90,
"placeholder": false,
"last_processed_at": "2023-03-02 17:47:38",
"has_odds": true,
"starting_at_timestamp": 1662204600,
"scores": [
{
"id": 11316768,
"fixture_id": 18535517,
"type_id": 1,
"participant_id": 53,
"score": {
"goals": 3,
"participant": "home"
},
"description": "1ST_HALF"
},
{
"id": 11316769,
"fixture_id": 18535517,
"type_id": 1,
"participant_id": 62,
"score": {
"goals": 0,
"participant": "away"
},
"description": "1ST_HALF"
},
{
"id": 11316770,
"fixture_id": 18535517,
"type_id": 2,
"participant_id": 53,
"score": {
"goals": 4,
"participant": "home"
},
"description": "2ND_HALF"
},
{
"id": 11316771,
"fixture_id": 18535517,
"type_id": 2,
"participant_id": 62,
"score": {
"goals": 0,
"participant": "away"
},
"description": "2ND_HALF"
},
{
"id": 11316772,
"fixture_id": 18535517,
"type_id": 1525,
"participant_id": 53,
"score": {
"goals": 4,
"participant": "home"
},
"description": "CURRENT"
},
{
"id": 11316773,
"fixture_id": 18535517,
"type_id": 1525,
"participant_id": 62,
"score": {
"goals": 0,
"participant": "away"
},
"description": "CURRENT"
}
],
"participants": [
{
"id": 53,
"sport_id": 1,
"country_id": 1161,
"venue_id": 8909,
"gender": "male",
"name": "Celtic",
"short_code": "CEL",
"image_path": "https://cdn.sportmonks.com/images/soccer/teams/21/53.png",
"founded": 1888,
"type": "domestic",
"placeholder": false,
"last_played_at": "2023-02-26 15:00:00",
"meta": {
"location": "home",
"winner": true,
"position": 1
}
},
{
"id": 62,
"sport_id": 1,
"country_id": 1161,
"venue_id": 8914,
"gender": "male",
"name": "Rangers",
"short_code": "RAN",
"image_path": "https://cdn.sportmonks.com/images/soccer/teams/30/62.png",
"founded": 1873,
"type": "domestic",
"placeholder": false,
"last_played_at": "2023-02-26 15:00:00",
"meta": {
"location": "away",
"winner": false,
"position": 2
}
}
],
"periods": [
{
"id": 4295921,
"fixture_id": 18535517,
"type_id": 1,
"started": 1662204680,
"ended": 1662207533,
"counts_from": 0,
"ticking": false,
"sort_order": 1,
"description": "1st-half",
"time_added": 2,
"period_length": 45,
"minutes": null,
"seconds": null
},
{
"id": 4296154,
"fixture_id": 18535517,
"type_id": 2,
"started": 1662208498,
"ended": 1662211318,
"counts_from": 45,
"ticking": false,
"sort_order": 2,
"description": "2nd-half",
"time_added": 2,
"period_length": 45,
"minutes": null,
"seconds": null
}
]
},
​

Rate limit per entity

The rate limit will now be based on requests per entity instead of being based on a single endpoint. For example, the Team entity is used in Teams endpoints. You can find out more about the rate limit here.

Pagination

A new pagination system has been implemented. In API 3.0, we will no longer provide a count and total_pages property in the meta of the response. Instead, you can paginate using the has_more parameter to determine if you can still propagate through results. This change decreases the load on our databases and massively increases API response speed and reliability.
In addition to that it is now possible to add the filters=populate to your query parameter. This parameter allows for a higher pagination limit (max 1000), so you can populate your database more conveniently instead of using the default pagination limit of 50. To prevent our services from overloading, using includes is disabled when this filter is added to the request.
Please check our pagination tutorial for more info.

Core and odds

​Core and odds are no longer sport specific. Both have their own documentation related to all sports released on API 3.0. Odds contain bookmakers and markets which are not sport specific but Odds are still available on a per sport basis.