ESPN Developer Center Developer Blog
Today we are excited to announce the beginning of what will be an ongoing relationship with you, the ESPN developer community. Going forward we will be making regular announcements regarding the ESPN API, including the availability of new content, feature enhancements, and bug fixes right here on developer.espn.com.
Since our launch on March 5th we’ve had the opportunity to meet with many app developers and businesses of all sizes, and by following Tweets, forums discussions, and other avenues of feedback, we’ve learned a great deal about what developers are hoping to get from the ESPN API and what our team should be focused on to best serve those interests.
f-dub's ESPN Stories demo was one of many interesting creations made with the Headlines API
While we know there’s work to be done, it’s been exciting to see some of the great innovations come from our developer community in just a couple short months and with a limited dataset. We’ve seen plugins for Wordpress (nice work davidpean) and Drupal (not bad, erikwebb) to tap into news content from our Headlines API. A handful of great SDKs have been created in popular languages like PHP (by madcaplaughs), Ruby (rondale_sc), Grails (Nick Hagen), and Python (Chad Masso). We’ve seen some excellent tutorials for creating products with the ESPN API (awesome job f-dub ), a slick Ruby/Padrino playground (by Brian Jackson), and we’ve been able to launch some pillar ESPN apps that leverage our APIs, like the new ESPN Radio iOS app and our ESPN Hub app for Nokia Lumia phones.
In addition to enabling our own product development and strategic partnerships, we are working on many aspects of improving the ESPN API for both smaller companies and public developers.
- Effective immediately, public developers can now make up to 7,500 API calls per day (an increase of 5k/day). We’re also working on making additional data available that would allow for broader creativity and usage to help build innovative applications. As more data is made available we will announce it here on the blog.
- For smaller companies and independent app developers with commercial needs, we are looking at a way to make a set of ESPN content available to this group. We are aiming to have additional details on this offering later this year. In the meantime, we ask that companies interested in a strategic partnership with ESPN contact us. Due to the large volume of inquiries we’ve received it can take us up to 2-3 weeks to respond, but we will reach out. We appreciate your patience while we work on a more streamlined partner offering to meet this demand.
Speaking of making more data available, we’re finally to the fun part. We are happy to announce the following enhancements to the ESPN API:
- Olympics and ESPNW (our online destination for female sports fans) news is now available through the Headlines API.
- Athlete ID and name information across all sports is available to all access tiers in the Athletes API.
- Team ID, name, color, and venue information across all team sports is available to all access tiers in the Teams API.
- College football and college basketball player biographical data (including height, weight, position, age, birth date and birthplace) is now publicly available to all developers via our Athletes API.
For our internal developers and strategic partners, the following enhancements have been made:
- Team logos are now included in the Teams API and as an option in the Scores, Athletes and Standings APIs.
- College football and college basketball recruiting data is now available in the Athletes API.
- Story text (both standard and Mobile, where available) can be optionally disabled in the Headlines API by using a disable=story,mobileStory parameter.
We hope you enjoy the improvements. Stay tuned for more announcements in the coming weeks.