For the complete documentation index, see llms.txt. This page is also available as Markdown.

πŸ§‘β€πŸ€β€πŸ§‘Teams

🏎️ Motorsport API Required

All Teams endpoints require an active Motorsport API subscription (€79/mo, 3,000 API calls/hr).

View pricing β†’

A team represents a constructor competing in a motorsport championship - for example, Ferrari, McLaren, or Red Bull Racing. In Formula 1, teams are also referred to as constructors, and their championship points are tracked separately from drivers via the Constructors' Championship.

Use the Teams endpoints to retrieve constructor profiles, look up team IDs for use in standings and race results endpoints, filter by country, or list all teams competing in a season.

Use the seasonDetails include to enrich team responses with per-season information such as car details, team principal, and branding. The type reference for these details is described in the Metadata & Per-Season Data Type Reference.

Available endpoints

Include options

You can enrich team responses using include:

sport country drivers latest upcoming seasons seasonDetails seasonDrivers

The drivers include returns driver participation information for the current season. To include the full driver entity alongside it, use the drivers.driver nested include.

If you only need a few fields, use select to request specific fields and reduce response size. See: Request options

Include depth: Teams endpoints support a maximum of 3 nested includes.

Working with team fields

  • id - the unique team ID. This is the same value referenced as team_id in lineup objects and race results responses. Use it as the join key when combining team profiles with standings or race result data.

  • country_id - the country the team is registered in or associated with. Resolve with ?include=country.

  • short_code - a 3-letter constructor abbreviation, e.g. "FER" for Ferrari, "MCL" for McLaren. Suitable for compact leaderboard displays.

  • type - indicates the team's power unit type, e.g. "hybrid". Reflects the engine technology classification used in the current regulatory era.

  • last_played_at - the datetime of the team's most recent session. Useful for checking whether a team is currently active or has been retired from competition.

  • placeholder - true for a team slot that exists structurally but has not yet been assigned to a real constructor. Filter these out when building team listings.

  • founded - the team's founding year. Sparsely populated - handle null values in your application.

  • venue_id - not used in the Motorsport API. Unlike football clubs, constructors do not have a home venue. This field is inherited from the shared v3 response structure and will always be null.

Common requests

Look up a team by name:

Full team profile with current drivers and country:

All constructors in a season:

All constructors in a season with their current drivers:

Lightweight team list (name, short code, and logo only):

Use the search endpoint to find a team ID before calling standings or race results endpoints. The search accepts partial names - "red bull", "alpine", "haas" - and returns matching constructor records with their IDs.

Get an overview and explanation of all the fields returned in the API response:

Last updated

Was this helpful?