“Of the 140 enterprise IT professionals polled in May, more than 43% of respondents reported that their organization currently had an API program in place, while 27% said a program would be launched within the next year. Respondents to the survey overwhelmingly pointed to a broad range of key business goals driving the growing need for API programs, including:
Mobility programs (71.9%)
Partner connectivity (69.1%)
Cloud integration (67.6%)
Enabling internal developers (66.9%)
Fostering external developer ecosystems (55.4%)”
What’s an API you say?
For the uninitiated, here’s part of the Wikipedia answer:
The practice of publishing APIs has allowed web communities to create an open architecture for sharing content and data between communities and applications. In this way, content that is created in one place can be dynamically posted and updated in multiple locations on the web.
- Photos can be shared from sites like Flickr and Photobucket to social network sites like Facebook and MySpace.
- Content can be embedded, e.g. embedding a presentation from SlideShare on a LinkedIn profile.
- Content can be dynamically posted. Sharing live comments made on Twitter with a Facebook account, for example, is enabled by their APIs.
- Video content can be embedded on sites served by another host.
- User information can be shared from web communities to outside applications, delivering new functionality to the web community that shares its user data via an open API. One of the best examples of this is the Facebook Application platform. Another is the Open Social platform.
- If content is a direct representation of the physical world (e.g., temperature at a geospatial location on earth) then an API can be considered an “Environmental Programming Interface” (EPI). EPIs are characterized by their ability to provide a means for universally sequencing events sufficient to utilize real-world data for decision making.”
Thanks to Cloud Computing Journal