# Standings

> **🏎️ Motorsport API Required**
>
> All Standings endpoints require an active Motorsport API subscription (€79/mo, 3,000 API calls/hr).
>
> [View pricing →](https://www.sportmonks.com/formula-one-api/)

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**

* [**GET All Driver Standings**](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/endpoints/standings/get-all-driver-standings): returns all driver standings available in the Motorsport API.
* [**GET Driver Standings by Season ID**](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/endpoints/standings/get-driver-standings-by-season-id): returns driver standings for a provided season ID.
* [**GET All Team Standings**](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/endpoints/standings/get-all-team-standings): returns all team (constructor) standings available in the Motorsport API.
* [**GET Team Standings by Season ID**](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/endpoints/standings/get-team-standings-by-season-id): returns team standings for a provided season ID.

#### **Include options**

You can enrich standings responses using `include`:

[`sport`](https://docs.sportmonks.com/v3/core-api/entities/core#sport), [`participant`](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/entities/driver), [`season`](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/entities/season), [`league`](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/entities/league), [`stage`](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/entities/stage)

{% 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 %}

**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:**

```http
GET /v3/motorsport/standings/drivers/seasons/SEASON_ID
?api_token=YOUR_TOKEN&include=participant
```

**Current constructors' championship standings:**

```http
GET /v3/motorsport/standings/teams/seasons/SEASON_ID
?api_token=YOUR_TOKEN&include=participant
```

**Standings with round context (which race they reflect):**

```http
GET /v3/motorsport/standings/drivers/seasons/SEASON_ID
?api_token=YOUR_TOKEN&include=participant;stage
```

**Lightweight standings table (position and points only):**

```http
GET /v3/motorsport/standings/drivers/seasons/SEASON_ID
?api_token=YOUR_TOKEN&select=position,points,participant_id&include=participant
```

{% hint style="info" %}
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.
{% endhint %}

#### **Related entities**

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

* [Standing](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/entities/standing)

#### **Related pages**

* [Race Results](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/endpoints/race-results) - Full season result records per driver or team
* [Drivers](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/endpoints/drivers) - Resolve driver `participant_id` to full profiles
* [Teams](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/endpoints/teams) - Resolve team `participant_id` to full profiles
* [Seasons](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/endpoints/seasons) - Look up season IDs
* [Stages](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/endpoints/stages) - Resolve `stage_id` to the race weekend the standing reflects


---

# 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/standings.md?ask=<question>
```

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.