FAQ

Ask additional questions using the comments box.

How do the current, last and next shortcuts behave?

For the purposes of the API, a season is assumed to begin when results become available for the first race of the season. This transition will be seen if the <season> field in URLs is set to "current".

In a similar way, the changeover point for the "last" and "next" round shortcuts occurs when a new set of race results become available. After the last race of a season the URL:

http://ergast.com/current/next/...

will refer to the first race of the following season.

Is there any restriction on how qualifiers can be combined?

A query can include any combination of the following qualifiers unless otherwise stated:

/circuits/<circuitId>
/constructors/<constructorId>
/drivers/<driverId>
/grid/<position>
/results/<position>
/fastest/<rank>
/status/<statusId>

For example:

/drivers/alonso/constructors/renault/results/1

The order of the qualifiers has no effect except that the last one determines the result type.

Season, Driver, Constructor and Standings queries can include the following qualifiers, subject to certain restrictions:

/constructorStandings/<position>
/driverStandings/<position>

The last qualifier in a query determines the type of data returned.

What happens if a round is not specified?

For Standings queries and queries which include a standings qualifier the round value defaults to the last round of each season (i.e. the final standings). Otherwise a query covers all rounds of a season.

What is the purpose of the attributes in the table elements?

All responses contain a table of some kind. The attributes of the table element define the scope of the table and reproduce the criteria specified in the original query. If a specific attribute is omitted the scope concerns all entities of that type e.g. if there is no driverId attribute the scope of the table is all drivers who match the specified criteria.

How soon after a race will data become available?

Usually in 3 – 6 hrs.

71 Responses to “FAQ”

  1. James Murrell says:

    Big Thanks….

  2. Bas says:

    Hey there Chris,

    first of all thanks for supplying and maintaining this API. I’m using it (for educational purposes) as an example in workshops on testing RESTful APIs and was wondering if there is any way to run the whole API locally (inside a VM or a Docker image for example) to prevent any issues with the API being temporarily unavailable at the time of my workshops..

    Thanks in advance for your answer and keep up the good work!

    — Bas

  3. Admin says:

    Hi Bas,
    Unfortunately there’s currently no way to do this – but it’s a nice idea. I’ll think through the implications of releasing the server code – maybe someone would add the cloud support? On the plus side the API is usually pretty reliable.

  4. Bas says:

    Hi Chris,

    thanks. The reason I asked is (of course) because I ran into this situation before.. I’ll find a suitable way of dealing with this though, no worries. Maybe recording traffic through a proxy and using that to generate stubs.

  5. Robert says:

    Hi,

    I like your API a lot. Tester and wrote scripts to test data and making imports to a Joomla component. I want update the qualifying results and race results. Is the qualifying data coming the same day as the race results?

    Or do they come the same day as the qualification rounds end?

    Robert

  6. Robert says:

    When are qualifying results become available? Is this after the race or when qualifying results are present? (Last qualifying date)

    Thanks for the great API!!

  7. Robert says:

    Sorry for the double post, I had the wrong ordering and did not saw my first post..

  8. Admin says:

    Hi Robert,
    Thanks for the positive comments. Qualifying results are usually available a couple of hours after the qualifying session ends.

  9. Rob I says:

    Is there any way, either now or in the forseeable future, to get sector time data in addition to laptime data? Either way, love the work you’ve done here. I was hoping to implement a ‘live’ laptime dashboard for people like me who watch the races on ‘tape delay’ or people watching old races and whom would still love a live timing screen. I’ve worked out a simple method for users to start the ‘live’ timing and the race video at the same time so that everything will ‘sync’; but I was curious if sector times were available somehow I’m missing or if that data just isn’t there. Either way I intend to complete the project because even with just whole laptimes I think there’s a lot of value. Thanks for your hard work!

  10. Admin says:

    Hi Rob,

    Unfortunately not. I’m not sure there’s a source.

  11. Nag says:

    Hi,

    This is a great resource, and I’m thinking of building an app that uses this API. It’ll be on iOS, and it will be personal (my wife and I will use it, not on the App Store).

    Do you see this project continuing into 2018 and beyond? I’m only a hobby programmer, so I don’t want to spend a lot of time if this API is scheduled to be deprecated soon. Also my wife won’t be happy if her app stops working..

  12. Admin says:

    Hi Nag,

    Yes, the API will continue, at least for the next few years.

  13. Nag says:

    Thank you for the response.

  14. Victor says:

    Hi,

    This is an interesting API, I am an iOS developer and I would like to develop a statistics application for my own use, I have worked with Restfull API and in all of them “always” there is an authentication system except this one. You need to have a control over who is consulting your API, you have to protect yourself from malicious developers. Please, to solve this, read a bit of OAuth2 or similar. I hope this is useful for you. Sorry for my bad English, I speak Spanish 🙂

  15. tob says:

    Hi,

    great API so far. For my App I would like to get the date and time of the F1 qualifying which isn’t stored yet. The problem is that the qualifiying isn’t always 24h before the race. Is it possible to get that additional data?

  16. Admin says:

    Hi Tob,
    Unfortunately, it’s quite hard to find this info before the season starts so I haven’t included it in the schema. Do you know of a reliable source?
    Chris

  17. tob says:

    Hi Chris,

    thank you for your fast response. I think http://www.f1calendar.com is a reliable source for that, but I don’t know how fast they update their data for a new season. But maybe you can have a look on that website.

  18. Kamil says:

    Great API, thanks for your work on it… Just a quick question – is there any problem with this week data? I am trying to get qualification data, but it still looks empty. Is there any problem or API change? Thanks, Kamil

  19. Brad says:

    Hi Chris, I hope all is well. Is there an estimate on the Spa data update? My wife and I very much enjoy your efforts and use the data as F1 fans to enhance our PHP and MySQL skills.

    Best
    -Brad & Karen

  20. Admin says:

    Hi Kamil, Brad,
    Sorry for the delay – there have been a number of technical issues this weekend. The qualifying data is now available and a MySQL dump (without lap times as these still need to be fixed)
    Chris

  21. Vivec says:

    Hi Chris,

    Just wanted to say thank you for this great resource.
    Developing a nice dashboard for this data. Hobby project :).

    I’m now trying to find resources for:
    – tyres (and usage per lap)
    – engine manufacturers (linked to constructor and results)
    – perhaps even engine (type) usage
    – penalties
    – weather per event

    It’s incredibly hard to find comprehensable resources.
    Wikipedia holds a lot of data, but almost never in a fixed structure (for scraping)…

Add a Comment: