GUI / visual editor for creating and editing OpenApi / Swagger definitions
Switch branches/tags
Nothing to show
Clone or download
Pull request Compare This branch is 12 commits ahead, 227 commits behind Mermade:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


OpenApi-gui is a GUI for creating and editing OpenApi (Swagger) JSON/YAML definitions. In its current form it is most useful as a tool for starting off and editing simple OpenApi definitions.

For the OpenAPI 3.x version, check out the latest branch.

Version 3.x live demo


This project was initially a fork of Daryl Kuhn's IODoctor, which in turn was inspired by IODoctor by Brandon West which was written in Ruby.


How It Works

Select an existing OpenApi definition to upload, or create a new definition and start adding Paths, Operations, and Parameters. When an existing definition is used, it is parsed and forms for editing each Path, Operation and Parameter will be created.

Click an item from the menu on the left to begin editing. View the JSON/YAML output at any time by selecting one of the "Export" tabs. When finished, download the output to save it locally or copy it your clipboard. OpenApi-gui only stores one definition at a time, and this is in your browser's local-storage. Make sure you save your JSON/YAML output locally.

Before performing a destructive action, OpenApi-Gui saves the current state of the definition. At all other times you must remember to select Save manually.


OpenApi-gui runs entirely client-side using a number of Javascript frameworks including jQuery, Twitter Bootstrap, and Vue.JS.

To get the app up and running just browse to the page, deploy to Heroku using the button below, or clone the repo and load index.html into a browser / host it yourself - couldn't be simpler.

You only need to npm install the Node.js modules if you wish to use the Arapaho embedded web server, otherwise they are only there for Heroku deploys.



  • OpenApi-gui will de-reference shared parameters. For publication, you may wish to pass your OpenApi definition through a tool such as OpenApi-optimise.
  • The definition must be self-contained with no external $refs.
  • Editing a response / example / body schema will dereference it.
  • OpenApi-gui will not always preserve vendor-extensions.
  • OpenApi-gui will not preserve comments from definitions imported in YAML format.


  • Add validation on form fields
  • Consumes/Produces and security at operation level
  • Handle circular $refs in responses / examples / body schemas