> 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/international-tournaments/live-matches-livescores-and-events.md). # Live matches, livescores & events The 2026 Tournament is one of the few moments where millions of fans are watching the same match at the same time. This chapter covers how to retrieve live match data, in-play events, and real-time scores for tournament 2026 fixtures. ### Getting live tournament matches There are three livescores endpoints depending on what your application needs. [**GET Inplay Livescores**](https://docs.sportmonks.com/v3/endpoints-and-entities/endpoints/livescores/get-inplay-livescores) returns all currently live fixtures: ```http https://api.sportmonks.com/v3/football/livescores/inplay ?api_token=YOUR_TOKEN ``` [**GET All Livescores**](https://docs.sportmonks.com/v3/endpoints-and-entities/endpoints/livescores/get-all-livescores) returns fixtures from 15 minutes before kick-off until 15 minutes after the final whistle: ```http https://api.sportmonks.com/v3/football/livescores ?api_token=YOUR_TOKEN ``` [**GET Latest Updated Livescores**](https://docs.sportmonks.com/v3/endpoints-and-entities/endpoints/livescores/get-latest-updated-livescores) returns only fixtures that have had changes in the last 10 seconds. This is the most efficient option for a polling loop (your app only processes what has actually changed): ```http https://api.sportmonks.com/v3/football/livescores/latest ?api_token=YOUR_TOKEN ``` All three endpoints return fixtures based on the leagues in your subscription. To filter to Tournament matches only, add the league filter (League ID: 732): ```http https://api.sportmonks.com/v3/football/livescores/inplay ?api_token=YOUR_TOKEN&filters=fixtureLeagues:732 ``` ### Enriching livescores with includes By default, livescores return a lean response. Use the `include` parameter to pull in everything you need in a single request. For a typical match centre view with scores, events, and teams: ```http https://api.sportmonks.com/v3/football/livescores/inplay ?api_token=YOUR_TOKEN&filters=fixtureLeagues:732 &include=scores;participants;statistics.type;events;lineups ``` Available includes on the livescores endpoints include `scores`, `participants`, `events`, `lineups`, `state`, `periods`, `statistics`, `venue`, and more. See the individual endpoint pages for the full list. ### Retrieving in-play events The `events` include returns the full match event timeline (goals, cards, substitutions, and more), directly in your fixture response. Each event has a `type_id` that maps to the [Types entity](https://docs.sportmonks.com/v3/endpoints-and-entities/entities/types). Use the [GET All Types](https://docs.sportmonks.com/v3/endpoints-and-entities/endpoints/types/get-all-types) endpoint to look up the label for any `type_id`. ### Getting data for a specific match If you already know the fixture ID, for example, from the season schedule, you can pull everything for that match in one request using [GET Fixture by ID](https://docs.sportmonks.com/v3/endpoints-and-entities/endpoints/fixtures/get-fixture-by-id): ```http https://api.sportmonks.com/v3/football/fixtures/19609149 ?api_token=YOUR_TOKEN&include=events;scores;state;participants;lineups ``` This is the most efficient approach for a dedicated match page. {% hint style="info" %} **Note:** For in-play fixtures, use the livescores endpoints rather than the fixtures endpoints. The fixtures endpoints are better suited for pre-match and historical data. {% endhint %} ### Lineups for tournament fixtures The `lineups` include returns the starting XI, substitutes, positions, and shirt numbers for both teams. Official lineups are typically confirmed around 60–75 minutes before kick-off, before that, the array will be empty for that fixture. ### Live standings during the group stage Group standings update in real time as matches are played. Use the live standings endpoint with the correct season ID: ```http https://api.sportmonks.com/v3/football/standings/live/leagues/732 ?api_token=YOUR_TOKEN ``` This is the same standings data covered in the [Displaying season standings](https://docs.sportmonks.com/v3/world-cup-2026/how-to-build-your-world-cup-application#displaying-season-standings) section, but updates dynamically during matches. ### Handling the `is_placeholder` property As covered in the season schedule section, knockout round fixtures will have `placeholder: true` until the qualifying teams are confirmed. The same applies at the participant level. Filter out placeholder teams before rendering names or crests: ```javascript const liveMatches = response.data.filter(fixture => !fixture.placeholder); ``` ### What to build next With live match data, events, and lineups in place, you can extend your application further: * **Match statistics** — use the `statistics` include or the [Statistics endpoints](https://docs.sportmonks.com/v3/endpoints-and-entities/endpoints/statistics) for possession, shots, passes, and more * **Live standings** — see the live standings endpoint above * **Odds and predictions** — available via add-on; see [Odds and Predictions](https://docs.sportmonks.com/v3/tutorials-and-guides/tutorials/odds-and-predictions) --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.sportmonks.com/v3/international-tournaments/live-matches-livescores-and-events.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.