> 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/endpoints-and-entities/endpoints/standings.md).

# Standings

Keep track of the season performances of your favourite teams. The standings endpoint is used to retrieve full league standing tables. 

{% hint style="warning" %}
The response of the standings endpoint can be returned in two formats depending on the league setup. For ‘normal’ leagues, the response format differs from Cups. 

Please check your response carefully if you have cups and 'normal' Leagues in your plan.
{% endhint %}

Use one of our 6 standings endpoints. Per endpoint, you can find the details, including base URL, parameters, includes and more. 

* [**GET All Standings**](https://docs.sportmonks.com/v3/endpoints-and-entities/endpoints/standings/get-all-standings)**:** returns all the standings available within your subscription.
* [**GET Standing by Season ID**](https://docs.sportmonks.com/v3/endpoints-and-entities/endpoints/standings/get-standings-by-season-id)**:** returns the full league standing table from your requested season ID.
* [**GET Standings by Round ID**](https://docs.sportmonks.com/v3/endpoints-and-entities/endpoints/standings/get-standings-by-round-id)**:** returns the full league standing table from your requested round ID.
* [**GET Standing Correction by Season ID**](https://docs.sportmonks.com/v3/endpoints-and-entities/endpoints/standings/get-standing-correction-by-season-id)**:** returns the standing corrections from your requested season ID.
* [**Get Live Standings by League ID**](https://docs.sportmonks.com/v3/endpoints-and-entities/endpoints/standings/get-live-standings-by-league-id)**:** returns the LIVE league standing table from your requested league ID.
* **GET Standings by Round ID:** returns the full league standing table from your requested round ID.

<figure><img src="https://3469464275-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9zsNGu3HAzSnl5DWBD3Y%2Fuploads%2FBI4PxfyGsTY6ZRZclemc%2F11-05-26-01-standings-v1.png?alt=media&amp;token=b3bcc30e-c17e-4501-addb-0ea091dd835b" alt=""><figcaption></figcaption></figure>

### Include options

[`participant`](/v3/endpoints-and-entities/entities/team-player-squad-coach-and-referee.md#team) [`season`](/v3/endpoints-and-entities/entities/league-season-schedule-stage-and-round.md#season) [`league`](/v3/endpoints-and-entities/entities/league-season-schedule-stage-and-round.md#league) [`stage`](/v3/endpoints-and-entities/entities/league-season-schedule-stage-and-round.md#stage) [`group`](/v3/endpoints-and-entities/entities/league-season-schedule-stage-and-round.md#group) [`round`](/v3/endpoints-and-entities/entities/league-season-schedule-stage-and-round.md#round) [`rule`](/v3/endpoints-and-entities/entities/standing-and-topscorer.md#standingrule)  [`details`](/v3/endpoints-and-entities/entities/standing-and-topscorer.md#standingdetail) [`form`](/v3/endpoints-and-entities/entities/standing-and-topscorer.md#standingform) [`sport`](https://docs.sportmonks.com/v3/core-api/)

### **Related Entities:**

Get an overview and explanation of all the fields returned in the API response. The related entities for the standings endpoint are:

* [Standing](/v3/endpoints-and-entities/entities/standing-and-topscorer.md#standing)


---

# 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/endpoints-and-entities/endpoints/standings.md?ask=<question>&goal=<user_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.