Making an accessible API

We’ve been consumers of APIs from many vendors and projects, and so we have opinions on how things ought to work in an API. An API should be:

  • powerful and comprehensive
  • concise and easy to learn
  • documented
  • usable with the minimum of external dependencies
  • stable

Then there’s the difference between a “wire protocol” to a web service and how you interact with a web service from within a programming language. Each programming language comes along with its own “style” – Ruby is heavily OO, PHP is a bit more workmanlike, VB is … well, VB.

Today we’ve published a set of PHP bindings for the API on github. You can now CRUD (“Create, Read, Update and Delete”) your objects in efficient batches in Workbooks from PHP and, better yet, there is accessible documentation and it’s released under the MIT license.

Please, go forth and innovate…..!

Advertisements
Posted in API. Tags: , , . Leave a Comment »

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: