If you have any comments, suggestions or feature requests please add them here. Problems and errata can be reported on Bug Reports page.

371 Responses to “Feedback”

  1. Admin says:

    Hi Daniel,
    Unfortunately not, apart from disqualification being shown in the status and time penalties being added to the final times.

  2. Ayoub Nay says:

    Hi first of all i want to say thank you for this amazing API.

    i just want to ask for the possibilty to add more info about drivers(height,age,carrer points,championships won) and Teams(points,WCC,current drivers).

    Thank you.

  3. Admin says:

    Hi Ayoub,
    I try to keep the API lightweight, so it’s easier to maintain and the API responses are compact. I think the points totals you suggest could be determined by one API query and a summation at the client.

  4. Marco says:

    Dear Sir or Madam,

    first of all amazing API.

    i found a little error. In the JSON for DriverStandings the code like “HAM” or “VER” arent there for some reason on the years 1950-2015. But only some are missing like for example in the year 2001 Hakkinen has no code like “HAK” or so.

    Yours faithfully,

  5. Admin says:

    Hi Marco,
    The driver codes were added a few seasons ago, following a request. I don’t think they have existed for all of Formula One’s history. If someone can provide codes for earlier drivers I would be happy to add them to the database.

  6. Adam says:

    Good afternoon,
    I just wanted to say thank you for creating such a fantastic resource. I built my entire final project (simple F1 Android app in an intro to app development course) using it, in conjunction with the actual F1 website.
    Thanks again,

  7. Admin says:

    Hi Adam,
    Many thanks for the positive comments. That’s great to hear.

  8. Peter says:

    Hey, first of all thank you for your API it’s very great! I had a question. Is there a possibility to add more schedule information about training and qualifying.

    Thank you so much again,

  9. Admin says:

    Hi Peter,
    Ideally I would, but it’s hard to find this information at the start of the season. It’s even hard to find the date/times for the race schedule and keep these up to date with the changes which follow.

  10. Christian Rokitta says:

    Hi, Any chance the tire set info (with either lap-times or pit-stop data) could be provided too?
    Cheers, Christian

  11. Admin says:

    Hi Christian,
    I’ve never been able to find a reliable source of tyre data from year to year.

  12. Suvashan says:

    Hello Admin

    I have been a long-time user of this API, and I have decided to write a simple python script to obtain tyre changes that are made during the race and I have inserted them into MySQL. This data comes straight from the press.pirelli website (if you are not familiar, for example, the tyres used for the 2021 bahrain gp can be found at–sunday/). Unfortunately, this data is only available from 2019 til now. Please let me know if you would like to take a look at this and potentially add this data to the API.


  13. Dave says:

    Why doesn’t driver information contain their current team or anything beyond their name and birthday?

    What a useless data point. Literally useless.

  14. Admin says:

    Hi Dave,
    The endpoint is intended to provide filtered lists of drivers, subject to a set of criteria. So, for example, you can get a list of all the drivers active in a particular year – or have driven for a particular constructor. If you want to know a drivers current team you can use the standings endpoint e.g.

    If you want more biographical data you can access other databases using the Wikipedia page ID e.g.

  15. Mike says:

    Wanted to say what a great resource! Just stumbled upon this in the last few weeks, it’s great. Wondering if you are thinking about adding datasets for the Sprint Qualifiers? I know it’s not set in stone as to if it’s going to carry on. Just wondering.

  16. Admin says:

    Hi Mike,
    If the sprint races becomes a permanent feature I’ll support them – but it’s not trivial because they’ll require a new database table and all the things needed to support it.

  17. Alistair says:

    I’ve been using your database for quite a while now and I was wondering if there was any way to collect the Final starting Grid

  18. Admin says:

    Hi Alistair,
    Yes – the final grid positions are in the results table e.g.

  19. Alistair says:

    Thanks a lot but it looks like it the final results whereas I was looking for the final STARTING grid positions (before the first lap but after the qu’Ali with applied penalties)

  20. Admin says:

    Hi Alistair,
    There’s a “grid” field for each driver in the data. That’s the Final Starting Grid positions, with occasional adjustments when someone starts from the pit lane after the formation lap.

  21. Justin says:


    Fantastic database, I really am enjoying learning python with it. I was wondering if there was an end point for the number of laps that a race is supposed to have? I’m trying to determine how best to handle issues like Spa this year where the race only technically had two laps, but it should have had more. This is so I can figure out if I need to award half points or not.


  22. Admin says:

    Hi Justin,
    Unfortunately, there isn’t a race laps field. It’s not usually an issue – Spa was an anomaly.

  23. Admin says:

    Thanks Lasse – now corrected.
    I should have a format checker.

  24. jim says:

    Hi Admin,
    What a great DB for people who love f1 and python! I have been using it for a few months now.
    Just an issue (probably just me though) happened recently.
    When I download the latest DB (f1db.sql.gz MySQL 5.7 database dump) and run a local version, I can get any race results past round 15.

    When I run
    This is my result:

    Is the DB incomplete??
    Can you advise at all please?

  25. Admin says:

    Hi Jim,
    I’ve re-issued the dumps in case there was a problem. If you gunzip the dump and search for `seasons` to find the seasons table then just above it will be the end of the results table. You should see 20 entries like this:


    where the second field on each line is the race ID (1073) for the round 2021/22.
    Try loading this new dump to see if it solves your problem. If not, check for error messages when you load the dump.

  26. jim says:

    Thanks Admin,
    It looks like there was nothing wrong with your DB.

    I ran “docker-compose up –build -d –remove-orphans” to rebuild the docker image and it fixed the problem.

    Sorry for the trouble, I should have done this first.

    Thanks for the great data, looking forward to 2022 season!!

  27. jim says:

    Hi Admin,
    One more question, how do I form the API to return the “milliseconds” field in the “lapTimes” table? (if an API for that is available).

    I have tried many combinations but just get “bad request” error.


  28. Admin says:

    Hi Jim,
    The query used by the lap times method is here:
    You should be able to adapt it to return millis instead of the time field.
    Good luck!

  29. Borna says:

    Just wanted to thank you for creating and maintaining this great API. I used it in one of my college Android projects and it’s been a wonder to work with.
    Many thanks and best of luck!


  30. Admin says:

    Hi Borna,
    Thanks for the positive comments – I’m glad the API was useful. Let me know if you want to add your project to the Application Gallery.

  31. Niall says:

    Hi Chris,

    Congrats on a wonderful API. I really enjoy using it and appreciate the time/effort/expense to make it.

    I am building a fun webapp sideproject that uses Ergast F1 API data (cached on my site) to calculate driver points on the fly for previous seasons. For example – did you know that had one of the succeeding points schemas been in place (2003 1st-8th or 2010 1st-10th) in 1999, Eddie Irvine would have been champion?!

    I have developed an extensive calculator that works out the points awarded to each driver for a given race. It even allows you to play “What If…”

    example: Who would be Formula 1.5 champion each year if you ‘disabled’ the top tier teams and re-distributed wins/position/points to other drivers who are not in the top tier team?

    My question:
    Would it be at all possible to add an optional “sprintPosition” number field to drivers’ race results? It would make life immeasurably easier to just have that small field of data for the 3 weekends where there were sprints in 2021 (and 2022 onwards)

    Many thanks,

  32. Admin says:

    Hi Niall,
    I’m currently working on support for the Sprint Qualifying sessions. This will be a separate API query to the results query. However, I will backfill data from 2021.

  33. Niall says:

    Chris, sounds terrific thanks so much.

    Another quick query for you:

    I can’t seem to find any data on “Scheduled” Laps for a race. For example, Malaysia 2009 was scheduled for 56 laps, but Button the winner only completed 31, therefore half points were awarded.

    Is there any endpoint or database table that provides the scheduled number of laps for a race event?

    Many thanks again,

  34. Admin says:

    Hi Niall,
    Unfortunately that’s not currently supported. Is it published somewhere pre-season?

  35. Niall says:


    I played around with a few sites and managed to find one site so far that’s useful:

    They wrap the scheduledLaps in a div with a data attribute “data-source=’scheduledlaps'” so it’s possible to scrape it programatically assuming all races are rendered the same.


    Run this in the console:
    Number(document.querySelector(“[data-source=’scheduledlaps’] > div”).innerText.split(‘ laps’)[0])

    // 56

    If I were to go and scrape all the scheduledLaps data for you, would you be interested in appending it into the database?

    I’ll probably end up scraping it for myself anyway and locally appending to the data your API has kindly provided. At the moment for half-point scoring races, I am inferring it’s a half points race by looking at the points awarded for the winner -vs- what they should have received were it a full run race distance for that years points scoring system.

    Feel free to DM me @noccer on twitter or you have my email.


  36. Admin says:

    Hi Niall,
    Thanks – I’d prefer to use an official source if I can find one. I’ll have dig around.

  37. Filip says:

    Hello Chris!

    Is it possible for you to update the tables diagram and database user guide to include the sprint tables/columns/data? I assume there might be an added column in the results table which indicates if it’s a sprint or a race but might be totally wrong! 😀


  38. Daniel says:

    Shows the latest season that had a race, however this can be confusing during the “pre-season” stage (which we are currently on). The docs say the after mentioned endpoint retrieves the current season, however when the season is over and preseason testing starts I would argue the upcoming season is the current one.

  39. Admin says:

    Hi Daniel,
    It’s been like that for 14 years but I agree, it’s not ideal. Next season I will make it change with the calendar year.

  40. Emre says:

    Hello again,

    We continue to use your service. We are grateful. We are using the Docker version, but the data here is from 2021. Are you going to update the data here?

  41. Admin says:

    Hi Emre,
    Unfortunately, I don’t know anything about the Docker version. Is it this one: ? The author may be able to help. Perhaps you just need to update f1db.sql.gz which you can download here:

  42. Filip says:

    Hello Chris!

    It would be kind of nice to have the countries/nationalities in ISO 3166-1 format! Also the nationalities between constructors and drivers sometimes are not the same. For example Belgium has “belgium” and “belgian” or New Zealand with “new zealand” and “new zealander”.

    Take care!

  43. Admin says:

    Hi Filip,
    Thanks for the feedback. I only found two examples (in the constructors). Hope that’s all of them.

  44. Filip says:

    Hello again Chris!

    That’s nice to hear! There might be an issue with the race Wikipedia url for 2021 Brazil race :S My URL validator is throwing a “MalformedException” when checking it which I presume is due to the “ã” character it contains (“ão_Paulo_Grand_Prix”). When using the link it takes me to “” instead which I assume is the “final Url” this one reroutes to. What are your thoughts on the matter? 🙂


  45. Admin says:

    Hi Filip,
    I’ve aded the year and applied percent-encoding so it should now be valid and correct.

  46. Filip says:

    Hi Chris!

    Awesome! I have yet another question :’) When fetching driver standings per round in season, if a driver has made a swap from, let’s say Toro Rosso to Red bull, both teams are listed in constructors for that driver. Will the order of the constructors always be in the order as gone through the season? In other words: will the driver’s current team be the latest in that list?

    Thank you!

  47. Admin says:

    Hi Filip,
    The driver’s current team will be the latest in the list – where “current” means the last set of results.

  48. Filip says:

    Hi again Chris!

    Thank you! I have been unable to find a way to get the lap times and (if any) pitstops of sprint races! Is this a feature that could be added? I have also been unable to find a way of getting the drivers’ best FP1, FP2, FP3 times, is this also something that might be added? Another very small thing would be if “Fastest Lap” data contained a field for something like “PointsAwarded” or something as one could get fastest lap but not get points for it. This can of course already be deduced by counting the points the driver’s got but for different eras of rules that can be quite hard. Please let me know your thoughts on these suggestions! 😀

    Thank you!

  49. Admin says:

    Hi Filip,
    It’s hard for me to find time to add additional data, particularly on Fridays. Maybe when I retire!
    I think about the fastest laps point – unfortunately the rules keep changing.

  50. Christian says:

    Hi Chris! As an F1 fan and developer, I have been taking a look at your API with a project in mind and its an amazing resource!

    I wanted to suggest an idea, not sure if anyone suggested it earlier. It would be great if possible to use “greater/less than” modifiers to the position qualifiers. For eg. you could get Verstappen’s 2021 wins at, but if you wanted his podiums, I believe you would need to either:
    1) Fetch a lot more data than necessary to then filter it client-side, or
    2) Join results from 3 separate API calls (even worse if you wanted to get top 10 results or something like that)

    Please let me know if there’s already some other method I missed in the documentation. But if there’s not, I think it would be good to be able to do something like “/results/3ls” (meaning 3 or less) if you wanted to fetch his podium results, or “/results/4gr” (meaning 4 or greater) if you wanted his finishes outside the podium, for example. I think it would be a neat feature and one that shouldn’t break any backwards compatibility. Same if you wanted a driver’s front-row starts, for eg.

    Please let me know your thoughts. Thanks! 🙂

Add a Comment: