> 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/motorsport-api/tutorials-and-guides/tutorials/live-data.md).

# Live data

The Motorsport API provides real-time session data as a race unfolds. This section covers how to access live data, how session states work, and how to structure your polling strategy.

### In this section

* **Live sessions** - How to request currently active sessions, what data is available live, and how to poll efficiently.
* **Session states** - The state lifecycle from scheduled through to finished, and how to detect when a session goes live.

### How live data works

Live data is available via the Live endpoints, which return all currently active sessions:

```http
https://api.sportmonks.com/v3/motorsport/livescores
?api_token=YOUR_TOKEN
```

You can enrich the live response with results, lineups, laps, and pitstops using the `&include=` parameter:

```http
https://api.sportmonks.com/v3/motorsport/livescores
?api_token=YOUR_TOKEN
&include=results;lineups
```

For a specific fixture that is currently live, the standard [Fixture endpoints](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/endpoints) return the same live data. The Live endpoints are a convenience wrapper that filters for active sessions only.

### Polling guidance

The API does not push updates. To track a live session, poll at a sensible interval. For position and gap data, polling every 10-15 seconds is sufficient. For lap timing, which updates on each new lap, polling every 30-60 seconds is more appropriate.

Each include adds to your query complexity and payload size. During a live session, keep your live requests lean: fetch position, interval, and gap data as a baseline, then use separate lower-frequency requests for lap and pitstop data.

See [Query complexity](https://docs.sportmonks.com/v3/motorsport-api/welcome/query-complexity) for per-include complexity scores.

### Related

* [Entities - Live](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/entities)
* [Results and Live Data Type Reference](https://docs.sportmonks.com/v3/motorsport-api/welcome/results-and-live-data-type-reference)
* [Enrich your response](https://docs.sportmonks.com/v3/motorsport-api/tutorials-and-guides/tutorials/enrich-your-response)


---

# 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/motorsport-api/tutorials-and-guides/tutorials/live-data.md?ask=<question>&goal=<endgoal>
```

`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.