Ergast Developer API

Bug Reports

If you identify any API bugs or errors in the data please record them here.

Comments

852 responses to “Bug Reports”

  1. Michel Avatar
    Michel

    Thanks again for providing the data. It seems some stop and lap values for pitstops are turned around.

    For example https://ergast.com/api/f1/2024/1/pitstops/12
    this should be stop: 1 and lap: 12.

    Is going wrong for the pitstops below:
    – https://ergast.com/api/f1/2024/1/pitstops/12
    – https://ergast.com/api/f1/2024/1/pitstops/13
    – https://ergast.com/api/f1/2024/1/pitstops/33
    – https://ergast.com/api/f1/2024/1/pitstops/34

  2. Admin Avatar
    Admin

    Thanks Michel – now corrected.
    Cheers,
    Chris

  3. Dan Avatar
    Dan

    Hello! Thanks for all the great work.

    I noticed that the race schedule results, such as http://ergast.com/api/f1/current/next are not currently including the times of all the race sessions like they did in previous years.

    Is there any plan to add in session times for this season?

    Thanks!

  4. Luigi Avatar
    Luigi

    Hello! Thanks for all the great work Chris.

    The race table on database image not including any times and date for Fp1,Fp2,Fp3 Sprint and pole

    Is there any plan to add them in for this season?

    Thanks!

  5. Dan Avatar
    Dan

    The Chinese GP has a sprint race according to https://www.formula1.com/en/racing/2024/China.html

    Currently, the API is showing China as a regular race with no sprint. Could you please update this so that the correct session names appear on http://ergast.com/api/f1/current/5.json ?

    Thank you!

  6. Ab Avatar
    Ab

    Thank you the hardwork on the Ergast database. In the latest version of the csv files is nr 842 (Pierre Gasly) missing.

    840,”stroll”,18,”STR”,”Lance”,”Stroll”,”1998-10-29?,”Canadian”,”http://en.wikipedia.org/wiki/Lance_Stroll”
    841,”giovinazzi”,99,”GIO”,”Antonio”,”Giovinazzi”,”1993-12-14?,”Italian”,”http://en.wikipedia.org/wiki/Antonio_Giovinazzi”
    843,”brendon_hartley”,28,”HAR”,”Brendon”,”Hartley”,”1989-11-10?,”New Zealander”,”http://en.wikipedia.org/wiki/Brendon_Hartley”
    844,”leclerc”,16,”LEC”,”Charles”,”Leclerc”,”1997-10-16?,”Monegasque”,”http://en.wikipedia.org/wiki/Charles_Leclerc”

  7. Ab Avatar
    Ab

    Mine statement above is not correct. Gasly is in the list about 400 places higher.

    Although the list appears to be sorted, it is not.

    Thanks
    Ab

  8. Robert Avatar
    Robert

    Hi,

    I see from the current driverstandings that the permanentNumber from verstappen is not correct. It should be “1” and it’s still “33”.

    But many thanks for providing all these data, makes me very happy! 🙂

    Regards,

  9. Dan Avatar
    Dan

    Hello! Could you please add a “code” property for Oliver Bearman’s “Driver” object. Currently this property is missing for him but is included for all other 2024 drivers.

    Thank you as always!

  10. Admin Avatar
    Admin

    Hi Robert – IIRC permanent numbers don’t change but drivers can opt to use “1” whilst they’re world champion. Hence the API provides both a “number” and “permanentNumber” field.
    Cheers,
    Chris

  11. Reuben Avatar
    Reuben

    Oliver Bearman currently has no date of birth (empty string) – see https://github.com/ReubenFrankel/tap-f1/issues/21.

    Thanks for your work on the API!

    Cheers,
    Reuben

  12. Admin Avatar
    Admin

    Hi Reuben,
    Thanks for the warning – now corrected
    Chris

  13. ash Avatar
    ash

    current driverStandings and current constructorStandings don’t work

  14. Admin Avatar
    Admin

    Hi Ash,
    Standings look ok from here. What’s the issue?
    Chris

  15. Craig Thomas Avatar
    Craig Thomas

    Hi Admin.

    Thanks for this awesome resource and all your efforts to keep it going for so long – I do hope the site/API is able to continue beyond 2024.

    I think there may be an issue with the fastest lap times in the 2023 Austrian race results – they seem out of sequence or attached to the wrong driver compared to the FIA results document.

    Please compare:
    http://ergast.com/api/f1/2023/9/results.json
    To the FIA final classification document:
    https://www.fia.com/sites/default/files/decision-document/2023%20Austrian%20Grand%20Prix%20-%20Final%20Race%20Classification.pdf

    (Apologies if your results are the correct ones.)
    I hope you can check and clarify if the API’s JSON results are correct or not?

    Thanks

  16. Mark Herring Avatar
    Mark Herring

    Hi, thanks for all your great work. I’m having some issues with pitstops. For example if I use:-

    http://ergast.com/api/f1/current/4/pitstops.json

    I believe this should get me all the pitstops for the last race at Japan 2024 in JSON format?

    What I am getting is the first 30 pitstops (which matches what is on the Formula 1 site https://www.formula1.com/en/results.html/2024/races/1232/japan/pit-stop-summary.html) but then there seems to be a further 24 missing from the end. The data seems to be there as I can run something like:-

    http://ergast.com/api/f1/current/4/drivers/hamilton/pitstops.json

    and I can see all of his pitstops including ones that are in the missing 24.
    For the 2024 races so far I’m seeing

    Bahrain – Found 30 missing 13
    Saudi Arabia – Found 19 missing 0
    Australia – Found 30 missing 6
    Japan – Found 30 missing 24

    30 seems to be a limiting factor for some reason.

    Hope you can help.

  17. Craig Thomas Avatar
    Craig Thomas

    This years Saudi result doesn’t seem to match up with the FIA results order. In particular Tsunoda and Sargeant are not in the same order – it may be that the penalties for Tsunoda were not included in the Ergast results?

    Ergast Results:
    https://ergast.com/api/f1/2024/2/results.json

    FIA Results:
    https://www.fia.com/sites/default/files/decision-document/2024%20Saudi%20Arabian%20Grand%20Prix%20-%20Final%20Race%20Classification.pdf

  18. Admin Avatar
    Admin

    Hi Craig,
    Thanks for the warning – now corrected.
    Cheers,
    Chris

  19. Admin Avatar
    Admin

    Hi Mark,
    Have a look at the section on Response Paging in the API documentation. The default response size is 30. You can get all the pitstops in one query by setting a higher limit e.g.
    https://ergast.com/api/f1/current/4/pitstops.json?limit=100
    Cheers,
    Chris

  20. Admin Avatar
    Admin

    Thanks Craig – now corrected
    Cheers,
    Chris

  21. Aditya Avatar
    Aditya

    Hi, the fast lap information for lando and oscar doesnt match up. https://ergast.com/api/f1/2024/6/results.json
    The lap timings are correct but it shows the fastest lap was during lap 1 for both, which is not true, For Noris its 55 and for Oscar its 43.

  22. Admin Avatar
    Admin

    Thanks Aditya – now corrected. There’s something odd about the PDFs this season.
    Cheers,
    Chris

  23. Aditya Avatar
    Aditya

    Hi, the Monaco race results do not have fast-lap information in the results, and the drivers and constructor standings have wrong information for the current points. For example, in the driver’s standings, Lewis has 106 points, as shown in the API, but in reality, this is not true.

  24. baldrick Avatar
    baldrick

    Lewis Hamilton’s Monaco 2024 result is incorrect – the number of points recorded in the database is 71 rather than 7…

  25. Omar van Galen Avatar
    Omar van Galen

    Hi Chris,

    Thanks for the update. The timestamp on the database image page is still on May 19th. Cheers.

  26. Admin Avatar
    Admin

    Hi all,
    Apologies for he issues this weekend. I was on a boat all weekend with only a mobile phone to fix things.
    Chris

  27. Michel Avatar
    Michel

    Thanks again for providing the data. It looks like the pitstops are missing for the Monaco GP. Will those be added later?

  28. Jordan Avatar
    Jordan

    I am developing an iOS app just for myself at the moment but may release for free depending on how things go. I am able to fetch data to display in the app but was trying to also have some data be displayed in a home screen widget.

    I am using the same code and url that is working when the data pulls into the app successfully, but the same fetch/url is not working when trying to pull the data into the iOS widget. Do you know why I would be getting an error here? Do widgets need some sort of customized headers or url or something? Thank you!

  29. Anon Avatar
    Anon

    Hi Chris,
    Can you please fix constructor standings data of the current 2024 season where Mercedes apparently has 160 points instead of the expected 96.
    Thanks.

  30. Admin Avatar
    Admin

    Hi Michel,
    They’re their now. They didn’t initially appear on the FIA site.
    Chris

  31. Admin Avatar
    Admin

    Hi Jordan,
    I’ve had to block the widget user agent because someone developed a widget app which polled (and broke) the API when waiting for the results to appear. You can avoid the block if you change the user agent header – but please do not poll the API in a loop! Only make requests in response to a user action.
    Cheers,
    Chris

  32. Admin Avatar
    Admin

    Hi Anon,
    Apologies – now fixed.
    Chris

  33. Aditya Avatar
    Aditya

    Hi Chris
    Thank you for the amazing API. If possible, could you fix the constructor point for Mercedes? It’s currently shown as 260, but it’s supposed to be 196.

    Thanks,
    Aditya

  34. Admin Avatar
    Admin

    Hi Aditya,
    Thanks for the warning – now corrected.
    Chris

  35. art Avatar
    art

    The latest DB 024-07-07 22:52, does not contain lap times for the latest race. Also, I am interested in how you go about retrieving the lap times since I just learned you will no longer be doing this after 2024

  36. Fush Avatar
    Fush

    Hi
    Thank you for your work on that API. Seems like lap times for the Silverstone race are not available yet.
    Thank you

  37. Adam Vonder Haar Avatar
    Adam Vonder Haar

    It seems like the lap data for the previous race is not showing up: http://ergast.com/api/f1/2024/12/laps.json?limit=2500

  38. Taylor Avatar
    Taylor

    Not a specific bug, but it seems like the api has been experiencing a high number of outages over the past few days, specifically 503 errors.

    Is this likely to continue going forward or is there a known issue that could be resolved soon? Thanks!

  39. Richard Avatar
    Richard

    No lap times for latest season 2024, round 12, British Grand Prix!

  40. Fush Avatar
    Fush

    No lap times for the round 13 of 2024, seems like round 12 was missing the previous time and now that data is not updated properly

  41. Aditya Avatar
    Aditya

    Hi Chris,

    The fast lap info is wrong for the recent Spa GP. It is mentioend that it belongs to Alonso, but it was acutally Perez.

    Thanks, cheers!

  42. Toby Masters Avatar
    Toby Masters

    Hi Chris
    It looks like the database image is still not updated post Spa?

    “The database images were last updated on: 22/07/2024 22:42”

    Cheers

  43. Admin Avatar
    Admin

    Hi Taylor,
    Unfortunately someone has released an app which creates a high load at specific times around race weekends. They’re also using a random user agent string which makes it hard to block!
    Cheers
    Chris

  44. Admin Avatar
    Admin

    Unfortunately, this year, the FIA has not always published all the documents I need for the lap data until the day after the race. I need two specific PDFs.
    Cheers,
    Chris

  45. Admin Avatar
    Admin

    Thanks Aditya – now corrected.
    Chris

  46. Admin Avatar
    Admin

    Hi Toby,
    Thanks for the warning. Now updated.
    Chris

  47. Michel Avatar
    Michel

    There seems to be a problem with the lapdata for the latest race (Azerbaijan). When getting the following URL https://ergast.com/api/f1/2024/17/laps.json?limit=2500 only lapdata for the first 5 laps is returned. Also using a higher limit doesn’t seems to fix the problem.

  48. Michael Avatar
    Michael

    Error in the qualifying data for 2024 Baku – Gasly has Ocon’s driver number (31) instead of his own (10). https://ergast.com/api/f1/2024/17/qualifying

  49. Admin Avatar
    Admin

    Hi Michel,
    The maximum value of the limit parameter has been reduced to 100 due a recent rapid rise in requests using 1000 (see Latest News).
    You can page through the results using the offset parameter e.g. https://ergast.com/api/f1/2024/17/laps?limit=100&offset=100
    Or you request each lap individually e.g. http://ergast.com/api/f1/2024/17/laps/2
    Cheers,
    Chris

  50. Admin Avatar
    Admin

    Hi Michel,
    Re: Baku qualifying – thanks for the warning. Now corrected.
    Chris

Older Comments
1 … 15 16 17 18
Newer Comments

Leave a Reply

Your email address will not be published. Required fields are marked *