> 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/standings.md). # Standings This section covers how to retrieve championship standings for both drivers and constructors, and how to filter standings by season. ### In this section * **Championship standings** - How to retrieve the driver standings and constructor standings, enrich them with driver and team data, and filter by season. ### Drivers standings vs constructor standings The API provides two standing types: driver standings (individual championship positions) and constructor standings (team championship positions). Both are available via the Standings endpoints. To retrieve the driver standings for a specific season: ```http https://api.sportmonks.com/v3/motorsport/standings/drivers/seasons/SEASON_ID ?api_token=YOUR_TOKEN ``` To enrich with driver details: ```http https://api.sportmonks.com/v3/motorsport/standings/drivers/seasons/SEASON_ID ?api_token=YOUR_TOKEN &include=participant ``` To retrieve constructor standings for a season: ```http https://api.sportmonks.com/v3/motorsport/standings/teams/seasons/SEASON_ID ?api_token=YOUR_TOKEN ``` ### Points mid-session During a live race, the `POINTS` type in `lineups.details` returns the points a driver would receive if they finished in their current position. This is distinct from the season standings, which only update after a session is confirmed as finished. See [Results and Live Data Type Reference](https://docs.sportmonks.com/v3/motorsport-api/welcome/results-and-live-data-type-reference) for the POINTS type ID and availability. ### Related * [Endpoints](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/endpoints) * [Entities - Standing](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/entities) * [Schedule and calendar](https://docs.sportmonks.com/v3/motorsport-api/tutorials-and-guides/tutorials/schedule-and-calendar) * [Results and Live Data Type Reference](https://docs.sportmonks.com/v3/motorsport-api/welcome/results-and-live-data-type-reference) --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.sportmonks.com/v3/motorsport-api/tutorials-and-guides/tutorials/standings.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.