🛣️Venues
🏎️ Motorsport API Required
All Venues endpoints require an active Motorsport API subscription (€79/mo, 3,000 API calls/hr).
A venue represents a physical racing circuit where motorsport fixtures take place - for example, Circuit de Monaco or Silverstone Circuit. A venue is the track itself and is distinct from the Stage (race weekend) that takes place there. The same circuit can host race weekends across multiple seasons.
Use the Venues endpoints to retrieve circuit profiles, display track layouts and location data, or list all circuits on a season calendar.
Use the metadata include to enrich venue responses with detailed track information such as track length, direction, surface type, DRS zones, and number of turns. The type reference for these details is described in the Metadata & Per-Season Data Type Reference.
Available endpoints
GET All Venues: returns all venues (racing circuits) available in the Motorsport API.
GET Venue by ID: returns a single venue by its ID.
GET Venues by Search: returns venues matching a provided search query.
GET Venues by Season ID: returns all venues on the calendar for a provided season ID.
Include options
You can enrich venue responses using include:
country, city, fixtures, metadata
Want to keep responses lighter and faster? Use select to request only the fields you need. See: Request options
Using metadata
metadataThe metadata include adds track-specific data not present in the base response, including track length, direction (clockwise or anti-clockwise), circuit type (race circuit or street circuit), Grand Prix name, DRS zone count, and number of turns. Resolve the exact type values via the Metadata & Per-Season Data Type Reference.
Using city
cityThe base response includes a city_name field, but this is sparsely populated and may be null even when city_id is present. Use ?include=city for reliable city data.
Include depth: Venues endpoints support a maximum of 2 nested includes.
Working with venue fields
image_path- returns a track layout diagram, not a photograph of the venue. This is the circuit map image suitable for displaying alongside race weekend previews and venue profiles.latitude/longitude- geographic coordinates of the circuit as strings. Parse to float before passing to a mapping library.capacity- spectator/grandstand capacity. Useful for venue profile pages.surface- the track surface material. For F1 circuits this is always"asphalt".city_name- sparsely populated. Use?include=cityinstead for reliable city data.address/zipcode- sparsely populated. Handlenullvalues in your application.national_team- not used in the Motorsport API. Inherited from the shared v3 response structure and can be safely ignored.
Venues vs Stages
It is worth being clear on the distinction between a venue and a stage when building location-based features:
Represents
The physical circuit
The race weekend event
Changes per season?
No - circuits are permanent
Yes - new stages each season
Has fixtures?
Via ?include=fixtures
Via ?include=fixtures
Best for
Circuit profiles, track maps, location data
Race weekend schedules, event metadata
A stage's venue is accessible via ?include=venue on the Stages or Fixtures endpoints.
Common requests
Full circuit profile with track data:
Search for a circuit by name:
All circuits on this season's calendar:
Lightweight circuit list (name, layout image, and coordinates):
Related entities
Get an overview and explanation of all the fields returned in the API response:
Related pages
Last updated
Was this helpful?