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:

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

• Enrich your response

• Endpoints