Blue(print)+(post)man - clever! Use Drafter to convert your .apib file into .json, then use Blueman to convert json to a postman collection.json, open postman, import it, voila! Currently needs a little work around until Protagonist is ready to replace Drafter, instructions here.

Building a JSON API, you should be trying to follow the JSON API spec. Save your team the effort of arguing the best response format. It reached version 1.0 earlier this year, so it's safe to say there won't be too many big changes now.

It defines a standard for what the offsets in the json response should include: a resource is returned in "data", pagination in "links", errors in "errors", additional data in "meta", and a standard for including other objects aka "compound documents" in "relationships"/"included", so that instead of embedding other resource objects inside the main resource it flattens the graph of objects to eliminate duplicate data in the response (eg. the same user can be both the post author and a comment author).

If you're curious about some of the design decisions or how it compares to HAL, check out the FAQ.

Dredd is a command-line tool for validating API documentation written in API Blueprint format against its actual code. With Dredd you can easily plug your API documentation into a Continous Integration system like Travis CI or Jenkins and have API documentation up-to-date, all the time. Works to test API's written in PHP, Node.js, Ruby and Python. I've been using Swagger for API docs, but I'm looking forward to trying out Dredd + Blueprint in a future project.

This allows numerous providers to be used in addition to the ones provided by Laravel Socialite (and they can be overridden easily). You can also easily create your own new providers.

Flysystem is a filesystem abstraction which allows you to easily swap out a local filesystem for a remote one. Redis and Memcache caching. Emulates directories in systems that support none, like AwsS3. Supports third party plugins. Makes it easy to test your filesystem interactions.

Before you start coding your API, you should model it out; see what kind of endpoints you're going to need and what kind of parameters they're going to accept. RAML is very colorful visual way of modeling an API.

I/O Docs is a live interactive documentation system for RESTful web APIs. Open sourced by the talented API guys at Mashery. I/O Docs is a lot like Swagger except I/O Docs isn't just a spec, it's the interpreter as well and it's written in NodeJS.

Swagger is a popular open source spec to auto-generate very nice looking API documentation with the ability to easily try any API request. You can use the Swagger's own swagger-core framework for node.js, Java or scala, but there's is also support in many other languages because of the strong open source community behind it for other languages like PHP, Ruby, Python, etc. Swagger's biggest open source competitor is Mashery's I/O Docs.

Great video and nettuts article from Phil Sturgeon on how we can use CodeIgniter to create a RESTful API for your existing web applications, and demonstrate how to interact with your own API or other RESTful web-services, such as Facebook and Twitter.

"Maps are often placed on a company website to help customers find their way there. For that, Google Maps is excellent. But wouldn’t it be nice to add your company logo, parking lots, train stations, etc. to the map, to help the customer even more? It is very simple, and in this article I am going to show you how."