Formula 1 Race History: Driver & Team Results

Formula 1 Race History returns Grand Prix results for the drivers or constructors you name, one row per race entry, newest first. Compare grid position, finish, points, laps and status using the Jolpica API, the community successor to Ergast.

What does Formula 1 Race History do?

Formula 1 Race History resolves each query against Jolpica and returns driver or constructor race results, including grid, finishing position, points, laps and status.

• Type names in plain text (Max Verstappen, Lando Norris, Charles Leclerc, HAM); no IDs needed.
• Get recent form in one call: the newest races first, across seasons when needed.
• Ask for many names in one run and get one combined table.
• Export to JSON, CSV or Excel, or connect the Actor to an AI workflow through Apify integrations or an MCP client.

What data can you extract?

Field	Meaning
query	Query
sport	Sport identifier
entityType	Driver or constructor
entityId	Jolpica driver or constructor ID
entityName	Driver or team
date	Date
season	Season
round	Round
race	Race
circuit	Circuit
country	Country
driver	Driver
team	Team
grid	Grid
position	Position
positionText	positionText
points	Points
laps	Laps
status	Status
raceTime	raceTime
fastestLapRank	fastestLapRank
url	Race URL
scrapedAt	When this run retrieved the row
runId	Your optional workflow identifier

Every row also includes query (the name you entered), entityId, scrapedAt and your optional runId.

How to use Formula 1 Race History

1. Open Formula 1 Race History on Apify and sign in or create a free account.
2. Add one or more names in Drivers.
3. Set Maximum races per name (10 is a good default for recent form).
4. Click Start and download the results, or call the Actor from the API or an AI agent.

Input examples

{
  "drivers": [
    "Max Verstappen",
    "Lando Norris"
  ],
  "maxItems": 10
}

{
  "teams": [
    "Ferrari"
  ],
  "season": "2025",
  "maxItems": 48
}

Output example

{
  "query": "Ferrari",
  "sport": "f1",
  "entityType": "team",
  "entityId": "ferrari",
  "entityName": "Ferrari",
  "date": "2026-09-26T11:00:00Z",
  "season": "2026",
  "round": 15,
  "race": "Azerbaijan Grand Prix",
  "circuit": "Baku City Circuit",
  "country": "Azerbaijan",
  "driver": "Charles Leclerc",
  "team": "Ferrari",
  "grid": 2,
  "position": 4,
  "positionText": "4",
  "points": 12,
  "laps": 51,
  "status": "Finished",
  "raceTime": "+14.136",
  "fastestLapRank": 5,
  "url": "https://en.wikipedia.org/wiki/2026_Azerbaijan_Grand_Prix",
  "scrapedAt": "2026-10-09T12:00:00.000Z",
  "runId": null
}

Who uses Formula 1 Race History?

• Betting and prediction-market research: check a driver's last 10 grid slots and finishes, or a team's reliability, before race or podium markets close.
• Fantasy F1: compare points and qualifying-to-finish gains before choosing a team.
• Analysts and media: pull a season or a career run race by race.

Schedule recurring runs if you track the same drivers or constructors throughout a season.

Why use Formula 1 Race History?

Feature	Typical sports scrapers	Formula 1 Race History
Input	Site-specific slugs or IDs	Plain names, URLs or IDs
Same-name athletes	Often picks the wrong person	Filtered to Formula 1 only
Output shape	Raw page tables	One clean row per race, newest first
Several names per run	Usually one	Up to 50
AI agent use	Not described	Short, predictable rows for MCP tools

How much will Formula 1 Race History cost?

Formula 1 Race History uses pay-per-event pricing. At current Free-tier rates, the default 4 GB run-start charge is about $0.004, plus $0.001 per returned race; 10 rows therefore cost about $0.014. Your plan tier and Apify's current rates may change the total. Check the Pricing tab and request only the rows you need.

Run it through the Apify API

curl -X POST "https://api.apify.com/v2/acts/trovevault~f1-race-history/run-sync-get-dataset-items" \
  -H "Authorization: Bearer <YOUR_APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"drivers": ["Max Verstappen", "Lando Norris"], "maxItems": 10}'

Limitations

• Grand Prix results only; sprint races and qualifying sessions are not included. New results usually appear within a day of the race.
• Data comes from the open Jolpica F1 database (the community successor of the Ergast API), so coverage and update timing follow that source and may lag the end of an event.
• Only completed races are returned; scheduled ones are skipped.

Troubleshooting

• No rows returned: check the spelling or use a Jolpica driver or constructor identifier. Upcoming races are not included.
• Fewer rows than requested: the source may have fewer completed results for that name, season or competition.
• Some names failed: successful names are still returned. Check the RUN_SUMMARY key-value record for the per-name errors and retry only those names.
• Rows are missing from your existing dataset: confirm the datasetId belongs to a dataset you can write to. The run's default dataset is still populated separately.

FAQ

Can I use Formula 1 Race History with AI agents?

Yes. You can call the Actor from an AI agent using Apify's API or an MCP client configured to access Apify Actors.

Can I use Formula 1 Race History with the Apify API?

Yes. Use the run-sync-get-dataset-items endpoint shown above, or the Apify JavaScript and Python clients.

How many races can I get per run?

Up to 200 races per name and up to 50 names per run.

Can I get historical races?

Yes. Set Season to read a past season, or raise Maximum races per name and the Actor goes back across seasons.

Does it work with integrations?

Yes. Send results to Google Sheets, Make, Zapier, n8n, Slack or webhooks with Apify integrations, or append them to an existing dataset with Dataset ID.

Is it legal to collect this data?

Formula 1 Race History collects factual sports results and statistics that are publicly available. You are responsible for how you use the data, including any terms of the sources and betting rules in your country.

Your feedback

Found a missing race or a wrong name match? Open an issue on the Issues tab and include the name you entered.