Comments for Ergast Developer API

Comment on Feedback by Admin

Admin — Wed, 04 Jan 2012 14:27:28 +0000

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.

Comment on Feedback by Maksim

Maksim — Wed, 04 Jan 2012 12:36:08 +0000

How about season 2012? I want to use your api in my project.

Comment on Bug Reports by Admin

Admin — Mon, 12 Dec 2011 10:00:55 +0000

Apologies for the outtage. There was a major upgrade by the hosting site this weekend which took out all my PHP scripts.

Comment on Bug Reports by Matt

Matt — Sun, 11 Dec 2011 13:42:01 +0000

Seems to be down today?

All of my requests response are,
“scgiwrap: Caller must be the nobody user”

Comment on Bug Reports by Admin

Admin — Fri, 11 Nov 2011 09:16:54 +0000

Thanks Bob. Now corrected. The results followed the “Top 11″ rule up to the 1981 but not thereafter for some reason. The points have now been corrected 1981-1991. I think 1988 championship was the only place where the problem affected the standings.

Comment on Bug Reports by Bob T

Bob T — Sat, 05 Nov 2011 06:19:49 +0000

Great work, excellent API. One problem: in 1988 only the top 11 results counted towards a drivers WDC points, so although Prost scored more points than Senna, Senna was champion. The API lists Senna’s position as 2nd.

Comment on Feedback by Admin

Admin — Fri, 26 Aug 2011 08:51:46 +0000

Antonio:

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.

Comment on Feedback by Antonio

Antonio — Thu, 25 Aug 2011 09:29:12 +0000

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.

Comment on FAQ by Admin

Admin — Wed, 03 Aug 2011 20:29:30 +0000

I’ve now added JSONP support to all the API calls.

The callback parameter value must be a valid Javascript function name otherwise you get a “400 Bad Request” error.

Let me know if you build anything interesting with it.

Comment on FAQ by Admin

Admin — Tue, 02 Aug 2011 19:36:35 +0000

Ok, I’ve added JSONP support to the Race Schedule call for people to try. If you include a query parameter called “callback” in the URL you’ll get JSONP rather than JSON.

e.g. http://ergast.com/api/f1/2011.json?callback=parseSchedule

Feedback would be appreciated. If people are happy with this approach I’ll add it throughout the API.

Notes:

1. Content-type changes to “application/javascript”

2. Any non-alphanumeric characters are stripped from the callback parameter value.