Environments & Variables

Manage variables across protocols and reuse them in your requests using the {{key}} syntax.

Architecture

Variables are resolved in a two-level hierarchy:

  1. Collection Variables (protocol-scoped) — defined per protocol (REST, Realtime, Service Bus, GraphQL) within each collection
  2. Global Environments — shared across all collections and protocols (fallback)

Collection variables take precedence over global environments. If a key exists in both, the collection value is used.

Collection Variables (per protocol)

Each collection can have its own set of variables organized by protocol. When you switch protocols, the Variables tab shows the corresponding group.

Collection "Ismael Tester"
  ├── REST       → col.variables.rest
  ├── Realtime   → col.variables.ws
  ├── Service Bus → col.variables.servicebus
  └── GraphQL    → col.variables.graphql

To edit collection variables, select the protocol first (REST / Realtime / Service Bus), then open the Variables tab in the request panel:

  • REST — [Params] [Headers] [Auth] [Body] [Pre-request] [Tests] [Variables]
  • Realtime (WS) — [Headers] [Auth] [Variables]
  • Service Bus — [Overview] [Connection] [Entities] [Messages] [Variables]

Variable rows

Variables are displayed in the same UI as query parameters:

  • [☐] — Enable/disable toggle
  • Key — Variable name (used as {{key}})
  • Value — Variable value
  • [✕] — Delete row

Bulk JSON editor

Click Bulk to switch to a textarea where you can edit all variables as key: value pairs:

host: api.example.com
token: eyJhbGciOiJIUzI1NiIs...
# disabled_param: value

Lines starting with # are disabled. Click Done to apply changes back to the table.

Global Environments

Global environments are shared across all collections and protocols. They act as a fallback when a variable is not found in the collection variables.

Creating an Environment

  1. Open the tab in the sidebar
  2. Click the [+] button to create a new environment
  3. Add variables as key-value pairs
  4. Toggle variables on/off with the checkbox

Using Variables

Variables are resolved in all request fields across all protocols:

  • URL — https://{{host}}/api/users
  • Headers — value fields
  • Body — JSON or text content
  • Query parameters — value fields
  • Authentication — Bearer token, Basic Auth, API Key values
  • Service Bus — connection string, entity path, subscription name
  • WebSocket — URL, headers, auth

Resolution order

resolveVars("{{key}}")
  1. Collection variables (current protocol) → wins
  2. Global environments → fallback

Example

Given a collection "Ismael Tester" with REST variables:

Collection variables (REST):
  host  → api.example.com
  token → abc123

Global environment "DEV":
  company → u4erp

URL: https://{{host}}/{{company}}/users
→ https://api.example.com/u4erp/users

The {{host}} is resolved from collection variables (REST). The {{company}} falls back to the global environment.

Sidebar overview

The sidebar tab shows both global environments and collection variables grouped by protocol. Click on a protocol name to switch to that protocol and view its variables.

On this page