GET Latest Updated Fixtures

https://api.sportmonks.com/v3/football/fixtures/latest

{
    "data": [
        {
            "id": 19238160,
            "sport_id": 1,
            "league_id": 1412,
            "season_id": 22988,
            "stage_id": 77469045,
            "group_id": null,
            "aggregate_id": null,
            "round_id": null,
            "state_id": 1,
            "venue_id": null,
            "name": "Tersana vs El Gounah",
            "starting_at": "2024-08-08 15:00:00",
            "result_info": null,
            "leg": "1/1",
            "details": null,
            "length": 90,
            "placeholder": false,
            "has_odds": true,
            "has_premium_odds": true,
            "starting_at_timestamp": 1723129200
        },
        {
            "id": 19238159,
            "sport_id": 1,
            "league_id": 1412,
            "season_id": 22988,
            "stage_id": 77469045,
            "group_id": null,
            "aggregate_id": null,
            "round_id": null,
            "state_id": 1,
            "venue_id": 4568,
            "name": "Pyramids FC vs Abu Qir Semad",
            "starting_at": "2024-08-08 15:00:00",
            "result_info": null,
            "leg": "1/1",
            "details": null,
            "length": 90,
            "placeholder": false,
            "has_odds": true,
            "has_premium_odds": true,
            "starting_at_timestamp": 1723129200

Definition of “Latest Updated”

This endpoint returns all fixtures whose livescore data has changed within the last 10 seconds. It tracks changes to these fields: state_id, venue_id, name, starting_at, result_info, leg, length, placeholder, has_odds, has_premium_odds, and starting_at_timestamp. The update window is fixed at 10 seconds and cannot be altered.

Changes to each field mean the following:

• State_id > the match phase progressed (for example, from 1 to 2 at kick-off or from 2 to 3 at half-time)

• Venue_id > the assigned venue was updated (for example, moved from stadium A to stadium B)

• Name > the fixture name text was modified (for example, team abbreviations or formatting changed)

• Starting_at > the kick-off time string was rescheduled (for example, “2024-08-04 15:30:00” to “2024-08-04 16:00:00”)

• Starting_at_timestamp > the UNIX timestamp for kick-off was rescheduled (for example, 1722785400 to 1722787200)

• Result_info > the score summary text was updated (for example, “0-0” to “1-0”)

• Leg > the leg designation changed (for example, “1/2” to “2/2”)

• Length > the fixture duration changed (for example, 90 to 120 when extra time is added)

• Placeholder > whether the correct teams have been confirmed or not

• Has_odds > whether the match has odds available or not

• Has_premium_odds > whether the match has premium odds available or not

Frequency of updates & no-change responses

On each call, any fixture that experienced a change to one or more of the tracked fields in the last 10 seconds will be returned in the data array. If no fixture changed during that window, the API returns HTTP 200 with "data": [], signalling that there is nothing new to process.

Polling frequency & rate limits

• To reduce end-to-end latency, we highly recommend polling every 5 to 8 seconds if your rate limits allow.

• Monitor for network jitter: slight timing shifts can cause overlap or small gaps. Adjust polling intervals if you see missed updates or duplicate data.

Caching strategy & best practices

• Cache only the tracked fields per fixture in a local store.

• On each response:

  1. Compare incoming values to your cache.

  2. Discard fixtures with no differences.

  3. Process fixtures with changes and update your cache entries.

• Cache lookup data (such as team names and league info) locally, since it changes rarely.

• If you encounter long runs of empty responses, back off on polling frequency or check for network issues to avoid unnecessary calls.

Filters

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

Pagination

NO

Include depth

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

Include options

sport round stage group aggregate league seasoncoaches tvStations venue state weatherReport lineups events timeline comments trends statistics periods participants oddspremiumOdds inplayOdds prematchNews postmatchNews metadata sidelinedpredictions referees formations ballCoordinates scores xGFixture pressure expectedLineups predictedLineups matchfacts AIOverviews

Related Entities:

Get an overview and explanation of all the fields returned in the API response. The related entities for the fixtures endpoints are:

• Fixture

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.

Code Example