Importing from OpenAPI

Vegha imports OpenAPI 3.x and Swagger 2.0 specifications, generating a native .bru collection with one request per operation. Imported OpenAPI collections can also be re-synced when the upstream spec changes.

Running the import

Open the Import dialog with Ctrl+I and select the spec file (JSON or YAML). Choose a destination folder, and Vegha generates the collection.

How the spec maps

OpenAPI / Swagger	Vegha
Operation (path + method)	A .bru request
Tags	Folders grouping the requests
servers (or host + basePath)	A base URL variable
Path / query / header parameters	Request parameters
Request body schema	A sample request body
securitySchemes / security	Native request or collection auth

Each operation becomes an executable request with its path, method, parameters, and a sample body derived from the schema. The first server entry is used as the base URL variable, so you can switch hosts in one place.

Sync and drift detection

OpenAPI is the one importer that supports ongoing sync. When the API’s spec changes, re-import the updated file into the same destination. Instead of silently overwriting, Vegha runs drift detection and shows what changed:

• Operations that were added — new requests to generate
• Operations that were removed — requests no longer in the spec
• Operations that were modified — changed parameters, bodies, or auth

Review the drift summary, then apply it to regenerate the affected requests while leaving your other edits intact.

Keep collections current

Re-import the spec whenever the API publishes a new version. Drift detection turns a full re-import into a reviewable changelist.

Caution

Drift detection reports changes at the operation level. Manual edits to a request that an updated spec also changes may be overwritten when you apply the drift — review the summary before applying.