Environments

Environments let you define reusable variables per project. Switch between development, staging, and production with one click — same flow, different config.

Creating an environment

In the API flow toolbar, click the environment dropdown (shows “No Environment” by default)
Type a name like “Development” and click +
Click the gear icon next to the environment to add variables

Adding variables

Each environment has key-value pairs:

Key	Value
`baseUrl`	`https://api.staging.example.com`
`apiKey`	`sk_test_abc123`
`testEmail`	`test@staging.example.com`

Secret variables

Toggle a variable as secret to mask its value:

Always shows •••••• in the UI
Masked in shared result links
Variables with key, token, secret, password in the name are flagged automatically

Using variables

Reference environment variables in any field with {{variableName}}:

URL:    {{baseUrl}}/users
Header: Authorization: Bearer {{apiKey}}
Body:   {"email": "{{testEmail}}"}

Switching environments

Select a different environment from the dropdown before running your flow. The same flow runs against different servers — no changes needed. Example:

Environment	baseUrl	apiKey
Development	`http://localhost:3000`	`dev_key_123`
Staging	`https://api.staging.com`	`stg_key_456`
Production	`https://api.prod.com`	`prod_key_789`

Be careful running flows against production. Consider using a dedicated test account.

Documentation Index

​Environments

​Creating an environment

​Adding variables

​Secret variables

​Using variables

​Switching environments

Environments

Creating an environment

Adding variables

Secret variables

Using variables

Switching environments