Importing OpenAPI / Swagger

Why use OpenAPI import?

If your product is built for developers or your product has an API, you need great product documentation — otherwise, you can't cut through to developers.

Once you import your OpenAPI file, Archbee will read it and convert it to a beautiful UI and make it ready to be:

1. shared publicly(on a custom domain)
2. internally with your colleagues and teams.

Once imported, you can sync, update and test your OpenAPI. See more details in the sections below.

Rules and default settings

Supported OpenAPI versions:

Archbee currently supports the following OpenAPI versions to be imported:

1. Version 2.0 and 2.0.XX
2. Version 3.0 and 3.0.XX
3. Version 3.1 and 3.1.XX

Supported Auth methods

Archbee currently supports the following Auth methods:

1. Basic Authentication
2. API Keys
3. Bearer Authentication

If you import OpenAPI files with other Auth methods, they will import correctly, and the Auth method will be ignored.

This means that you will get the whole Archbee OpenAPI experience, except the Try It! feature, if your endpoint requires an Auth that is not in the list above.

Others

1. If you define a "default" parameters in your OpenAPI and you give it a value, the code sample and the parameter box will be automatically pre-populated with that value. This makes it easy for your users or customers to test your API with Try It! withoud having to update all the required parameters.
2. If you define an "example" parameter in your OpenAPI, the example value will be displayed on the left side just below the API parameter. This makes it easy for your users to identify what type of input is needed for that specific parameter.

How does it work?

Here's a video of how it works