> ## Documentation Index
> Fetch the complete documentation index at: https://docs.requestly.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Import / Export OpenAPI Spec
> Learn how to import OpenAPI Specification (Swagger) files to instantly generate API collections and environments.
Import your **OpenAPI Specification** files directly into the **Requestly,** and instantly create organized API collections without any manual setup.
This helps you bring your existing API definitions from Swagger, Postman, or your backend documentation straight into Requestly in just a few clicks.
## What You Can Import
The importer supports both **YAML** and **JSON** OpenAPI files. When you upload a spec, Requestly automatically reads the file and creates API collections and requests based on your defined endpoints.
### How It Imports
Open **Requestly Desktop App**. Make sure you’re in the Project where you want to import your API collection.
Click **Import → OpenAPI** and select your `.yaml` or `.json` file.
Requestly will show a preview of what will be imported, including:
* The collections that will be created
* The environments and variables that will be set up
Review the preview and confirm to complete the import.
* Each **path** in your OpenAPI file becomes an individual **request**.
* Requests are grouped under collections named after your API or service.
* Requestly automatically fills in the **method, URL, headers, and body** (if defined in the spec).
* If your spec defines multiple servers (e.g., staging, production), Requestly creates matching environments.
* Each environment includes a `{{base_url}}` variable set to the server URL.
* You can switch environments easily from the environment dropdown.
## What Happens After Import
Once imported, Requestly automatically maps elements from your OpenAPI file to your workspace structure.
| **OpenAPI Element** | **Where It Appears in Requestly** |
| ------------------------------- | ----------------------------------------------------------------------- |
| **Paths** | Individual requests inside the imported collection |
| **Methods (GET, POST, etc.)** | Reflected automatically in each request |
| **Servers (root level)** | Creates environments with a `{{base_url}}` variable for each server URL |
| **Servers (path level)** | Used as **collection variables in parent** |
| **Schemas / Components** | Used internally for request and response structure |
| **Request bodies & parameters** | Automatically mapped to request body and query params |
## Exporting an OpenAPI Spec
Need an OpenAPI definition for sharing or documentation? You can export any API collection as a standard OpenAPI (Swagger) file directly from Requestly.
### How to Export
Hover over the collection you wish to export and click the **three‑dot menu (⋯)**.
Select **Export → OpenAPI** (or **Export as OpenAPI Spec** in some releases). Requestly will generate the spec based on the requests and variables in the collection.
A modal previews the generated file. Click **Download** to save the `.yaml` (or `.json`) spec to your device.
**Tip**: Make sure the collection’s requests and environment variables are up to date, the exported spec reflects the current state of the collection.
