FAQ
- How do the current, last and next shortcuts behave?
- Is there any restriction on how qualifiers can be combined?
- What happens if a round is not specified?
- What is the purpose of the attributes in the table elements?
- How soon after a race will data become available?
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.
Hey,
Is it possible to get the total amount of points for a driver/constructor?
Thanks
It is possible to rise the limit of 30 results? Thanks!
Yes, you can add a limit field to queries with a value up to 1000 e.g.
http://ergast.com/api/f1/drivers?limit=100
Use the smallest value possible for good performance.
It is possible to get all the points in one query but it’s slow and you need to add up the points for each year in the results e.g.
http://ergast.com/api/f1/drivers/alonso/driverStandings
The time for Vietnam Grand Prix is wrong. Also you can constantly check the time and date for other Grand Prix because COVID virus can cause some changes in the times.
Hi John,
I’ve updated the calendar to reflect decisions. I’ll watch for further changes but if you spot anything let me know.
Thanks,
Chris
HI,
I am trying to use the api to get a JSON response but keep getting XML how can i specify to get a JSON response?
Thanks
Hi Brendan,
JSON is obtained by appending “.json” to the URLs e.g.
http://ergast.com/api/f1/current/last/results.json
For more information see the Response formats section here:
http://ergast.com/mrd/
Chris
Chris
Does this also cover fp1,fp2,fp3 and qualifying? And if so how long after those sessions will the data be available
Hi AnonB,
Qualifying is available from 2003 onwards. It’s usually available within 2-6 hours of the session ending. I don’t have time to process the FP data as it’s on a working day.
Chris