Enter a URL, set some headers, view the response, then share it with others. Perfect for demoing and debugging APIs.
(Full Story: http://www.hurl.it/ )
apiDoc creates a documentation of your embedded API descriptions in your application source code. With an integrated template you generate a standalone usable website with the API documentation. Own templates can be used. Highlight is an API history, with that various API version levels can be compared. So you, or a frontend developer, can retrace what changes in the API since the last version.
(Full Story: http://apidocjs.com/ )
There are in fact two approaches to automation that are used to document REST APIs. One is similar to the tools I mentioned above, where comments are taken from code to generate the documentation. The other involves having the documentation separate from the code, but in a data format (such as JSON) that can be parsed and used to generate the documentation.
(Full Story: Automated Documentation for REST APIs)
General principles for good URI design:
Don’t use query parameters to alter state
Don’t use mixed-case paths if you can help it; lowercase is best
Don’t use implementation-specific extensions in your URIs (.php, .py, .pl, etc.)
Don’t fall into RPC with your URIs
Do limit your URI space as much as possible
Do keep path segments short
Do prefer either /resource or /resource/; create 301 redirects from the one you don’t use
Do use query parameters for sub-selection of a resource; i.e. pagination, search queries
Do move stuff out of the URI that should be in an HTTP header or a body
(Full Story: How to create REST URLs without verbs? – Stack Overflow)
Swagger is a specification and complete framework implementation for describing, producing, consuming, and visualizing RESTful web services. The overarching goal of Swagger is to enable client and documentation systems to update at the same pace as the server. The documentation of methods, parameters and models are tightly integrated into the server code, allowing APIs to always stay in sync. With Swagger, deploying managing, and using powerful APIs has never been easier.
The third “leg” of the web services concept, Universal Description, Discovery and Integration (UDDI), conceptually makes a lot of sense, but in practice, hardly anyone uses it. As a developer, I couldn’t even think of a scenario where UDDI would help me in my particular project. Sure, I could artificially insert UDDI into my use case, but in the scenario where I needed loose coupling, I could get that by simply abstracting my end points and data schema. To the extent I needed run-time and design-time discoverability or visibility into services at various different states of versioning, I could make use of a registry / repository without having to involve UDDI at all. I think UDDI’s time has come and gone, and the market has proven its lack of necessity. Bye, bye UDDI.
(Full Story: How I became a REST ‘convert’)
This REST approach makes interfacing the Arduino to web applications elementary (a jQuery example is included) and most platforms provide basic HTTP out-of-the-box so integrating with desktop and mobile applications is very straightforward.
(Full Story: RESTduino – Arduino hacking for the REST of us)