> 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/enrich-your-response.md).

# Enrich your response

By default, every endpoint returns only the fields of the base entity. Includes let you attach related data in the same request, so you can get everything you need in a single call instead of chaining multiple requests.

### In this section

* **Includes** - How the includes system works: syntax, nesting, field selection, and performance guidance.
* **Lineups** - Driver and team assignments for a session, including driver number and grid position.
* **Results** - Position, time, gap, tyre, and status data per driver. Covers both the `results` include and the full `lineups.details` alternative. See [Retrieving results](https://docs.sportmonks.com/v3/motorsport-api/tutorials-and-guides/tutorials/retrieving-results).
* **Laps** - Lap-by-lap timing data including sector times, lap duration, and lap number.
* **Pitstops** - Pit entry timestamps and stop durations per driver per session.
* **Stints** - Tyre stint data including stint number and start/end lap.

### How includes work

Add `&include=` to any request and name the include you want. Separate multiple includes with a semicolon:

```http
https://api.sportmonks.com/v3/motorsport/fixtures/19408487
?api_token=YOUR_TOKEN
&include=lineups;results
```

Use dot notation to nest includes:

```http
https://api.sportmonks.com/v3/motorsport/fixtures/19408487
?api_token=YOUR_TOKEN
&include=lineups.driver
```

Use a colon to select only specific fields from an include, which reduces payload size:

```http
https://api.sportmonks.com/v3/motorsport/fixtures/19408487
?api_token=YOUR_TOKEN
&include=lineups.driver:display_name,image_path
```

See [Request options](https://docs.sportmonks.com/v3/motorsport-api/welcome/request-options) for the full syntax reference including field selection on the base entity (`&select=`).

### Performance guidance

Each include increases payload size and counts against your query complexity budget. Only request includes you actually need for the current view. For reference data that changes rarely - driver names, team names, country details - fetch once at startup and cache locally rather than including on every request.

See [Query complexity](https://docs.sportmonks.com/v3/motorsport-api/welcome/query-complexity) for how complexity is calculated and what the limits are.

### Type reference

Each result type and lineup detail type has a numeric ID. When working with `lineups.details`, the type is not returned by default. Use `lineups.details.type` to include it in the response, or fetch all types once and cache them locally.

The full list of driver-level type IDs is in the [Results and Live Data Type Reference](https://docs.sportmonks.com/v3/motorsport-api/welcome/results-and-live-data-type-reference). Session-level types (lap counter, fastest lap) are in the [Metadata and Per-Season Data Type Reference](https://claude.ai/welcome/metadata-and-per-season-data-type-reference).

### Related

* [Request options](https://docs.sportmonks.com/v3/motorsport-api/welcome/request-options)
* [Query complexity](https://docs.sportmonks.com/v3/motorsport-api/welcome/query-complexity)
* [Results and Live Data Type Reference](https://docs.sportmonks.com/v3/motorsport-api/welcome/results-and-live-data-type-reference)
* [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/enrich-your-response.md?ask=<question>&goal=<endgoal>
```

`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.