Tips for Providing a Web API

Alex Bosworth over at Source Labs (and creator of the great open source resource SWiK) writes consistently good posts and Monday's was no exception: How to Provide a Web API. In it he addresses the question of "What are a few simple rules for providing a web API?" with these five points:

  1. Keep it clean and simple
  2. Stick to standards
  3. Make it about data
  4. Keep it working
  5. Design for updates

I completely agree with that list and might also add: a) provide examples, and b) document and support it. Neither of these need to be super extensive/expensive, just enough to get things kick-started (docs/examples) and help support the developer community as it grows. This reminds me of Nat Torkington's excellent post awhile back on How To Roll Out An Open API. He makes a good case that providers should: Make signup simple, offer toolkits for the languages that Internet developers use, and think laterally about business models. Recommended reading.

John Musser



I would also highly recommend supporting any API with a developer website, with forums, example code, feedback, etc.

More important than the actual technology is getting it to work for you. Only 20% of development is writing code, the other 80% is figuring out how.



<strong>Web Services: Gestaltung der API</strong>

Kern des Web2.0 sind unter anderem Web Services welche über eine sogenannte API von anderen Diensten genutzt werden können. Da es unzählige Möglichkeiten gibt solche Schnittstellen zu beschreiben und umzusetzen macht es Sinn einen kleinen Ãœberblick Ã

[...] You can find lots of other interesting APIs at programmable web, a directory for mashups and APIs (API list at And also some tips when creating your own web api. [...]


Yes it's absolutely right. Support is most important when you are providing a web API because it will help you to fix errors as well as retain the customer.