Tools
Import from Swagger 2.0
Parse a Swagger 2.0 spec and import the selected operations as tools.
POST
This endpoint mirrors
/import-openapi but targets the older Swagger 2.0 schema. The same two-phase parse-then-commit flow applies.
Phase 1 (no
commit flag) parses the spec and returns candidates with temp_ids. Phase 2 (commit: true) takes selected_temp_ids and writes the chosen tools. Use the /import-openapi endpoint instead for OpenAPI 3.x — passing a 3.x document here will fail with unsupported_version.Path Parameters
The UUID of the server to import into (e.g.
836995ae-1cff-41ec-823e-a4f07ccca3a0). Numeric IDs are also accepted for backwards compatibility.Body Parameters
Where the spec content comes from. One of:
text (use content), url (use url).The raw spec body (JSON or YAML). Required when
source is text. Hard cap of 10 MB.Public URL to fetch the spec from. Required when
source is url. Followed up to 3 redirects, 10 s timeout.When
false (default), parse and return candidates only. When true, persist the candidates listed in selected_temp_ids.Array of
temp_id strings identifying which candidates to create. Required when commit is true.Slug-collision policy. One of:
skip, duplicate.Status for newly created tools. One of:
draft, active.Status Codes
| Code | Meaning |
|---|---|
200 | Spec parsed (phase 1) or commit completed (phase 2). |
400 | Bad spec, empty content, wrong version, or unfetchable URL. |
402 | 14-day trial expired and no active license. |
403 | Current license tier does not allow Swagger import. |
404 | Server not found. |

