All features
Feature
Environments & Vaults (beta)
Reuse variables across requests, mocks and health checks, and keep secrets sealed behind a passphrase.
How it works
Define variables once per environment and use them in requests, mocks, health checks and every protocol tab; built-in randomizers generate IDs, emails or timestamps for test data. Secrets go in a vault that is encrypted with a passphrase only you know, and are referenced like any other variable. From the terminal, a vault can hand its secrets to a command as environment variables. **Beta:** Vaults are in beta: unstable and still under development, and how they store data may change. Local vaults stay on this device only. Keep your own copy of any secret you store.
When to use it
- Switch the same requests between local, staging and production.
- Generate fresh IDs, emails and timestamps for test data.
- Keep API keys out of saved requests, captured traffic and exports.
