Ergast Developer API

172 Responses to “Feedback”

1. Admin says:

   16 September 2016 at 20:50

   Would it satisfy you needs if the site used a self-signed certificate? Unfortunately it costs money to obtain one from a trusted certificate authority.

2. Peter says:

   16 September 2016 at 21:19

   I have used https://letsencrypt.org which is free, very easy to install with Apache and gives a properly signed cert.

3. Jens says:

   10 October 2016 at 11:51

   Great Service. Can you add a constructorlist in the driver details, so it is possible to show all teams for a driver?

4. Daniel says:

   10 October 2016 at 13:13

   Did you already try for example
   http://ergast.com/api/f1/drivers/vettel/constructors
   ?

5. Jens says:

   10 October 2016 at 13:31

   Thanks Daniel, maybe i have overseen it in the documentation, But isn’t it easier to use if you not have to do a second API call?

6. Jorge says:

   31 October 2016 at 17:05

   Will the site be updated to reflect the post race penalties for the USA and Mexican GP?

   USA: Kevin Magnussen was given a post race 5s penalty and dropped to 12th

   Mexico: Sebastian Vettel was given a post race 10s penalty and dropped to 5th

7. Admin says:

   1 November 2016 at 20:31

   Hi Jorge,
   Thanks for the heads-up. All now done.
   Chris

8. Caspar says:

   14 November 2016 at 21:02

   Is there any way to distinguish between a DNS and a DNF? e.g. Grosjean was a DNS in the last race, and Hulkenberg was a first-lap DNF back in Singapore, but their positionText are both “R” and I can’t see anything different to distinguish them.

   Thanks in advance!

9. Admin says:

   26 November 2016 at 17:23

   Hi Caspar,
   The positionText for Grosjean should have been “W” in the last race. I’ve made the correction.
   Chris

10. Stergios says:

    25 January 2017 at 13:33

    Hi there,

    I’m building something really cool on top of ergast! I’ll share it as soon as it is ready. 🙂

    One question. Is there any way to get the fastest lap of a race without downloading all the laptimes of all drivers? I’m using the API, not the DB.

    Thanks!

11. Admin says:

    10 February 2017 at 10:01

    Hi Stergios,

    Yes, the fastest lap for each driver is included in the race results. Loop thru the results and select the one where rank=1

12. David says:

    23 February 2017 at 14:45

    Hi guys!

    Could be possible to add track length to circuit information?

    Best regards,
    David

13. Admin says:

    27 February 2017 at 17:47

    Hi David,
    I did consider this but then realised that the length of many circuits has changed over the years. Unfortunately, the data model doesn’t allow circuits to have temporal versions.

14. Bart Delano says:

    3 March 2017 at 12:11

    Hi Admin,

    Are there changes expected for the 2017 season or will the data of the database image and rest calls be the same as in 2016?

    Greetz,
    Bart

15. Admin says:

    5 March 2017 at 22:46

    Hi Bart,
    I’m not planning any changes to the database or API this year which will continue into the new season.
    Chris

16. Bart Delano says:

    6 March 2017 at 08:18

    Thanks Chris!

17. Stergios says:

    20 March 2017 at 10:42

    Hi Chris,

    I’ve just launched this blog (f1-predictor.com) where I’ll be posting on quali and race predictions. All underlying data are, of course, taken from your excellent API.

    I’ll prepare more cool analyses in the future.

    Thanks for your great work,
    Stergios

18. Emma says:

    27 March 2017 at 10:27

    Hi, great API, really useful so far!

    I’m writing something for a fantasy F1 game which has some (imo) weird rules.

    Is there a way to tell the actual start position?
    The example I’m working with is:
    RIC’s grid for the (2017) Australian GP was P15, but he actually started the race a few laps down, from the pit lane as he broke down on the formation lap. So then everyone from P16 up effectively started the race one place higher than their grid.

    Is there any way to tell that from the API?

    Thanks in advance,
    Emma

19. Admin says:

    27 March 2017 at 12:30

    Hi Emma,
    Thanks for the positive comments.

    Ricciardo’s grid position was recorded incorrectly and has now been updated - the API uses ‘0’ to indicate that a driver started from the pit lane (I’ll add a note to the documentation).

    Note that drivers don’t move up the grid when this happens - they leave the slot unoccupied.

20. Søren says:

    29 April 2017 at 16:36

    Hi,

    Would it be possible to add a position filter for qualifying results like race results? Like this:

    /qualifying/1

    It’s not that big of a deal that the option is missing, but I’m guessing it would be pretty simple to implement and it would also make it more consistent with the race results API.

    Best regards,
    Søren

21. Admin says:

    30 April 2017 at 17:35

    Hi Søren,

    Good point. I’ve now allowed it in qualifying queries e.g.

    http://ergast.com/api/f1/current/last/qualifying/1

    However, for the time being you can’t specify a qualifying position in other types of queries - this would need a lot more work.

22. Chris says:

    16 May 2017 at 18:26

    Thanks for this great resource. Curious if there is any information out there about tyre data for each lap?