Ctrlk
CoreContact
For the complete documentation index, see llms.txt. This page is also available as Markdown.

🔢Standings

🏎️ Motorsport API Required

All Standings endpoints require an active Motorsport API subscription (€79/mo, 3,000 API calls/hr).

View pricing →

Standings represent the current championship rankings of drivers and teams within a season. Each standing record contains a participant's position and points total as of the most recently completed race weekend.

Use the Standings endpoints to build championship tables, track points gaps between drivers or constructors, or power season summary dashboards.

Available endpoints

Include options

You can enrich standings responses using include:

sport, participant, season, league, stage

Want to keep responses lighter and faster? Use select to request only the fields you need. See: Request options

Using participant

The participant include resolves participant_id to the full entity profile. For driver standings, this returns the driver's name, nationality, date of birth, and image. For team standings, it returns the constructor name, country, and logo. The same include name works for both - the resolved entity type depends on which standings endpoint you call.

Using stage

The stage_id field on each standing record indicates the most recent race weekend after which the standing was updated. Adding ?include=stage gives you the name and date of that stage - useful for displaying "Standings after round X" context in your UI.

Include depth: Standings endpoints support a maximum of 2 nested includes.

Working with standings fields

  • participant_id - the unique ID of the driver or team. For driver standings, this is the same participant_id used across laps, pitstops, stints, and race results endpoints. Use it to link standings data with session-level performance data.

  • position - the current championship position. Sorted ascending (1 = championship leader).

  • points - total points accumulated in the season to date.

  • stage_id - the ID of the most recently completed race weekend that this standing reflects. Resolve with ?include=stage to display which round the standing is current as of.

  • result - not used in the Motorsport API. In other Sportmonks v3 APIs this field shows position movement (up/down). It is always null here.

  • group_id, round_id, standing_rule_id - not used in the Motorsport API. These fields are inherited from the shared v3 response structure and can be safely ignored.

Driver standings vs team standings

The Motorsport API provides separate standings for drivers (the World Drivers' Championship) and teams (the World Constructors' Championship). They share the same response shape - only the participant_id resolves to a different entity type.

Driver standings
Team standings

participant_id resolves to

Driver profile

Team/constructor profile

Points source

Individual race finishes + sprint points

Combined points of both drivers

Use case

Drivers' championship table

Constructors' championship table

Common requests

Current drivers' championship standings:

Current constructors' championship standings:

Standings with round context (which race they reflect):

Lightweight standings table (position and points only):

Both "all standings" endpoints return standings across every available season. For a specific season's current standings, always use the by-season-ID endpoints to avoid fetching unnecessary historical data.

Related entities

Get an overview and explanation of all the fields returned in the API response:

Related pages

  • Race Results - Full season result records per driver or team

  • Drivers - Resolve driver participant_id to full profiles

  • Teams - Resolve team participant_id to full profiles

  • Seasons - Look up season IDs

  • Stages - Resolve stage_id to the race weekend the standing reflects

PreviousGET Race Results by Season and TeamNextGET All Driver Standings

Last updated

Was this helpful?