If you have any comments, suggestions or feature requests please add them here.
Just a quick suggestion
It would be fairly easy to generate location maps of circuits with the data you are already outputting in xml or json using google maps api or virtual earth
[VE likely to be better as has birds eye view option for major cities]
Sliverstone Aerial only
Monaco [Birds Eye on]
however i would suggest ‘long’ is changed to ‘lng’
as ‘Long’ is a reserved word for many database [SQL] based queries.
it would save troube in future.
An excellent API – well laided out and easy to understand.
This is an excellent API. Is there any chance of getting the race lap times? I believe this is published in PDF format, although it could be alot of data.
Wish I had found it earlier could have saved me sooooo much time when running the Fantasy Formula 1 for my work!
What’s the plans for next season and other sports?
The only current plan is to extend the database to include all seasons back to 1950 when the championship started. In principle, it would be good to cover some other motor racing series but I’m reluctant to take on the responsibility for data entry – this has to be timely and carefully checked. Perhaps the best plan would be to tidy up the code and release it as an open source project so that anyone could set up a service to cover another formula.
I have the 2009 gadget on my site, will it auto-update to the latest 2010 standings after tomorrows race?
Sure – there’s always a short delay whilst I enter the results and then another delay due to Google caching the database queries. The results are typically there within 2 hours.
Quick question, do you plan to add practice results in future/for the 2011 season?
do you plan to add practice results in future/for the 2011 season?
I’ll put it on the “maybe” list for the 2012 season. But does anyone take much notice of the practice results? Not many people are using the qualifying results IIRC.
Great API. One suggestion. It would be nice to have some way to show a photo of the driver, along with his name, nationality and date of birth.
It would be nice to have some way to show a photo of the driver
Thanks for the suggestion. This should be possible for drivers in recent seasons, but perhaps not for all the historical data. I’ll look into it.
How about season 2012? I want to use your api in my project.
Yes, I can confirm that the Formula 1 API will continue throughout the 2012 season. There may be some extensions but no major changes affecting backwards compatibility.
This is a great API and I’m so happy I finally found one which is concise, easy to understand and a variety of return formats. Keep up the good work. I will be using this on my website at some point to make a next race widget.
Would be nice if practice data was available or if you could combine a round so for each node in the round, you would have the practice data, qualifying data and then the race data. You could then build a widget similar to that on Formula1.com.
Great work so far though.
Many thanks for the positive feedback Amit. Be sure to send me a screenshot of your widget for the Application Gallery. I’ll look into your suggestion but I’m not certain there’s a demand for the practice data – there don’t seem to be many requests for the qualifying data. The traffic is mainly results and standings requests!
Great API..is it okay to use this API in my website ,if they like the API can they donate money ? And can I use this data to send messages to all those people who are interested in f1.
All these ideas sound reasonable Ameen.
Hello and great work !
But it was better to have in your database model :
- a relation between a driver and a team (constructor) for a season, and a result have for foreign key this relation
- tables for manage season/position/point
- a “country” table
Thanks for the positive comments and suggestions.
> a relation between a driver and a team (constructor) for a season
I had considered that but occasionally drivers move between teams during the season (like Fisichella in 2009)
- tables for manage season/position/point
- a “country” table
What would you want these tables to list?
> a relation between a driver and a team (constructor) for a season :
You can add in relation between driver and team a position in the team, exemple :
id_team_driver | id_team | id_driver | position
1 Ferrari M. Schum 1
2 Ferrari E. Irvine 2
3 Ferrari M. Salo 3
In tables ‘results’, ‘qualif’, …, use id_team_driver
The advantage of this solution is to list titulare pilots (position tables for manage season/position/point
This relationship allows to answer the question: what is the distribution of points of a season ?
| 1 |
|id_score_system | position | point |
| 1 | 1 | 10 |
| 1 | 2 | 8 |
fk : id_score_system
pk : (id_score_system, position)
A season have an id_score_system.
> a “country” table
It’s better to centrelize countries data (iso2, name, ref …) in other table.
For exemple, if I use iso country code to display a flag icon.
An other question : when is that qualifications are available after the session ?
Hi, amazing set of data. I’ve been using it to power a Fantasy F1 app i’ve built for the office and its been flawless. I’m considering porting it to a Facebook app or similar for next season. Do you have any update on whether the API will available next year?
With race results http://ergast.com/api/f1/current/last/results.json, is there any way to identify with the status entity whether or not the driver actually finished the race, i.e include a DNF string. I’m trying to differentiate between drivers that crashed out or retired and those that managed to stay on the track for the duration of the race.
With the current API you can do this by checking whether the Status field is “Finished” or ends with “Lap” or “Laps”.
This isn’t very elegant so I’ll try to add something specific for the next season.
Fabulous API, really great to have this data available so easily.
Any chance of adding tire type to the pit stop records? It would be really nice to be able to derive tire strategy (and weather conditions) from the pit stop details.
Excellent work on the API. Its so simple to use.
Just wondering how far before the season starts do you update the drivers?
For example for 2013 there are a number of new drivers.
Or does this get populated after the first race too?
One weakness of the current API is that there isn’t a way to list the drivers (or constructors) for the season until after the first race results are entered into the database. This sort of makes sense because you never really know who’s going to turn up until the first race (remember US F1?). However, all the new drivers for 2013 are in the database and this is the driverId line-up for 2013:
Let me know if you build something interesting.
It seems the fastest lap timings were missed off the last race (Spain 2013). Is this an oversight or is this to be expected from now on in the season?
many thanks for a great data provision!
Thanks for the heads-up.
I’m not sure what happened earlier. The lap times are now there. I’ll keep an eye on this in future.
I have (like many before me, I discovered on this website) an application as well for predicting formula 1 results, which I use together with some colleagues. It was only yesterday that I thought of googling ‘Formula 1 API’. My app runs since the 2010 season, and ever since I had to manually configure the app every year, and update post-race results. Now thanks to your simple and clear API this work is all gone. I was able to implement your services very easily, and want to congratulate you on your work.
You have a small, new user-base now based in Belgium
Keep up the good work!
Mail (will not be published) (required)
Notify me of follow-up comments by email.
Notify me of new posts by email.
and Comments (RSS)