Formula 1 APIformula1.com ↗
Access F1 race results, qualifying times, pit stops, driver/constructor standings, and World Champion data from formula1.com via 13 structured endpoints.
What is the Formula 1 API?
This API exposes 13 endpoints covering Formula 1 race data sourced from formula1.com, spanning seasons from 1950 to the present. You can retrieve full race result detail including all finishing positions and gap times via get_race_result_detail, pull qualifying Q1/Q2/Q3 lap times per driver, fetch pit stop summaries with per-stop durations, and query both Drivers' and Constructors' Championship standings for any season.
curl -X GET 'https://api.parse.bot/scraper/9bfc909e-ec35-447c-aee1-476971bf8f19/get_meetings_list?year=2024' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace formula1-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""
Formula 1 API - Usage Example
Get your API key from: https://parse.bot/settings
"""
from parse_apis.formula_1_api import F1, SessionNumber
f1 = F1()
# Get 2024 season data
season = f1.season("2024")
# List all meetings in the season
for meeting in season.meetings():
print(meeting.name, meeting.country_code)
# Get driver standings
standings = season.driver_standings()
for driver in standings.drivers:
print(driver.position_number, driver.driver_first_name, driver.driver_last_name, driver.championship_points)
# Get the world champion
champion = season.champion()
print(champion.driver_first_name, champion.driver_last_name, champion.team_name)
# Get team standings
team_standings = season.team_standings()
for team in team_standings.constructors:
print(team.position_number, team.team_name, team.championship_points)
# Access a specific meeting's data
bahrain = f1.meeting("1229")
practice = bahrain.practice_result(year="2024", session_number=SessionNumber.FP1)
print(practice.year, practice.season_state)
# List available sessions for a meeting
for session_ds in bahrain.sessions(year="2024"):
print(session_ds.text, session_ds.is_available)
Get list of Grand Prix meetings for a season. Returns an array of meeting objects with location names, numeric IDs, and country information. Use the meeting ID (value field) to query session-specific endpoints.
| Param | Type | Description |
|---|---|---|
| yearrequired | string | Season year (e.g. 2024, 2025) |
{
"type": "object",
"fields": {
"data": "object containing items array of meeting objects with value (meeting ID), text (location name), meetingCountryCode, meetingIsoCountryName"
},
"sample": {
"data": {
"items": [
{
"text": "Bahrain",
"value": 1229,
"isDefault": false,
"meetingCountryCode": "BRN",
"meetingIsoCountryName": "Bahrain"
}
]
},
"status": "success"
}
}About the Formula 1 API
Session and Meeting Data
All per-event endpoints require a meeting_id, which you obtain from get_meetings_list by passing a year parameter. That endpoint returns an array of meeting objects with a value field (the meeting ID), a text field for the location name, and meetingIsoCountryName for the country. Before fetching any session data, you can call get_session_datasets with a year and meeting_id to discover which result types — race, qualifying, practice, fastest laps, pit stops, starting grid — are actually available for that event, since not every meeting has all sessions populated.
Race Weekend Results
get_race_result_detail returns a raceResultsRace object containing a full results array with each driver's finishing position, classified time, and gap to the leader. get_qualifying_result adds per-driver q1, q2, and q3 lap times. get_practice_result accepts an optional session_number (1, 2, or 3) to target a specific free practice session, returning a raceResultsPractice1/2/3 object. get_starting_grid provides positionNumber and classifiedTime per driver. get_fastest_laps returns a ranked list including lapNumber, classifiedTime, and averageSpeed. get_pit_stop_summary exposes each stop's lapNumber, pitStopNumber, and totalPitTime.
Standings and Champions
get_driver_standings and get_team_standings both accept a year and return championship points, positions, and associated team or driver details. Note that the drivers array from get_driver_standings may not be sorted by positionNumber — sort client-side if you need ordered output. get_world_champion_by_year isolates the driver at positionNumber 1 for a given season and returns upstream_error if no champion data exists yet for that year.
Season Schedule and Awards
get_race_results_by_season returns the full calendar for a year as an events array, including top-3 finishers and seasonState indicating whether the season is complete or ongoing. get_award_results retrieves Driver of the Day voting results, including votePercentage and votePosition per driver, and can be filtered to a specific meeting by appending a meeting filter to the award_path parameter.
The Formula 1 API is a managed, monitored endpoint for formula1.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when formula1.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official formula1.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a season results tracker showing race winners and podium finishers for every Grand Prix using
get_race_results_by_season. - Compare qualifying performance across a season by pulling Q1/Q2/Q3 lap times per driver from
get_qualifying_result. - Analyze pit stop strategy by extracting
totalPitTimeandlapNumberdata fromget_pit_stop_summaryacross multiple races. - Display live or historical Drivers' and Constructors' Championship tables sorted by
championshipPointsfromget_driver_standingsandget_team_standings. - Show fastest lap rankings with
averageSpeedper driver for any race usingget_fastest_laps. - Build a historical World Champions page by iterating
get_world_champion_by_yearacross multiple decades. - Surface Driver of the Day fan vote results including vote percentages per meeting using
get_award_results.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Formula 1 have an official developer API?+
What does `get_race_result_detail` return beyond finishing positions?+
get_race_result_detail returns a raceResultsRace object with a full results array covering each driver's finishing position, classified time, and gap to the race leader, along with session metadata and meeting information. It does not include telemetry or lap-by-lap breakdowns — only final classified results.Does the driver standings endpoint return results sorted by championship position?+
drivers array from get_driver_standings may be unordered by positionNumber. You should sort the array client-side on positionNumber to display a correctly ordered standings table.Does the API cover Sprint race results?+
How far back does historical season data go, and are all sessions available for older years?+
year parameter accepts seasons going back to 1950 according to the prior description, but session-level data such as qualifying times and pit stop summaries may not be populated for older seasons. You can call get_session_datasets for a given year and meeting_id to check which result types have isAvailable set to true before attempting to fetch them.