
When you first open the editor it shows the Swagger Petstore API, which is a sample API used by the Swagger project to show off the extensive capabilities of the OpenAPI specification. Swagger Editor is also open source and available on GitHub, so if you prefer you can run it offline on your local computer or on your own server. The downside is that there is no cloud storage, so you always need to save your work locally. The application runs in the browser and is completely built on client-side Javascript, so you do not have to trust their server with your data. Swagger Editor is freely available online at. In this article, we would like to showcase one of tools for the API design stage, the Swagger Editor, and be your step-by-step guide for creating your first OpenAPI definition. But the right tooling can make your job a lot easier. OpenAPI definitions are simple JSON or YAML files that you can create and edit with any text editor. If you are convinced now that OpenAPI is something you want to get your hands dirty with, you have come to the right place! We’ve already covered 5 reasons you should use OpenAPI/Swagger for your APIs on this blog. This enables them to automate various processes around the API lifecycle. OpenAPI definitions, formerly known as Swagger files, allow developers to specify the operations and metadata of their APIs in machine-readable form.
