Environment Variables

Manage configurations across different environments

Overview

Environment variables allow you to store values that can be reused across multiple requests. Switch between different environments (Dev, Staging, Production) without changing your requests!

Environment Manager + New Environment Environments Development 7 variables Active Staging 7 variables Production 7 variables Testing 5 variables Development Variables Edit Delete VARIABLE VALUE TYPE baseUrl https://dev-api.example.com text apiKey dev_k3y_abc123xyz secret timeout 5000 text userId test-user-001 text debugMode true text maxRetries 3 text version v2.1.0 text

Creating Environments

Open Environment Manager

Click "Environments" in the header or sidebar.

Click "+ New Environment"

Create a new environment.

Name Your Environment

Development
Staging  
Production
Testing
Create New Environment × Environment Name * Development Description (Optional) Development environment for testing i You can add variables after creating the environment, or start with an empty environment and add them later. Cancel Create

Add Variables

Define key-value pairs:

baseUrl = https://dev-api.example.com
apiKey = dev_12345
timeout = 5000
Development Environment - Variables + Add Variable VARIABLE NAME INITIAL VALUE TYPE ACTION baseUrl https://dev-api.example.com text × timeout 5000 text × a p i K e y d e v _ k 3 y _ a b c 1 2 3 secret ✓ ✓ Variable "apiKey" added successfully! i Tip: Use {{apiKey}} in your requests to reference this variable Secret variables are encrypted and not visible in exports

Using Variables

Reference variables with double curly braces:

In URL

{{baseUrl}}/api/users
{{baseUrl}}/api/products/{{productId}}

In Headers

Authorization: Bearer {{apiKey}}
X-API-Key: {{apiKey}}
X-Request-ID: {{$guid}}

In Body

{
  "api_key": "{{apiKey}}",
  "timeout": {{timeout}},
  "base_url": "{{baseUrl}}"
}
Request Man Environment: Development Request GET {{ baseUrl }} /api/users/{{ userId }} Variable value: https://dev-api.example.com Send Headers Authorization Bearer {{ apiKey }} X-Request-ID {{ $guid }} Body JSON { "api_key" : "{{ apiKey }}" , "timeout" : {{ timeout }}, "base_url" : "{{ baseUrl }}" , "user_id" : "{{ userId }}" , "debug" : {{ debugMode }} } All variables are resolved from "Development" environment ✓ apiKey = dev_k3y_abc123xyz ✓ timeout = 5000 ✓ baseUrl = https://dev-api.example.com ✓ userId = test-user-001 ✓ debugMode = true

Switching Environments

Use the environment dropdown in the header to switch between environments instantly!

Request Man Environment: Development Development Staging Production Testing Environment: Staging Request URL GET https://dev-api.example.com/api/users https://staging-api.example.com/api/users Headers Authorization: Bearer dev_k3y_abc123xyz staging_k3y_xyz789abc Active Environment Variables • baseUrl = https://dev-api.example.com • apiKey = dev_k3y_abc123xyz • timeout = 5000 • baseUrl = https://staging-api.example.com • apiKey = staging_k3y_xyz789abc • timeout = 3000 ✓ Environment Switched! All variables updated to "Staging" environment ✨ One-Click Environment Switch Benefits ✓ No manual URL editing needed ✓ All variables updated automatically ✓ Consistent across all requests ✓ Switch between Dev, Staging, Production instantly ✓ Prevent errors from wrong environment ✓ Team collaboration with shared environments
One Click Switch: Change from Development to Production without editing any requests!

Variable Types

Type Scope Priority
Environment All requests using that environment Highest
Collection All requests in collection Medium
Global All requests in workspace Lowest

Best Practices

1. Descriptive Names

Use clear environment names: "Production" not "Env1"

2. Keep Secrets Local

Don't share environments with sensitive data

3. Consistent Variables

Use same variable names across environments

4. Document Variables

Add descriptions to complex variables