Environments

Environments let you define named variables and switch between them without editing your requests. A typical setup has a Development environment pointing at localhost and a Production environment pointing at your live API.

Creating an environment

Open the Environments screen from the left toolbar. Click + to add a new environment. Give it a name (e.g. Staging) and a colour — the colour appears as a visual indicator in the header so you always know which environment is active.

Adding variables

Inside an environment, click + to add a variable. Each variable has:

• Key — the name you reference in requests, e.g. baseUrl
• Value — the actual value for this environment, e.g. https://staging.api.example.com
• Secret — mark a variable as secret to mask its value in the UI (it is never sent in bug reports)

Using variables

Reference a variable anywhere in a request using double curly braces:

{{baseUrl}}/users/{{userId}}

Variables resolve at send time from the active environment. Unresolved variables (no match in the active environment) are left as-is and highlighted in the URL bar.

Variables work in:

• URL (including path segments and query parameters)
• Headers (both key and value)
• Request body
• Auth configuration values

Switching environments

Click the environment switcher in the header toolbar and select the environment you want. The change is immediate — no restart or reload needed.

Environment colour indicators

In Settings → Appearance, you can enable two optional visual cues:

• Coloured pill — tints the environment switcher button with the environment's colour
• Tab glow — adds a subtle glow to the active request tab matching the environment colour

These are useful when you work across staging and production simultaneously.

Shared vs local variables

Currently all environment variables are local to your machine. Shared environments (synced across team members) are planned for the Teams tier.