Importing from Postman
Vegha imports Postman Collection exports in both the v2 and v2.1 schema versions, as well as Postman environment exports. The import converts the source into native .bru collection files in your workspace.
Exporting from Postman
Section titled “Exporting from Postman”In Postman, export a collection via Collection → Export and choose the v2.1 (recommended) or v2 format. Export an environment via Environments → Export. Both produce JSON files.
Running the import
Section titled “Running the import”Open the Import dialog with Ctrl+I, select the exported JSON file, and choose a destination folder. Collection and environment files are detected automatically.
How Postman concepts map
Section titled “How Postman concepts map”| Postman | Vegha |
|---|---|
| Collection | A .bru collection folder |
| Folder | A subfolder |
| Request | A .bru request file |
| Collection / folder variables | Collection-level variables |
| Environment | An environment in the workspace |
| Auth (Bearer, Basic, API key, etc.) | Native request or collection auth |
| Pre-request / test scripts | Pre-request and post-response scripts |
Headers, query parameters, path variables, and request bodies (raw, form-data, urlencoded) are carried across directly.
Caveats
Section titled “Caveats”Postman scripts use Postman-specific APIs such as pm.*. Vegha imports the script text, but APIs that are specific to Postman may need to be adjusted to Vegha’s scripting model.
Other points to check after import:
- Secrets — environment values marked secret in Postman are imported as plain values. Consider moving sensitive values to secret variables.
- Dynamic variables — Postman’s built-in dynamic variables (e.g.
{{$guid}}) may differ from Vegha’s equivalents. - Disabled items — disabled headers and parameters are preserved in their disabled state.