OpenAPI (Swagger) Document Type (Framework)
OpenAPI specification, previously known as Swagger specification, is a specification that defines a standard, programming language-agnostic interface description for HTTP APIs, which allows both humans and computers to discover and understand the capabilities of a service without requiring access to source code, additional documentation, or inspection of network traffic. Use cases for machine-readable API definition documents include interactive documentation, code generation for documentation, automation of test cases, and more. OpenAPI documents describe an API's services and are represented in either YAML or JSON format.
- OpenAPI 2.0
- OpenAPI 3.0
- OpenAPI 3.1
Editing OpenAPI Documents
You can edit OpenAPI files in Text mode and you have access to all the usual text editing actions.
Validation and Content Completion
Validation and content completion is supported in Oxygen XML Developer for OpenAPI documents (version 2.0, 3.0, 3.1). The validation and content completion in OpenAPI documents are driven by schemas according to the OpenAPI version in the document. Each of the three frameworks (OpenAPI 2.0, OpenAPI 3.0, and OpenAPI 3.1) have a unique schema specified for content completion and validation. When opening an OpenAPI document (in JSON or YAML format), Oxygen XML Developer automatically associates the corresponding schema based on the OpenAPI version of the document.
Resources
- Oxygen XML Developer includes a tool for generating documentation for OpenAPI components in HTML format: Generating OpenAPI Documentation.
- Oxygen XML Developer includes a testing tool for OpenAPI files: OpenAPI Tester.
- For more details about the OpenAPI Specification, along with example documents, go to https://spec.openapis.org/oas/latest.html.
- Video: OpenAPI Document Editing in Oxygen XML Editor
- Webinar: OpenAPI Editing, Testing, and Documenting
- Webinar: OpenAPI/AsyncAPI Support in Oxygen