Environments

Environments store reusable variables for requests. Use them for values that change between local, staging, and production APIs, such as base URLs, user IDs, and organization IDs.

WARNING

Environment variables are stored as plain text in your Markdown Vault. Do not store real passwords, API tokens, private keys, or other secrets in HTTP environments if your vault is synced, shared, or committed to Git.

Variables

Use variables with double braces:

{{apiUrl}}/v1/users/{{userId}}/sessions

The URL field keeps variables visible while you edit. Preview and request execution resolve variables from the active environment.

Variables can be used in:

• URL
• params
• headers
• body
• auth fields

Active Environment

Use the Environments panel below folders to choose the active environment.

Select No environment when you want requests to keep variables unresolved. This is useful when you are editing templates or copying a request without applying local values.

Managing Environments

Open Manage from the Environments panel to create environments and edit variables.

Each environment has:

• a name
• a key-value table of variables

The active environment is stored as part of the HTTP space state.