How to design an API: best practises, concepts, technical aspects

How to design an API: best practises, concepts, technical aspects

When I started to design Piwik I read a lot about APIs, software architecture, service oriented architecture (soa), etc. I really wanted to design a modular architecture that would make it easy to request any data and perform any action from outside the user interface.

Technically speaking, Piwik has been built on the top of Apis. Everything that does some logic in Piwik is available through an API. We basically open all these APIs via a REST API. Of course you must authenticate for some calls eg. when deleting a user. In ther user interface, the AJAX requests are directed to the API module that returns data in HTML or JSON format (javascript friendly).

Main concepts I tried to apply when designing the API:

  • Easy to learn ; the documentation provides simple examples, complete documentation
  • Easy to use ; single entry point, standard parameters
  • Hard to misuse ; explicit error message suggesting parameters values
  • Appropriate to audience ; I had chats about such a service with several phpmyvisites users, and I looked at what the competition was offering

Interesting resources that helped me have a better understanding of the topic:

Of course to design a good API you should have a look at existing APIs, and even use some of them:

If you have good resources or advice, feel free to post a comment

posted @ 2008-08-09 00:24  中土  阅读(368)  评论(0编辑  收藏  举报
©2005-2008 Suprasoft Inc., All right reserved.