f1.com APIf1.com ↗
Access F1 driver standings, constructor standings, race results, driver profiles, schedules, and awards data via a single REST API with 7 endpoints.
curl -X GET 'https://api.parse.bot/scraper/cf31b48a-e6f4-4bee-82bc-3b1864cf9a19/get_driver_standings?year=2024' \ -H 'X-API-Key: $PARSE_API_KEY'
Returns driver championship standings for a given season year, including position, driver name, nationality, team, and points.
| Param | Type | Description |
|---|---|---|
| year | string | Season year (e.g., 2024, 2023, 2022). |
{
"type": "object",
"fields": {
"season": "string — the requested season year",
"standings": "array of driver standing objects with position, driver, nationality, team, points"
},
"sample": {
"data": {
"season": "2024",
"standings": [
{
"team": "Red Bull Racing Honda RBPT",
"driver": "Max Verstappen",
"points": "437",
"position": 1,
"nationality": "NED"
},
{
"team": "McLaren Mercedes",
"driver": "Lando Norris",
"points": "374",
"position": 2,
"nationality": "GBR"
}
]
},
"status": "success"
}
}About the f1.com API
The F1.com API exposes 7 endpoints covering Formula 1 championship data from standings to detailed race results. Use get_driver_standings to retrieve per-season driver positions, points, nationality, and team, or call get_race_result with a specific meeting_id to get lap counts, finishing times, gaps to leader, and points scored for every classified finisher.
Standings and Championship Data
Both get_driver_standings and get_constructor_standings accept an optional year parameter, making it straightforward to query historical seasons alongside the current one. Driver standing objects include position, driver, nationality, team, and points. Constructor standing objects follow the same pattern with position, team, and points. Omitting year returns the current season by default.
Race Results
Fetching race-level data is a two-step process. Call get_race_results_by_season with a year to get a list of all meetings for that season — each object contains grand_prix, meeting_id, country_code, and country_name. Pass any meeting_id to get_race_result to retrieve the full finishing order, including each driver's position, driver_tla, team, time, laps, status, gap_to_leader, and championship points earned. The session field identifies the session type (e.g., Race).
Schedule and Driver Profiles
get_schedule returns the current season calendar without any inputs: an array of meetingDates objects, each with city, meetingId, startDate, endDate, and timezone. The meetingId values align with those returned by get_race_results_by_season, so schedule and result lookups can be chained. get_driver_profile takes a driver_slug in firstname-lastname format and returns biography text, a driverProfileImage object with URL and dimensions, and an assemblyRegion object containing related articles.
Awards
get_awards accepts an optional year and returns two objects: fastest_laps, which includes the DHL Fastest Lap Award winner and per-race fastest lap data, and pit_stops, which contains fastest pit stop data broken down by race. This endpoint covers season-level award aggregates rather than session-level telemetry.
- Build a season standings tracker that updates driver and constructor points after each race using get_driver_standings and get_constructor_standings.
- Power a race history browser by iterating all meeting_ids from get_race_results_by_season and fetching detailed results via get_race_result.
- Display a team's full season finishing data by filtering get_race_result responses by the team field across every meeting_id.
- Create a driver comparison tool using biography, images, and article links from get_driver_profile for multiple driver slugs.
- Build a race weekend countdown widget from get_schedule data, using startDate, endDate, and timezone fields.
- Track fastest lap and fastest pit stop award winners across seasons using get_awards with different year values.
- Generate a season calendar cross-referenced with results by matching meetingId values from get_schedule and get_race_results_by_season.
| 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 | 250 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.