> 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/fixtures.md). # Fixtures In the Motorsport API, a fixture is a single session: a practice session, a qualifying session, a sprint race, or the main race. Multiple fixtures make up a race weekend (stage). This section covers how to retrieve fixtures, understand session types, and work with session metadata. ### In this section * **Fixtures** - How to query fixtures by ID, by season, by stage, and how to enrich them with results and lineups. ### Session types A fixture has a `name` field that indicates the session type (e.g. "Race", "Qualifying", "Practice 1"). The `metadata` include gives you additional session-level data including whether the session counts towards standings, whether it is a sprint race, and the total lap count. To retrieve a single fixture with its session metadata: ```http https://api.sportmonks.com/v3/motorsport/fixtures/FIXTURE_ID ?api_token=YOUR_TOKEN &include=metadata ``` To retrieve all fixtures for a season in one call: ```http https://api.sportmonks.com/v3/motorsport/seasons/SEASON_ID ?api_token=YOUR_TOKEN &include=fixtures ``` ### Fixture state Every fixture has a `state_id` that tells you whether the session is scheduled, live, or finished. Fetch the state as an include to get the human-readable label: ``` https://api.sportmonks.com/v3/motorsport/fixtures/FIXTURE_ID ?api_token=YOUR_TOKEN &include=state ``` See the [Entities - State](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/entities) page for the full list of state values. ### Related * [Endpoints](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/endpoints) * [Entities - Fixture](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) * [Enrich your response](https://docs.sportmonks.com/v3/motorsport-api/tutorials-and-guides/tutorials/enrich-your-response) * [Retrieving results](https://docs.sportmonks.com/v3/motorsport-api/tutorials-and-guides/tutorials/retrieving-results) * [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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.sportmonks.com/v3/motorsport-api/tutorials-and-guides/tutorials/fixtures.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.