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:


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:


For example:


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:


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 2 – 6 hrs.

171 Responses to “FAQ”

  1. Admin says:

    Hi John,
    Information about the structure of the database can be found on the Database Images page, including an Entity Relation Diagram.

  2. Morgan Badet says:

    Hello Admin,
    I have a little question,
    When will the database will be updated ?
    Because I need the driver’s name for the beginning of the 2021 season

    thanks !

  3. Zoltan says:


    first of all thanks for this API.

    I’d like to use your API for a small site for personal usage for me and some friends. My question is about this:

    “You must not create any application which polls the API more than four times per second or more than 200 times per hour.”

    Can you please give me some more details about it.
    – how do you identify the source: by IP or by the origin in the header?
    – 4/sec and 200/h is for the whole API or by endpoints like race schedule and standings count separately?


  4. Admin says:

    Hi Zoltan,
    > how do you identify the source
    It’s per client, so each of your users can poll within these limits.

    > 4/sec and 200/h is for the whole API or by endpoints
    It’s the whole API

    I know the limits are annoying but people with a popular app can easily create unintentional DoS attacks – and this has happened!

  5. Edgar says:

    Hi. Is there a way to select drivers of a specific year?

  6. Admin says:

    Hi Edgar,
    If you want a list of drivers from a specific year use:
    For example:

  7. Clement says:

    Hi Chris,

    first, thank you for the time and effort you put into this API, it’s truly great.

    I read the terms and conditions and I was wondering if I can use it in an app that is free, and have a donate button in it or have a pro version of the app that allows access to another API for live scores but that doesn’t restrict or use data from you API ?


  8. Admin says:

    Hi Clement,
    You’re welcome to use the API in a free version of an app – but not in a commercial version.

  9. Alwyn says:

    Hi Chris,
    Are you guys planning on adding more historical data to the qualifying results? I see it is currently only going back to 1994. Would love to have access to data from 1950 onwards as I’m planning on building a free to use website that will show driver records vs their teammates in regard to qualifying, race results.

    Please le tme know. Thank you!

  10. Admin says:

    Hi Alwyn,
    I’d be happy to add more, if someone provides the data in SQL or another machine-readable form.

  11. John says:

    Hi. I want to ask about your database. For example, I want to get driver standings(driver’s name and constructor) of a specific year? How can I do this in SQL?

  12. Admin says:

    Hi John,
    You can see the SQL queries used by the Driver Standings API here:
    You can compare this against the database table details here: http://ergast.com/docs/f1db_user_guide.txt
    Let me know if you need more details via admin@ergast.com

  13. Alistair says:

    Is there any way to know on which laps the safety car was on track ?

  14. Tijmen says:

    Hi, first of all, I would like to say that this looks like a great API. I was wondering if there is any way of knowing whether it rained during the race.
    Kind regards,

  15. Admin says:

    Hi Alistair,
    No, there’s no explicit signaling for the safety car.

  16. Admin says:

    Hi Tijmen,
    No, there’s no data about the rain.

  17. Andrew says:

    Hi, thanks for making this available, I was keen to know if it is possible to get what tyre type they were running for a specific lap? Cheers

  18. Admin says:

    Hi Andrew,
    Unfortunately I don’t have a reliable source of tyre information, so haven’t been able to support this.

  19. Gus says:

    Do you have or are able to get data about the teams current engine parts used during the season e.g. how many MSU’s used out of available etc?

    Many thanks

  20. Admin says:

    Hi Gus,
    Unfortunately not. It would be very interesting.

Add a Comment: