A field guide to web APIs

Table of Contents

  1. Summary
  2. What are APIs used for?
  3. Why are web APIs different?
  4. History of web APIs
  5. What technology goes into an API?
  6. Deploying your web API
  7. Established practices for managing APIs
  8. Marketing and API evangelism
  9. The future of web APIs
  10. Cloud trends
  11. Key takeaways
  12. About Kin Lane


A new breed of web API has emerged, delivering a vision of a lightweight, low-cost approach to connect devices and allowing applications to exchange data efficiently.

This research report is a field guide for web API providers, developers, and even nondevelopers. Among its key points:

  • Previously APIs required custom technology, protocols, and often costly implementations, but web APIs build on existing technology, specifically the HTTP protocol that the world wide web employs to deliver content worldwide — with no need to invest in new technology.
  • Simplicity rules. The web API providers that simplify interfaces and encourage adoption (even to a nondeveloper audience) are emerging as the leaders.
  • The purpose of web APIs is to deliver valuable, scalable, and distributed resources across the internet. This requires four ingredients: commerce, social, the cloud, and mobile.
  • Application-developer onboarding requires clear steps. App developers should be able to register, authenticate, and access documentation, code samples, support, and any other resources essential to API integration. And they need to do it easily.
  • Opportunities for web APIs are emerging in the internet of things (IoT) — internet connectivity applied to everyday objects — in automobiles, homes, and building connections as well as in health and fitness and in manufacturing with 3D printing.

Source: flickr user Mike Baird

Request Access

Available to GigaOm Research Subscribers

  • Required

  • This field is for validation purposes and should be left unchanged.