Support HATEOAS (e.g., support links in responses to navigate to other resources)
Our API uses http links to navigate between resources. You can start from a single defined resource and then navigate down to the other resources in the API and their related resources.
Chrome's POSTMAN does it fairly well, but it would be great to embed such a feature in an API blueprint and I haven't seen support for this in any of the other API tools.
The “Resource Blueprint” https://github.com/apiaryio/api-blueprint/tree/resource-blueprint concept has been introduced.
While there is no implementation of it yet, we plan to move into that direction.
HATEOAS is also essencial for us. Without HATEOAS, it'sa deal break.
Olivier Pessin commented
This is an essential one for me (to go the right way in the REST direction)..
- media types need to be focused (structure described.. similar to what a XSD provides.. also, a such a machine readable description seems important to have)
- and typed links (rel, type) to navigate.
This looks like the site map of a website (What are nice ways to represent site maps ? ..).
Adam Rich commented
It should be like VMWare does it: http://www.vmware.com/support/developer/vas/rest-api-1.1.1.RELEASE/index.html#gemfire/