> 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/schedule-and-calendar.md).

# Schedule and calendar

This section covers how the Motorsport API models a racing season, from the championship level down to individual sessions. Understanding this hierarchy is the foundation for any race calendar, fixture list, or results archive.

### In this section

* **Leagues and seasons** - The championship structure, how to find the current season ID, and how to work with historical seasons.
* **Schedule** - How to retrieve the full race calendar for a season.
* **Stages** - The race weekend structure: practice sessions, qualifying, sprint sessions, and the race itself.

### The data hierarchy

The API is structured as a tree from championship down to session:

```
League (championship)
  └── Season (calendar year)
        └── Stage (race weekend)
              └── Fixture (individual session: FP1, qualifying, race, etc.)
```

A **League** is the championship, for example the Formula 1 World Championship. A **Season** is a calendar year. A **Stage** is a race weekend, grouping all sessions at one circuit. A **Fixture** is a single session within that weekend.

When you want all fixtures for the 2025 season, query the season and include fixtures:

```http
https://api.sportmonks.com/v3/motorsport/seasons/SEASON_ID
?api_token=YOUR_TOKEN
&include=fixtures
```

When you want all sessions for a specific race weekend, query by stage ID:

```http
https://api.sportmonks.com/v3/motorsport/stages/STAGE_ID
?api_token=YOUR_TOKEN
&include=fixtures
```

### Related

* [Entities](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/entities)
* [Endpoints](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/endpoints)
* [Fixtures](https://docs.sportmonks.com/v3/motorsport-api/tutorials-and-guides/tutorials/fixtures)
* [Metadata and Per-Season Data Type Reference](https://docs.sportmonks.com/v3/motorsport-api/welcome/metadata-and-per-season-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/schedule-and-calendar.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.