The status of web based application programming interfaces.

1. Web Based APIs
Sara Scherieble
Josh Schumacher

2. Introduction
• Application Programming Interfaces
‣ “A source code interface that a computer system or
program library provides in order to support requests
for services to be made of it by a computer program.”
• What makes Web based APIs unique?
‣ The web is evolving - possibilities are unlimited
‣ Real-time communication
‣ Personalized access to information
‣ Data aggregation from multiple sources

3. History
• Traditional Web: Static Information
‣ Hypertext links different information stores
• Introduction of Web Services
‣ Primarily intended for server to server communication
• XML
‣ Extensible Markup Language
• RSS
‣ Really Simple Syndication

4. The Evolving Web
Traditional Web Request Utilizing an API

5. Current State
http://rentometer.com
• Technology
‣ REST, JSON, XML
• Mash-ups
‣ A website or application
that combines content
from more than one
source into an integrated
experience.
‣ Success story of an API:
Google Maps
http://www.chicagocrime.org

6. Using APIs to
Create Custom
User Interfaces
Western Washington
University Residences
Google Search API
Non-Google Search Results

7. Modern Organizations
Who Utilize APIs
• Know more about your users
‣ Utilize information they have given other businesses
• Decreased barriers of entry
‣ Quick development of common tasks
• Automation of existing processes
‣ Example: Google Adsense
• Virgin mobile and social networking

8. Modern Organizations
Who Create APIs
• Traffic and Revenue Growth
‣ Ad Revenue
‣ Fee revenue
• Utilize the developer community
‣ You don’t know what they’ll think of next
• Increased visibility of services offered
• Services conform to customers wants

9. Impact on Operations and Strategy

10. Limitations
• API provider can limit data access
• API provider has to use time and
money to create the API
• Potential high cost to switch
technologies in the future
‣ Developers have invested time and resources

11. Future Trends
• Web as a database
• API providers five simple rules
‣ Keep it clean and simple
‣ Stick to standards
‣ Make it about data
‣ Keep it working
‣ Design for updates

12. Conclusion
• Why should we care about APIs?
• How can we APIs to make money?
• What markets aren’t being exploited?

13. Questions

14. Resources
‣ http://en.wikipedia.org/wiki/API
‣ http://www.sourcelabs.com/blogs/ajb/2006/08/
how_to_provide_a_web_api.html
‣ http://www.readwriteweb.com/archives/
yahoo_pipes_web_database.php
‣ http://www.businessweek.com/technology/content/
feb2007/tc20070213_172619.htm
‣ Yahoo Introduces Search APIs and Developer Network -
Information Week: NA, March 01, 2005. ISSN: 8750-6874