Skip to content
Vegha Docs

Collections Overview

Vegha organizes your API work into a simple hierarchy of workspaces, collections, folders, and requests — all stored as plain-text files on your local disk.

Core concepts

Section titled “Core concepts”
ConceptWhat it is
WorkspaceA folder on disk that holds one or more collections and environments.
CollectionA subfolder of the workspace that groups related requests.
FolderA nested subfolder inside a collection used to organize requests further.
RequestA single .bru file that describes one API call.

Because every level maps directly to a directory or file, there is no proprietary database. You can open the workspace folder in your file explorer, edit it in any text editor, and commit it to version control alongside your application code.

The Collections panel

Section titled “The Collections panel”

The Collections panel lives in the activity rail on the left edge of the window. It shows the tree of collections, folders, and requests in the active workspace. Click any request to open it in a new tab, or expand folders to browse deeper.

Creating and managing items

Section titled “Creating and managing items”

Right-click any node in the Collections panel to act on it:

  • New request — adds a .bru file. You can also press Ctrl+T (⌘+T on macOS).
  • New folder — adds a subfolder for grouping requests.
  • New collection — adds a top-level collection to the workspace.
  • Rename — renames the file or folder on disk.
  • Duplicate — copies a request or folder, including its contents.
  • Delete — removes the file or folder from disk.

Renaming, moving, and deleting items in Vegha directly changes the underlying files, so the panel always reflects what is actually on disk.

Importing existing work

Section titled “Importing existing work”

If you already have API definitions elsewhere, you can import them rather than starting from scratch. Vegha imports Bruno .bru, Postman v2/v2.1, Insomnia v4/v5, OpenAPI 3.x / Swagger 2.0, and WSDL documents. See the importer documentation for details on each format.

Next steps

Section titled “Next steps”