# Live > **🏎️ Motorsport API required** > > All Live endpoints require an active Motorsport API subscription (€79/mo, 3,000 API calls/hr). > > [View pricing →](https://www.sportmonks.com/formula-one-api/) You can obtain all the fixtures that are currently live, starting shortly, or recently ended via our live endpoints. The live endpoint returns the same fixture shape as the [Fixtures endpoints](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/endpoints/fixtures), but filtered to only sessions that are active right now, about to start, or have just finished. It is the starting point for any real-time race tracker, live timing display, or session status widget. Responses of the live endpoint are highly customisable because many includes are available to extend the response. You can find the full list of available includes below. {% hint style="info" %} To retrieve results for a fixture, you can use the `results` include. Alternatively, you can use the `lineups.details` nested include to retrieve additional lineup information and more result types. The types for these results are described in [results-and-live-data-type-reference](https://docs.sportmonks.com/v3/motorsport-api/welcome/results-and-live-data-type-reference). You can also use the `metadata` include to enrich the response with detailed information about the fixture, like the current and total lap count, race distance and fastest lap. The type reference for these details are described in [metadata-and-per-season-data-type-reference](https://docs.sportmonks.com/v3/motorsport-api/welcome/metadata-and-per-season-data-type-reference). {% endhint %} {% hint style="info" %} The endpoint to retrieve livescores is: * [**GET All Livescores**](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/endpoints/live/get-all-livescores): returns the fixtures that are currently live, starting shortly, or recently ended. {% endhint %} #### Include options [`sport`](https://docs.sportmonks.com/v3/core-api/entities/core#sport) [`league`](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/entities/league) [`season`](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/entities/season) [`stage`](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/entities/stage) [`state`](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/entities/state) [`venue`](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/entities/venue) [`participants`](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/entities/stint) [`results`](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/entities/fixture) [`metadata`](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/entities/fixture) [`lineups`](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/entities/driver) [`latestLaps`](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/entities/fixture) [`pitstops`](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/entities/pitstop) [`latestPitstops`](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/entities/pitstop) [`stints`](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/entities/stint) [`latestStints`](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/entities/stint) [`lineups.details`](lineups.detailshttps://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/entities/driver) {% hint style="info" %} Want to keep responses lighter and faster? Use `select` to request only the fields you need. See: [Request options](https://docs.sportmonks.com/v3/motorsport-api/welcome/request-options) {% endhint %} #### **Recommended includes for live use cases** The right combination of includes depends on what you are building: * **Session status widget** - `state;metadata` - tells you the session name, current state, lap count, and race distance with minimal payload. * **Live leaderboard** - `lineups.details;metadata` - gives you the full running order with positions, gaps, intervals, tyre data, and the `IN_PIT` indicator (available from 2025). * **Live timing with lap data** - `lineups.details;latestLaps;metadata` - adds the most recent lap per driver on top of the leaderboard. * **Pit window tracker** - `latestPitstops;latestStints` - shows the most recent pitstop and current stint per driver. For deeper lap telemetry during a session, use the [Laps endpoints](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/endpoints/laps) directly with the fixture ID returned here. #### **The `length` field on live fixtures** Unlike the standard fixtures endpoints where `length` is unused, the livescores endpoint populates this field during active sessions: * For **practice and qualifying sessions**: the planned session length in minutes. * For **race sessions**: the total scheduled lap count. This is useful for building progress indicators - combine `length` with `CURRENT_LAP` from the `metadata` include to show race completion percentage. #### **Polling guidance** The livescores endpoint returns sessions that are active, starting soon, or recently ended. When no session is active it returns an empty `data` array - this is expected behaviour, not an error. For live race applications, a polling interval of **10-15 seconds** is appropriate. The underlying data feed does not update faster than this, and polling more aggressively will consume your 3,000 calls/hr allowance without returning fresher data. During a 2-hour race at 10-second intervals, a single livescores call uses approximately 720 of your hourly allowance. If you need lap-by-lap updates rather than full session state, poll the [Latest Laps endpoint](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/endpoints/laps) separately - it returns only the most recent lap per driver and is a lighter call than fetching the full session with all includes. #### Related entities Get an overview and explanation of all the fields returned in the API response. The related entities for the live endpoints are: * [Live](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/entities/live) #### **Related pages** * [Fixtures](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/endpoints/fixtures) - Full fixture data including historical sessions * [Laps](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/endpoints/laps) - Lap-by-lap timing for a session * [Pitstops](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/endpoints/pitstops) - Pit lane visits for a session * [Stints](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/endpoints/stints) - Tyre stints for a session * [States](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/endpoints/states) - All possible session states * [Results & Live Data Type Reference](https://docs.sportmonks.com/v3/motorsport-api/welcome/results-and-live-data-type-reference) * [Metadata & Per-Season Data Type Reference](https://docs.sportmonks.com/v3/motorsport-api/welcome/metadata-and-per-season-data-type-reference) --- # Agent Instructions: 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: ``` GET https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/endpoints/live.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.