> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.youratlas.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.youratlas.com/_mcp/server.

# Import Actions from an OpenAPI Spec

If your API already has an [OpenAPI](https://www.openapis.org/) (Swagger) spec, you can generate Atlas Actions for every endpoint in one step instead of configuring each one by hand.

Each operation in the spec becomes a separate action with its URL, method, parameters, and descriptions pre-filled.

## When to use this

* You have a public or internal OpenAPI 3.x spec.
* You want to expose several endpoints to the agent quickly.
* You want consistent naming and descriptions sourced from your spec.

## How to import

1. Go to **Global Actions**.
2. Click **Create tool > Import from OpenAPI spec**.
3. Choose how to provide the spec:
   * **Spec URL** — Paste an https URL pointing to your `openapi.json` or `openapi.yaml`.
   * **Paste JSON** — Paste the raw OpenAPI JSON.
4. Click **Generate tools**.

Atlas parses the spec and shows a preview of every endpoint it found — method, name, and URL.

## Pick what to import

* Each row is one action. All endpoints are selected by default.
* Click a row to toggle selection.
* Use **Select all** / **Deselect all** to flip everything at once.
* Click **Back** to change the spec without losing your progress.

When you're ready, click **Import N tools**. Successfully imported actions appear on the **Actions Added** tab.

![](/_fern-img/defc7a06eb7e35ac98b508caecbc0ab7334f710614e6c3f5c3fcfc418bccebf3.webp)

## What gets generated

For each endpoint Atlas creates a Custom Action with:

* **Name** — Operation ID from the spec (or a generated name).
* **Description** — Operation summary/description from the spec. The agent uses this to decide when to call it.
* **URL** — Server URL + path.
* **Method** — `GET`, `POST`, etc.
* **Parameters** — Path, query, and body parameters with their types and descriptions.
* **Timeout** — Default `30s`.

## After import

* Review each generated action — descriptions sourced from a spec often need a rewrite to instruct the agent properly. See [parameter descriptions](/docs/atlas-actions/atlas-actions#configuration).
* Add authentication headers or an OAuth method if needed — see [OAuth Credentials](/docs/atlas-actions/o-auth-credentials).
* Attach the actions to a campaign — see [Manage Actions](/docs/atlas-actions/manage-actions).

## Errors and partial imports

If some endpoints fail to import (invalid spec, naming conflicts), Atlas creates the ones that succeeded and shows the failed ones with their reason. You can fix the spec and re-import; existing actions are not overwritten.