Jolpica F1 Public API Scraper

Jolpica F1 Public API Scraper

Scrape Formula 1 data from the Jolpica API for any season, from drivers and circuits to race results and championship standings. Every record returns in a clean, flat structure ready for analysis. Export to CSV, JSON, Excel, or XML.

The Jolpica API provides a free, Ergast-compatible source for historical and current Formula 1 data, but querying it manually for bulk analysis is slow and repetitive. This Actor reads the public endpoints directly, letting you pull drivers, constructors, race results, qualifying, sprint outcomes, and championship standings for any season. You get a complete dataset without writing a single line of code.

Who uses it	What they scrape Jolpica F1 for
F1 data analysts	Pull complete season results to model driver and constructor performance.
Sports journalists	Gather historical race data and standings for season previews and race reports.
Fantasy league developers	Feed driver standings and race results into a fantasy F1 scoring engine.
Motorsport researchers	Compile circuit and qualifying data across decades for a long-term study.

What it does

This Actor collects Formula 1 data from the Jolpica API for a specified season and resource type, and returns each record as a flat row.

• 🏎️ Full season coverage: Fetch data for any F1 season from 1950 to the current year.
• 📊 Nine resource types: Drivers, constructors, circuits, races, results, qualifying, sprint, driver standings, and constructor standings.
• 📦 Flat row output: Every record is returned as a single flat object, with no nested pagination to unpack.
• 🔁 Ergast-compatible schema: The data structure matches the widely-used Ergast format, making migration simple.

Results export to CSV, JSON, Excel, or XML, or straight from the API.

What you can do with Jolpica F1 data

🏆 Build a season review dashboard.

A data analyst pulls the full race results and driver standings for the 2024 season to populate a Tableau dashboard comparing teammate battles.

📝 Research a driver's career arc.

A journalist scrapes results across multiple seasons for a specific driver to chart their progression from debut to final race.

🏁 Power a fantasy F1 app.

A developer schedules a weekly run to collect the latest driver standings and race results, feeding the data into a custom fantasy league scoring system.

📈 Analyze constructor dominance.

A researcher collects constructor standings for every season since 1958 to quantify the most dominant eras in F1 history.

Why choose this scraper

	What you get
No API coding	Get F1 data without constructing URLs or handling pagination yourself.
Historical depth	Access data for every season back to the first Formula 1 World Championship in 1950.
Structured output	Receive a clean dataset with a fixed schema, ready for spreadsheets or databases.

How it compares

This Actor covers the full range of Jolpica API resources, while the alternative focuses specifically on a pre-filtered driver standings view.

Feature	ParseForge	Jolpica F1 Results Scraper - Standings and Drivers
Driver standings	Yes	Yes
Constructor standings	Yes	Not listed
Race results	Yes	Not listed
Qualifying results	Yes	Not listed
Sprint results	Yes	Not listed
Circuits data	Yes	Not listed

Configure the run

Drive the Actor by selecting a season and a resource type, and set a maximum record limit to control the size of your dataset. The Input tab lists every parameter.

A first run with the defaults:

{
  "season": "2024",
  "maxItems": 10
}

A larger pull:

{
  "season": "2024",
  "maxItems": 200
}

Pricing

Pay-per-result: $0.0085 per result collected. You pay only for the results written to your dataset.

Results collected	Approximate cost
100 results	$0.85
1,000 results	$8.50
10,000 results	$85.00

New Apify accounts start with $5 in free credit.

Free users

Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.

Run it

1. Create a free Apify account with $5 in credit.
2. Open the Jolpica F1 Public API Scraper.
3. Set your inputs and any filters, then click Start.
4. Export the results as CSV, Excel, JSON, or XML from the Dataset tab.

Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.

Use with AI agents (MCP)

Give an AI agent live access to Jolpica F1 through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:

claude mcp add --transport http apify "https://mcp.apify.com?tools=parseforge/jolpica-f1-scraper"

Then prompt it in plain language to run the scraper and read back the results.

Troubleshooting

Why am I getting an empty dataset?

Check that the season you entered is valid. For example, the first Formula 1 season is 1950. Also, some resources like 'sprint' only have data from 2021 onwards.

The run failed with an error. What should I check?

Verify your input values. The season must be a four-digit year or the word 'current', and the resource must be one of the nine options listed in the input schema.

I only got 10 records but I need the full dataset.

The 'Maximum records' input defaults to 10. Increase this value up to 1,000,000 to collect more data in a single run.

The data looks different from what I expected.

The output schema follows the Jolpica API's Ergast-compatible format. Refer to the Jolpica API documentation for detailed field descriptions for each resource type.

FAQ

Question	Answer
What seasons can I scrape with this Actor?	You can scrape any Formula 1 season from 1950 up to the current season. Set the season input to a specific year or use 'current' for the ongoing championship.
What data resources are available?	The Actor supports nine resource types: drivers, constructors, circuits, races, results, qualifying, sprint, driver standings, and constructor standings. You select one per run.
Does this Actor require an API key?	No. The Jolpica API is a free, public service and this Actor reads from it directly. You do not need to register or provide any credentials.
What format is the output data in?	The Actor returns data in a flat JSON structure, which you can export from Apify to CSV, JSON, Excel, or XML formats.
Is the data schema compatible with the old Ergast API?	Yes. The Jolpica API maintains an Ergast-compatible schema, so the fields and structure will be familiar if you are migrating from an Ergast-based workflow.
Can I get both qualifying and race results in one run?	No. Each run of the Actor fetches one resource type. To get qualifying and race results, run the Actor twice, once for 'qualifying' and once for 'results'.
How many records can I collect in a single run?	You can set the maximum records limit up to 1,000,000 per run. The default is 10, which is useful for testing your query before a full extraction.
Does this include sprint race data?	Yes. The 'sprint' resource returns sprint race results for seasons and events where a sprint took place.

Related actors

Browse the full ParseForge collection for more scrapers.

🆘 Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.

⚠️ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by Jolpica. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.