Freek.dev

V2.0 of the API was a weird hybrid of RESTful and RPC practices, which required everyone to learn our own special style of API design. With a few minor exceptions, API v3.0 is fully RESTful. This allows us to express in a couple dozen resources what it took the last version 120 distinct endpoints to accomplish.

Consuming this API doesn't seem to be that hard but I hope they'll release a PHP wrapper soon.

Read more

... it’s important to remember that API design isn’t strictly about the practical implications on client and server software. The audience for an API is the developer who is going to consume it. Per the "principle of least astonishment," developers will have an easier time learning and understanding an API if it follows the same conventions as other APIs they’re familiar with.

Read more

Having documentation on your API is highly beneficial. If it is well written you're likely going to receive less questions by consumers of your API about how it works.

Aglio is a nice tool that I've been using to generate API documentation. In goes the Markdown, out comes the beautiful documentation.

Read more

Google introduced a new method that verifies you are human without you having to solve a riddle.

On websites using this new API, a significant number of users will be able to securely and easily verify they’re human without actually having to solve a CAPTCHA. Instead, with just a single click, they’ll confirm they are not a robot.

It looks like this:

http://googleonlinesecurity.blogspot.nl/2014/12/are-you-robot-introducing-no-captcha.html

Read more