Quick Start
This walkthrough takes you from a fresh install to a saved, tested request. It should take about five minutes.
1. Create a workspace
Section titled “1. Create a workspace”A workspace is just a folder on disk. When Vegha opens for the first time, choose
New Workspace and pick (or create) an empty folder — for example ~/api-tests.
Everything you do lives inside that folder as plain-text files, so you can put it under git whenever you like. See Collections overview.
2. Send your first request
Section titled “2. Send your first request”-
Press
Ctrl + T(⌘ Ton macOS) to open a new request tab. -
Leave the method as GET and enter a URL:
https://httpbin.org/get -
Press
Ctrl + Enter(⌘ ↩) to send.
The response panel shows the status line (200 OK), the timing, the response size, and
the body with syntax highlighting. The connection timeline breaks the request down
into DNS, connect, TLS, and time-to-first-byte.
3. Save it to a collection
Section titled “3. Save it to a collection”- Press
Ctrl + S(⌘ S). - Vegha asks for a collection. Create one — call it
Demo— and give the request a name likeGet example.
Vegha writes a Demo folder into your workspace containing a .bru file for the
request. Open it in any text editor and you’ll see a readable, diffable representation of
exactly what you configured.
4. Add a variable
Section titled “4. Add a variable”Hard-coded URLs don’t scale. Let’s parameterize the host:
-
Open the Environments panel from the activity rail.
-
Create an environment called
defaultwith a variable:Name Value baseUrlhttps://httpbin.org -
Back in your request, change the URL to:
{{baseUrl}}/get -
Make sure
defaultis selected in the environment picker, then send again.
{{baseUrl}} is resolved at send time. See
Variables & Environments.
5. Write a test
Section titled “5. Write a test”Open the request’s Tests tab and add a post-response assertion:
test('responds 200', () => { expect(res.status).toBe(200);});
test('echoes the host', () => { expect(res.body.headers.Host).toBe('httpbin.org');});Send the request again. The Test Results view reports both assertions passing. Tests run in a sandboxed JS engine — see Scripting & Tests.
6. Run the whole collection
Section titled “6. Run the whole collection”You can run the entire Demo collection at once from the UI — or from your terminal with
the bundled CLI:
vegha run ./Demo --env defaultThe CLI shares the exact same engine as the desktop app. See the CLI overview.
Where to go next
Section titled “Where to go next”- Sending HTTP & REST requests — methods, params, bodies
- Authentication — OAuth2, API keys, mTLS and more
- Importing — bring in a Postman or OpenAPI collection
- Git integration — put your workspace under version control