Recently ESPN opened up their treasure trove of data to the developer community by releasing an API.
It looks great, well documented, REST based, intuitive. There’s also some useful tools around the API like a few helper methods that return the data required for making use of their advertised capabilities and a useful ‘health status‘ site.
Now before we get started let’s look at what do we have here:
- ESPN sports data, the innovation possibilities here are almost endless. Available categories include:
- Sports headlines
- Score & Game schedules
- Team data
- Athlete data
- Research notes (player stats & information)
- & much, much, more.
Using Mule it would be reasonably straight forward to invoke the ESPN API directly using an http endpoint, or a combination of custom components. However if I want to package all the methods exposed by this API and make it easily accessible to all of my developers the Mule DevKit is the best option.
Using the DevKit I can create a reusable Mule Connector that abstracts all of the low level implementation details related to interacting with the ESPN API that include, REST specifics (GET, PUT, POST, etc…), security, session management, and the configuration process. In addition to that once complete I can easily share this component with all developers in my organization using the Mule Studio eclipse update site capability, or alternatively with the entire Mule community on the Mule Extensions site (note: the artist previously known as the Mule Forge).