Importing Overview

Vegha can import collections and environments from a range of common API tooling formats. Every import converts the source into native, plain-text .bru collection files in your workspace — there is no proprietary database, so the result diffs, merges, and lives in git like any other code.

Opening the Import dialog

Choose File → Import or press Ctrl+I to open the Import dialog. Select a source file, pick a destination folder inside your workspace, and Vegha generates the equivalent .bru files.

Supported source formats

Format	Versions	Imports
Bruno	.bru	Collections
Postman	v2, v2.1	Collections and environments
Insomnia	v4, v5	Workspaces, requests, environments
OpenAPI	3.x	Collections (one request per operation)
Swagger	2.0	Collections (one request per operation)
WSDL	1.1	Executable SOAP collections

Choosing a destination

The Import dialog asks for a destination folder within your current workspace. Imported requests are written there as .bru files, preserving the source’s folder structure where one exists. You can import into a new subfolder to keep an imported collection isolated from existing work.

Import is a conversion

After import, the generated .bru files are fully native. The original export file is no longer needed and is not referenced by Vegha.

Importing from the CLI

The same conversion is available headless. Use vegha import to convert a source file into .bru files as part of a script or CI step. See vegha import for usage.

Format-specific guides

• Postman — v2 and v2.1 collections and environments
• Insomnia — v4 and v5 exports
• OpenAPI / Swagger — including sync and drift detection
• WSDL — executable SOAP collections

Tip

OpenAPI imports can be re-run later to detect drift when the upstream spec changes. See the OpenAPI guide for the sync workflow.