> 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/stages.md).
# Stages
The **Stages** endpoints allow you to retrieve structural phases of a season (e.g. regular season, playoffs, group stage). You can query stages at the season level or individually.
#### Available endpoints
* **GET All Stages:** get all stages available under your subscription
* **GET Stage by ID:** fetch a specific stage
* **GET Stages by Season ID:** get all stages linked to one season
* **GET Stages by Search (Name):** search for stages matching a name
### Include options
[`league`](/v3/endpoints-and-entities/entities/league-season-schedule-stage-and-round.md#league) [`season`](/v3/endpoints-and-entities/entities/league-season-schedule-stage-and-round.md#season) [`type`](https://docs.sportmonks.com/football2/v/core/endpoints/types) [`sport`](https://docs.sportmonks.com/v3/core-api/) [`rounds`](/v3/endpoints-and-entities/entities/league-season-schedule-stage-and-round.md#round) [`currentRound`](/v3/endpoints-and-entities/entities/league-season-schedule-stage-and-round.md#round) [`groups`](/v3/endpoints-and-entities/entities/league-season-schedule-stage-and-round.md#group) [`fixtures`](/v3/endpoints-and-entities/entities/fixture.md#fixture) [`aggregates`](/v3/endpoints-and-entities/entities/fixture.md#aggregate) [`topscorers`](/v3/endpoints-and-entities/entities/standing-and-topscorer.md#topscorers) [statistics](/v3/endpoints-and-entities/entities/statistic.md)
(Related entity: [Stage](/v3/endpoints-and-entities/entities/league-season-schedule-stage-and-round.md#stage))
### Why stages have standings?
Not every stage supports standings (i.e. ranking tables). Below is how you can determine which do, how to query standings per stage, and example usage.
**Understanding standings & stage relationships**
* The **standings** endpoints support filtering by **stage IDs**. You can pass `stage_ids` as a parameter [when requesting standings](https://docs.sportmonks.com/football/endpoints-and-entities/endpoints/standings).
* Only **table-based stages** (e.g. group stages, regular season) typically yield a standings table. Knockout or elimination stages (e.g. quarter-finals, semi-finals) usually do *not* produce standings, because they are not cumulative formats.
* If you query standings for a non-standings stage, you'll likely get either an empty array or the API will ignore that stage filter.
**Example: Querying standings by stage**
To get standings restricted to particular stage(s), you use something like:
{% code overflow="wrap" %}
```bash
GET /v3/football/standings/seasons/{season_id}?stage_ids={stage_id1},{stage_id2}&api_token=YOUR_TOKEN
```
{% endcode %}
For example, in a season with:
* **Stage A**: “Regular Season” (table)
* **Stage B**: “Playoffs” (knockout)
You might fetch full standings:
```bash
GET /v3/football/standings/seasons/19686?api_token=YOUR_TOKEN
```
Or drill into stage A only:
```bash
GET /v3/football/standings/seasons/19686?stage_ids=stageA_id&api_token=YOUR_TOKEN
```
If you pass `stage_ids` for a stage that doesn’t support tables (Stage B), the result may exclude it.
**Detecting standings support by stage**
* Use the `type` field on the Stage entity to infer its nature (e.g. “Group Stage”, “Regular Season”)
* In your UI logic, you can first query all stages in a season, then filter out those whose `type` is non-table or known elimination types
* Always combine that logic with a fallback: if standings for a stage come back empty, treat it as non-standings
**Edge cases & tips**
* Some seasons have multiple stages of the same type (e.g. “First Phase”, “Split Phase”); each can have its own standings.
* In group competitions (e.g. Champions League), you might combine `stage_ids` + `group_ids` to filter standings at both the stage and group level.
* For live standings, you can also use the [**Live Standings** endpoint by league ID](mailto:undefined).
---
# 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/stages.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.
