If you identify any API bugs or errors in the data please record them here.
Bug Reports
Comments
820 responses to “Bug Reports”
-
I think the time for the Qatar Grand Prix is incorrect.
https://ergast.com/api/f1/2023/17.json
It should be “17:00:00Z” according to https://www.formula1.com/en/racing/2023/Qatar.html
Thanks. Your API is great!
-
Hello
The Qatar 2023 sprint race results are incorrect. LEC got a 5 second penalty, so Albon moved up to 7th and Fernando moved up to 8th. Thanks! -
Thanks Brandon – now corrected
Cheers,
Chris -
Hi Chris,
There are a couple of minor errors in the Constructors standings:
Ferrari has 298 points, but API returns 300.
Aston Martin has 230 points, but API returns 229.
Williams has 23 points, but API returns 22http://ergast.com/api/f1/2023/constructorStandings
Source:
https://www.fia.com/sites/default/files/decision-document/2023%20Qatar%20Grand%20Prix%20-%20Championship%20Points.pdfThanks!
-
Hello! For the US GP session times, the current sprint shootout start time from the API is 30 minutes later than the official time. The API is returning 18:00:00Z but according to the official F1 calendar, the start time is 17:30:00Z.
I know the API still returns sprint shootout sessions as “SecondPractice” so I’m not sure if that has anything to do with the 30 minute difference but all other sessions times for this race are correct.
-
Hi fellow F1 fans and developers.
I have an issue that has been going on with this api for about 6 months. Every time I do a request from Vue, I get an CORS error. Pretty strange for an open api right? How can we fix this issue?
-
Hey Chris, would you be interested in some help developing this?
I already have a copy of this database modelled in Django if that is a technology of interest.
Feel free to contact on email listed -
Hi Chris,
Thanks for the data, I appreciate it, it saved me a ton of time. I found some conflicting results however. For example there are 3 records for race 800 and driver 612. I found 84 more cases like this with double records holding different data. Please let me know if you want me to send you the list with doubles.
-
Hey Chris,
in the results from the US GP (October 22), the grid positions are wrong. http://ergast.com/api/f1/2023/18/results
Louis Hamilton wasn’t on pole, it was Charles Leclerc.
-
For the US GP (October 22), Charles Leclerc’s car number is incorrectly listed as 22 (should be 16).
http://ergast.com/api/f1/2023/18/results -
I think the current constructor standings is incorrect
http://ergast.com/api/f1/current/constructorStandings
Ferrari has 322 points, but API returns 324.Source:
https://www.formula1.com/en/results.html/2023/team.html -
Hi Mika,
Have you tried a JSONL request?
Cheers,
Chris -
Hi Dan,
Unfortunately the session times have been tweaked frequently this year. It’s hard to keep up with the changes.
Cheers,
Chris -
Brandon, Josh,
Thanks for the warning – now corrected.
Cheers,
Chris -
Hi Brandon,
Thanks for the warning – the the race time and results have been corrected.
Cheers,
Chris -
Hi Achtchaern,
Thanks for the warning – now corrected.
Cheers,
Chris -
Hi Michael,
Thanks for the warning – now corrected.
Cheers,
Chris -
Hi George,
Thanks for the warning – now corrected.
Cheers,
Chris -
Hi,
First I want to thank you for the great API! I noticed Leclerc laptimes are missing for the last race. See for instance:
https://ergast.com/api/f1/2023/18/laps/24.json
Thanks for the great work!
-
Leclerc is missing from the lap-by-lap database within the most recent United States Grand Prix, round 18 of season 2023.
-
When pulling data for Liam Lawson using the driverID “lawson” his permanentNumber is coming up as 15 and according to the Formula 1 site it looks like it should be 40. It also shows up as 40 for any of the races he has taken part in e.g. Japan “http://ergast.com/api/f1/current/16/results.json”
-
Hi Mark,
Thanks for the warning – now corrected.
15 is his car number from the Super Formula Championship.
Cheers,
Chris -
Hi Richard,
Thanks for the warning – now corrected (I hope)
Cheers,
Chris -
Hi Michel,
Thanks for the warning – now corrected.
Cheers,
Chris -
If you look at the lapTimes from the Mexico City you will see not all drivers are represented.
SELECT distinct driverId from lapTimes WHERE `raceId` = 1117;
Only returns 11 drivers
-
Hi Anonymous,
Apologies – I forget to update the database dump when this error was corrected on Monday.
Try the latest dump (01/11/2023 21:14)
Cheers,
Chris -
Hey,
Thanks for the great work with the API. Do you plan on continuing after 2024. It says the API will be deprecated. We will really miss this API. Would you recommend any alternatives ? -
Hey there, new here so I apologize if I’m incorrect or misunderstanding but I think thr dates for the Las Vegas GP are wrong. If they are in Z (UTC) like the times, then they should all be shifted forward 1 day. For example, the race is 11/19 not 11/18 (it’s 11/18 local Vegas time), quali is 11/18, not 11/17.
-
Las Vegas Race Time is incorrect. Should be 2023-11-19, showing as 2023-11-18
-
I think the time for the Las Vegas Grand Prix is incorrect.
https://ergast.com/api/f1/2023/21.json
The date should be “2023-11-19”, not “2023-11-18”.
https://www.formula1.com/en/racing/2023/Las_Vegas.html
It is on 2023-11-18 track time, but in UTC, it is 2023-11-19.
Thanks
-
Hi Vamsee,
Unfortunately the API and website will shutdown after the 2024 season.
Cheers,
Chris -
Chris, is it possible you can open source the api and database and/or allow someone else to take it over? It’s a great resource and you’ve done an amazing job with it, should be a shame to lose it.
-
Hi Jesse,
The API is open-source (e.g. the runtime is on GitHub). There is some interest in updating and continuing the API but I can’t promise anything.
Cheers,
Chris -
Hi,
I detected the following errors in the database:
– The new circuits Losail, Miami and Las Vegas are missing the altitude (“alt”) in table “circuits” (they should be 12, 0 and 642 meters respectively).
– The “url” for driver Óscar González (driver id 806) has a typo. It should be: “http://en.wikipedia.org/wiki/%C3%93scar_Gonz%C3%A1lez_(racing_driver)”
– In table “qualifying” some entries have q1, q2 or q3 as an empty string (“”), but they should be NULL like the vast majority of the others.
– In table “results”, the “time” for resultId 20992 is incorrect, it should be “1:37:30.334”
– In table “results”, the “time” for resultId 21088 is incorrect, it should be “1:59:06.757”
– In table “results”, the “milliseconds” for resultId 19302 is missing. It should be “10644000”
– The table constructorResults contains entries for races 784 and 790 (1956 Argentinian and German GPs), but these should be removed from this table as the Constructor Championship only started in 1958.
– The URLs in tables “circuits”, “constructors”, “drivers”, “races” and “seasons” should be updated from “http://…” to “https://…”
I hope this helps!
-
Thanks Miguel – all updated except for the last one.
Cheers,
Chris -
Hi,
I think there is an error in Fangio’s entry (http://ergast.com/api/f1/drivers/fangio?limit=1)
The forename states “Juan”. The actual forename is “Juan Manuel” as shown by the bio URL linked in the very same entry.
cheers,
-
I believe there is an error for the grid entries in http://ergast.com/api/f1/2023/13/results
specifically, Both Zhou and Alonso have the grid slot 5. According to Formula1, Zhou should be 15, not 5https://www.formula1.com/en/results.html/2023/races/1217/netherlands/starting-grid.html
-
Hi Dionisio,
This may be true but I’m reluctant to introduce spaces in the forename field because of possible side effects.
Cheers,
Chris -
Thanks Nicholas – now corrected.
Chris -
I’m trying to snag the latest data with the zip file, and I noticed the website says the 2024 season is good to go. But here’s the kicker: when I actually download the files, the 2024 season seems to be MIA.
Any chance you could lend a hand in sorting this out? Would really appreciate it!
Cheers,
Lucas
-
Hi Lucas,
I’ve updated the database dumps.
Cheers,
Chris -
Thanks for putting this together and maintaining it, and sorry to see it go.
I found several places after the 1960s where there are multiple drivers per starting grid slot. I filtered out the ones from eras where there were legitimately multiple drivers per car, and removed pit lane starts. All-in-all I found 112 cases (56 pairs) of duplicate grid slots in the CSV data dump.
Rather than listing them all here, I published a Google Sheet which shows these duplicate columns, along with a link to the Wikipedia page for that race to help troubleshoot. In some cases (e.g., 1990 Japanese GP) it looks like a driver which withdrew still shows the grid spot in which they qualified, and in others there was a grid penalty which wasn’t accounted correctly for the penalized driver.
If you contact me directly I’m happy to help out more, but I didn’t just want to paste >100 items in this comment box. So here’s the spreadsheet:
-
2023 Round 13: currently returns the following results, where the millis are incorrect and should be corrected as shown
PER +10.068: 8655093 -> 8654479
TSU +29.893: 8682344 -> 8674304
MAG +31.410: 8679515 -> 86758212023 Round 19: ALO has status “Withdrew” and the associated statusId is 54 (correct) but the positionText is “R” instead of “W”
Cheers,
Philipp -
Qatar GP Circuit is Lusail not Losail.
Thanks Awesome API -
The times are missing on the schedule 🙁
-
First I would like to say Ergast is a very good API with a lot of great information. As a F1 fan I really love it. With 2024 season around the corner I wanted to know when the 2024 scheduled will be published. When I click on this link; I only see 2023 races : https://ergast.com/api/f1/current
-
Hello ! Thanks for providing this API until now!
When do you plan to add the constructors for 2024?
And which other API do you recommend to use after you stop?
Cheers! -
I see that the API already includes the information for 2024.
Example: https://ergast.com/api/f1/2024
But the current endpoints still point to 2023: https://ergast.com/api/f1/current
Can you update the current endpoints to refer to 2024 season?
Thanks!
-
Hi Chris
Looks like the Fastest Lap data is missing in the JSON for Round 1 of 2024. If you recall, this happened a few times last season as well.
http://ergast.com/api/f1/2024/1/results.json
Thanks!
-
Hello
Thanks for the great API! Are the fastest laps data going to be available this season? If so, when are they generally updated?
Leave a Reply