> 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/filter-and-select-fields.md).

# Filter and select fields

Filtering and field selection let you control exactly what the API returns. Used well, they reduce payload size, cut response time, and make your integration easier to maintain.

### In this section

* **Filtering** - How to use static and dynamic filters to narrow results by entity properties.
* **Selecting fields** - How to use `&select=` to return only specific fields from the base entity or from includes.

### Why this matters

A default request to the fixtures endpoint returns every field on the fixture entity. If you only need `name` and `starting_at`, the rest of the payload is wasted bandwidth. Field selection lets you trim that down:

```http
https://api.sportmonks.com/v3/motorsport/fixtures/19408487
?api_token=YOUR_TOKEN
&select=name,starting_at
```

Filtering is separate. It restricts which records are returned rather than which fields. For example, filtering by a specific driver ID or session state. Motorsport endpoints support the same filter syntax used across all Sportmonks v3 APIs.

### Syntax reference

The table below covers the key parameters. The full reference with examples is on the [Request options](https://docs.sportmonks.com/v3/motorsport-api/welcome/request-options) page.

| Parameter               | What it does                                                        | Example                                |
| ----------------------- | ------------------------------------------------------------------- | -------------------------------------- |
| `&select=`              | Return specific fields on the base entity                           | `&select=name,starting_at`             |
| `&include=entity:field` | Return specific fields on an include                                | `&include=lineups.driver:display_name` |
| `&filters=`             | Filter records by entity property                                   | `&filters=fixtureLeagues:3468`         |
| `&order=`               | Sort results ascending or descending                                | `&order=desc`                          |
| `&per_page=`            | Set records per page (default 25, max 1000 with `filters=populate`) | `&per_page=50`                         |

### Related

* [Request options](https://docs.sportmonks.com/v3/motorsport-api/welcome/request-options)
* [Enrich your response](https://docs.sportmonks.com/v3/motorsport-api/tutorials-and-guides/tutorials/enrich-your-response)
* [Endpoints](https://docs.sportmonks.com/v3/motorsport-api/endpoints-and-entities/endpoints)


---

# 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/filter-and-select-fields.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.