Use cases for machine-readable API definition documents include, but are not limited to: interactive documentation; code generation for documentation, clients, and servers; and automation of test cases.
The OpenAPI Specification does not require rewriting existing APIs. It does not require binding any software to a service — the service being described may not even be owned by the creator of its description.
The OpenAPI Specification was developed privately for several years under the name Swagger. Back when it was known as Swagger 2.0, the specification was donated to the OpenAPI Initiative and became an open standard in 2015. Version 3.0.0 was released under the name OpenAPI Specification 3.0.0.
To see our most up-to-date support for the OpenAPI Specification (including our support for OAS v3.1), see our compatibility chart.
The API Reference section of your docs will generate reference guides based on your API definition that include working code examples and the ability to make authenticated API requests directly within the documentation.
Got a Postman Collection? We support that too!
You can import the following file types into ReadMe (either JSON or YAML):
Postman Collections v2.0/v2.1
You can add additional Markdown content to each individual file that is imported. These changes will remain even after you re-sync as long as you do not change the
operationId or remove the import.
️Adding Additional Markdown Content
If you add additional Markdown content, be aware that it will be tied to the
operationIdof that specific imported API definition. If the
operationId, or file, is removed, your additional content will also be removed.
Updated 10 days ago