You can add vault secrets directly to your Postman Local Vault or from HTTP requests. Specify the key name that’s used to reference the vault secret, the value, and allowed domains. Then you can reference vault secrets in your Postman team. You can edit vault secrets from your local vault or from requests that reference them.
Add sensitive data, such as API keys and passwords, to Postman Vault and reuse them in Postman. Vault secrets are encrypted using Advanced Encryption Standard (AES) with a 256-bit key length.
To add secrets to your Postman Vault, do the following:
Open your Postman Vault.
Enter the following values in an empty row:
Key - The name of the vault secret. Use the name to reference the secret.
Value - The value used when sending requests in your local instance of Postman. It’s never synced to your account or shared with your team.
Allowed domains - The comma-separated list of domains and subdomains you’re allowed to send requests to with the vault secret. This enables you to prevent unintentional disclosure of sensitive data in your vault secret. By default, you can include vault secrets in requests to any domain and subdomain.
If you specify allowed domains or subdomains for a vault secret, you can only reference it at the request level.
To allow sending requests to any subdomain of an allowed domain, use * to represent any subdomain. For example, add *.example.com to allow sending requests to any subdomain of example.com.
You can also take the following actions to add vault secrets to Postman Vault:
You can select data from the URL builder, Params tab, Authorization tab, or Headers tab and set the data as a vault secret. You can also enter a value with sensitive data in the Authorization tab and add it directly to your Postman Vault as a vault secret.
To select data and set it as a vault secret, do the following:
To add sensitive data as a vault secret from the Authorization tab, do the following:
Try a vault secret in a request before adding it to Postman Vault. You can also create placeholder vault secrets to share with your API consumers. Your consumers can use placeholder vault secrets to add their own sensitive data. The value you enter is stored locally and only available in the request it’s set in.
To try a vault secret locally, do the following:
Values for vault secrets you try are stored locally in a request until you close its tab or sign out of Postman. When you open the request again, the vault secret’s value is empty.
Once you try a vault secret in a request, you can then add it to Postman Vault.
To add a vault secret from a reference, do the following:
{{vault:secret-name}}).If you would like to store the value as a variable instead, remove the vault: prefix, then follow the instructions to add the variable to a scope.
You can reference vault secrets in your HTTP collections and requests from the URL builder, the Params tab, the Authorization tab, the Headers tab, and the Body tab. Learn more about Postman feature availability with vault secrets.
Put the vault secret inside double curly braces ({{ }}) and append the prefix vault: to the vault secret’s name, enabling you to reference it throughout your workspaces. For example, to reference a vault secret named “postman-api-key”, use the following syntax:
To learn how to troubleshoot empty or unresolved vault secrets, see Troubleshoot vault secrets.
If you specified an allowed domain for a vault secret and you’re sending a request to the domain, you can select a vault secret from the Authorization tab. Note that you can only add a vault secret this way from the request level. Select an authorization from the Auth type dropdown list, click a field that holds sensitive data, then select a vault secret from the dropdown list. You can click Show to show the vault secret’s value in the dropdown list.
From the variables pane, you can view vault secrets referenced in an HTTP request and available from a Postman element. Click Variables in the workbench to open the variables pane. Review the vault secrets referenced in a request under Variables in request. If the request auth is set to Inherit auth from parent, you can view vault secrets referenced in the Authorization tab of the request’s parent collection or folder. Under All variables, you can view vault secrets that can be referenced and resolved in the Postman element that’s open. For requests that reference a variable or vault secret, click All variables to display all vault secrets a request can access.
Vault secrets stored in your Postman Vault are masked by default when they’re logged to the Postman Console. To edit whether vault secrets are masked in the Postman Console, click Settings, then turn the toggle on or off next to Mask vault secrets from the Settings tab.
If you reference a vault secret as the shared value of a variable, the reference to the secret (for example {{vault:secret-name}}) is synced using the Postman cloud. The reference to the vault secret, not the actual value, is shared with anyone who has access to the workspace. Learn more about shared values.
If you’re using the Postman web app with Safari as your web browser, it deletes vault secrets from your local instance of Postman after seven days of inactivity.
Use a different web browser if you want your vault secrets available for more than seven days without activity in the Postman web app.
Learn about the browser requirements for the Postman web app.
The following Postman features are supported with vault secrets:
The following features aren’t supported with vault secrets:
Edit vault secrets stored in your Postman Vault by updating them and their allowed domains, changing a vault secret’s name, making vault secrets unavailable, or deleting vault secrets. You can also edit the value of vault secrets directly from requests that references it or can access it.
To edit vault secrets, open your Postman Vault. You can take the following actions:
Changes are automatically saved to your Postman Vault.
You can also edit the value of a vault secret from the variables pane or the request builder. Click Variables in the workbench to open the variables pane. You can edit vault secrets referenced in an HTTP request under Variables in request and vault secrets available from a Postman element under All variables. In the variables pane, delete the existing value next to a vault secret, then enter a new value. You can also hover over the reference to the vault secret in the request builder, delete the existing value, then enter a new value.
From the variables pane, you can’t edit the value of a vault secret that’s linked to an external vault.