Jolpica F1 Scraper - Race Results, Qualifying & Standings
Pricing
Pay per event
Jolpica F1 Scraper - Race Results, Qualifying & Standings
Extract Formula 1 race results, qualifying times, driver and constructor standings, lap times, and pit stops from the Jolpica F1 API — the maintained successor to the defunct Ergast API. Covers all seasons from 1950 to present including 2025-2026.
Pricing
Pay per event
Rating
0.0
(0)
Developer
BowTiedRaccoon
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
4 days ago
Last modified
Categories
Share
Extract Formula 1 race results, qualifying times, driver and constructor standings, lap times, and pit stops from the Jolpica F1 API — the community-maintained successor to the Ergast API (retired end-2024). All seasons 1950 through 2025-2026 are available.
Why Jolpica? Ergast was the de-facto F1 data standard for a decade. When it was retired at the end of 2024, every fantasy app, sim-racing tool, and analytics script had to migrate. Jolpica is the migration target — same schema, live updates, free and open. This actor points at Jolpica, not the dead Ergast endpoint.
What Data Does It Return?
Each record type is a flat JSON object with all relevant fields:
Race Results (race_results)
Position, driver, constructor, grid, laps, status, fastest lap time and speed, race time, and championship points — per driver per race.
Qualifying (qualifying)
Q1, Q2, and Q3 session lap times per driver per race.
Driver Standings (driver_standings)
Championship points, wins, and position per driver, per season (or per round).
Constructor Standings (constructor_standings)
Championship points, wins, and position per constructor, per season (or per round).
Lap Times (lap_times)
Per-lap position and time for every driver in a specific race (requires season + round).
Pit Stops (pit_stops)
Stop number, lap, time of day, and duration for every pit stop in a specific race (requires season + round).
Input
| Field | Type | Description |
|---|---|---|
dataType | string | Data to fetch: race_results, qualifying, driver_standings, constructor_standings, lap_times, pit_stops |
season | string | Season year (e.g. 2024, 2025) or current. Leave empty for all seasons. |
round | string | Race round number. Required for lap_times and pit_stops. |
driverId | string | Filter to one driver (e.g. max_verstappen, hamilton). |
constructorId | string | Filter to one constructor (e.g. red_bull, mercedes). |
maxItems | integer | Maximum records to return. 0 = unlimited. |
Example Inputs
Get 2024 race results (all races, all drivers):
{"dataType": "race_results","season": "2024","maxItems": 100}
Get Hamilton's full race results career:
{"dataType": "race_results","driverId": "hamilton","maxItems": 0}
Get lap times for the 2024 Bahrain Grand Prix (round 1):
{"dataType": "lap_times","season": "2024","round": "1","maxItems": 0}
Get 2025 driver championship standings:
{"dataType": "driver_standings","season": "2025","maxItems": 25}
Output Schema
All record types share common race metadata fields and include a data_type field for filtering.
Common fields: data_type, season, round, race_name, circuit_id, circuit_name, circuit_locality, circuit_country, circuit_lat, circuit_long, race_date, race_time_utc
Race results / qualifying: driver_id, driver_code, driver_name, driver_nationality, driver_dob, constructor_id, constructor_name, position, position_text, grid, laps, status, points, fastest_lap_rank, fastest_lap_time, fastest_lap_speed_kph, q1_time, q2_time, q3_time
Standings: standings_position, standings_points, standings_wins, driver/constructor fields as applicable
Lap times: driver_id, lap_number, lap_time, lap_position
Pit stops: driver_id, pit_stop_number, pit_stop_lap, pit_stop_time_of_day, pit_stop_duration
Data Source
Jolpica F1 API — free, open, no authentication required. Maintained by the F1 data community as a drop-in replacement for Ergast. Covers 1950-present with ongoing updates.
Need More Features?
Have a use case that isn't covered — sprint results, fastest lap history by circuit, tyre strategy data, or a specific filtering combination? Open an issue or get in touch. We are happy to extend the actor for your needs.