Environments & Vaults

Reuse variables across requests, mocks and health checks, and keep secrets sealed behind a passphrase.

BifurcSearch requests, mocks and environments…Ctrl PCommandsCtrl KDevelopment

Acme APIWorkspace

Applications

ServicesHealth bar

Routing

Mappings4Proxy rules3CaptureMail

API

Requests12Mocks5Flows1

Workspace

Environments2Vaults1ConfigAudit log

Settings

main2 unpublished changes on this screenPublish

Forward proxy :8080 runningEngine 0.6.0

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.

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.