Swagger: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
(2 intermediate revisions by the same user not shown) | |||
Line 29: | Line 29: | ||
</pre> |
</pre> |
||
The Swagger specification 2.0 has been donated to the [[Open API Initiative]] for the [[OpenAPI]] 2.0 specification. |
|||
=Editeur Swagger= |
=Editeur Swagger= |
||
http://editor.swagger.io |
http://editor.swagger.io |
||
[[VT2016 Swagger]] |
|||
=Misc= |
|||
* [https://flows.nodered.org/node/node-red-contrib-swagger node-red-contrib-swagger] |
Latest revision as of 12:17, 8 December 2017
http://swagger.io/specification/
What is Swagger? The goal of Swagger™ is to define a standard, language-agnostic interface to REST APIs which allows both humans and computers to discover and understand the capabilities of the service without access to source code, documentation, or through network traffic inspection. When properly defined via Swagger, a consumer can understand and interact with the remote service with a minimal amount of implementation logic. Similar to what interfaces have done for lower-level programming, Swagger removes the guesswork in calling the service.
{ "/pets": { "get": { "description": "Returns all pets from the system that the user has access to", "produces": [ "application/json" ], "responses": { "200": { "description": "A list of pets.", "schema": { "type": "array", "items": { "$ref": "#/definitions/pet" } } } } } } }
The Swagger specification 2.0 has been donated to the Open API Initiative for the OpenAPI 2.0 specification.