Set environment variables
Create or update environment variables for an environment in a single atomic request.
By default this is an upsert: each variable in the payload is created if new or fully overwritten if the key already exists, and any variable not in the payload is left untouched. This lets you change one variable without re-sending the others, which matters for write-only secrets you can no longer read back.
Set prune: true to make it a full replace instead: after upserting, every
variable not in the payload is deleted. Sending prune: true with an empty
variables list resets the environment by deleting every variable.
Each variable is written exactly as sent, never merged, so omitted optional
fields fall back to their defaults rather than the previous value. Values are
always encrypted at rest. Set kind: recoverable to allow a value to be read
back; it defaults to writeonly, which can never be read back through the API.
Required Permissions
Your root key must have one of the following permissions:
environment.*.set_environment_variables(for any environment)environment.<environment_id>.set_environment_variables(for a specific environment)
Authorizations
Unkey uses bearer tokens for authentication. Public integrations use root keys, while the dashboard proxy uses short-lived JWTs. To authenticate, include the token in the Authorization header of each request:
Root keys have specific permissions attached to them, controlling what operations they can perform. Legacy permissions use tuple strings like api.*.create_key; resource permissions use Unkey Resource Names plus actions, like unkey:v1:ws_123:keyspaces/*#create_key.
Security best practices:
- Keep root keys secure and never expose them in client-side code
- Use different root keys for different environments
- Rotate keys periodically, especially after team member departures
- Create keys with minimal necessary permissions following least privilege principle
- Monitor key usage with audit logs.
Body
Identifies a resource by either its unique ID or its slug. Accepts a prefixed ID (such as 'proj_' or 'app_') or a slug.
3 - 255^[a-zA-Z0-9_-]+$"proj_1234abcd"
Identifies a resource by either its unique ID or its slug. Accepts a prefixed ID (such as 'proj_' or 'app_') or a slug.
3 - 255^[a-zA-Z0-9_-]+$"proj_1234abcd"
Identifies a resource by either its unique ID or its slug. Accepts a prefixed ID (such as 'proj_' or 'app_') or a slug.
3 - 255^[a-zA-Z0-9_-]+$"proj_1234abcd"
The variables to upsert. Each entry is created if its key is new or fully
overwritten if the key already exists. Existing variables whose keys are
not in this list are left untouched, unless prune is true.
Each entry is written exactly as sent, never merged with the current
state. Only value is required; omitted optional fields (kind,
description) fall back to their defaults rather than any previous value,
so overwriting a variable without a description clears it.
Each key may appear at most once; a duplicate key is rejected with a 400. The whole operation is atomic: if any part fails the environment is left unchanged. All values are encrypted at rest. Limited to 50 variables per request.
50Optional. Defaults to false. When false, the variables above are upserted
and any existing variable not in the list is kept. When true, this becomes
a full replace: after upserting, every variable not in the list is deleted.
Combined with an empty variables list, prune: true resets the entire
environment by deleting every variable.
Response
Successfully set the environment variables.
Metadata object included in every API response. This provides context about the request and is essential for debugging, audit trails, and support inquiries. The requestId is particularly important when troubleshooting issues with the Unkey support team.
Empty response object by design. A successful response indicates this operation was successfully executed.