🔴Live
🏎️ Motorsport API required
All Live endpoints require an active Motorsport API subscription (€79/mo, 3,000 API calls/hr).
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, 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.
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.
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.
The endpoint to retrieve livescores is:
GET All Livescores: returns the fixtures that are currently live, starting shortly, or recently ended.
Include options
sport league season stage state venue participants results metadata lineups latestLaps pitstops latestPitstops stints latestStints lineups.details
Want to keep responses lighter and faster? Use select to request only the fields you need. See: Request options
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 theIN_PITindicator (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 directly with the fixture ID returned here.
The length field on live fixtures
length field on live fixturesUnlike 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 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:
Related pages
Last updated
Was this helpful?