OpenAPI Form Editor

The Form Editor provides a structured interface for creating and editing OpenAPI specifications without requiring deep OpenAPI syntax knowledge. AsyncAPI uses Code, Diff, Governance and Preview. GraphQL uses Code, Diff and Preview. Neither format has a Form tab.

It presents form fields for each part of an API, organized by endpoint, so technical and non-technical team members can work on the same spec.

The Form Editor consists of two main parts:

• Left Side: The file tree on top and, below it, the navigation panel of the selected OpenAPI spec: Info, Tags, Servers, Security, Paths, Webhooks and components. From here, you can add paths, webhooks, parameters, and other reusable components.
• Right Side: Form-based operation panel that displays editable fields based on which part of the OpenAPI spec you select.

JSON Schema Specs

A repository can hold stand-alone JSON Schema files. In the add file dialog, choose the JSON Schema Spec card, then create or import a schema. JSON Schema specs have their own form editor and viewer, and they have no Governance tab, because browser governance applies to OpenAPI and AsyncAPI documents.

Other Files

A stand-alone component file, such as a file holding one request body or response, or any other JSON or YAML file, can’t be edited in the Form tab. It is shown read-only there with its resolved content. Use the Code tab to edit it.