HTTP & REST Requests
HTTP is the default request type in Vegha. An HTTP request has a method, a URL, and a set of tabs for everything else you need to configure.
Methods
Section titled “Methods”Choose the verb from the method selector at the start of the URL bar:
| Method | Typical use |
|---|---|
GET | Retrieve a resource |
POST | Create a resource |
PUT | Replace a resource |
PATCH | Partially update a resource |
DELETE | Remove a resource |
HEAD | Retrieve headers only |
OPTIONS | Discover supported operations |
The URL bar
Section titled “The URL bar”Type the endpoint into the URL bar. You can use {{variable}} interpolation anywhere in the URL — for example {{baseUrl}}/users/{{userId}}. Press Ctrl+Enter (⌘+Enter on macOS) to send the request, and Ctrl+S to save it.
Request tabs
Section titled “Request tabs”Each request has tabs for Params, Authorization, Headers, Body, Pre-request, Tests, and Docs.
Params
Section titled “Params”The Params tab lists query string parameters as key/value pairs. Parameters you add here are appended to the URL; editing the query string in the URL bar keeps the table in sync.
Headers
Section titled “Headers”The Headers tab holds request headers as key/value pairs. Headers inherited from the folder or collection also apply — see Collection settings for precedence.
The Body tab is where you set the request payload. Available body types:
| Type | Description |
|---|---|
| JSON | Structured JSON with syntax highlighting |
| form-url-encoded | application/x-www-form-urlencoded key/value pairs |
| multipart form-data | Key/value pairs plus file uploads |
| raw | Plain raw text |
| XML | XML document with syntax highlighting |
For multipart form-data, you can attach files alongside text fields, which makes it suitable for file-upload endpoints.
Authorization
Section titled “Authorization”Select an auth method on the Authorization tab. Vegha supports API Key, Bearer, Basic, Digest, NTLM, OAuth1, OAuth2, AWS SigV4, WSSE, and mTLS. See Authentication.
Pre-request and Tests
Section titled “Pre-request and Tests”The Pre-request tab runs sandboxed JavaScript before the request is sent; the Tests tab runs assertions after the response arrives. See Scripting.
Retry and timeout
Section titled “Retry and timeout”Each request can define its own retry count and timeout. If a request fails or exceeds the timeout, Vegha retries it up to the configured number of attempts before reporting a failure.
Cookies and redirects
Section titled “Cookies and redirects”Vegha keeps a cookie jar, so cookies set by a response are stored and sent automatically on subsequent requests to the same host. Redirects are followed automatically. The connection timeline and full response details are covered in Responses.
Generating client code
Section titled “Generating client code”You can export any request as ready-to-run code — curl, Node fetch, Python requests, Go, C#, or Java — to share or embed elsewhere.