Set application environment variables in Coolify via the API
domain: coolify.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create a bearer API token with write permission
For a single variable, POST /api/v1/applications/{uuid}/envs or PATCH .../envs/{env_uuid} to create/update one entry
For many variables at once, PATCH /api/v1/applications/{uuid}/envs/bulk with a JSON body: {"data": [{"key":..., "value":..., "is_preview":..., "is_literal":..., "is_multiline":..., "is_shown_once":...}]}
Redeploy the application (or rely on instant_deploy on next deploy) for changes to take effect in the running container
Use DELETE .../envs/{env_uuid} to remove a variable
Known gotchas
The bulk endpoint upserts by key — omitting an existing key does not delete it, you must call the delete endpoint explicitly
is_shown_once controls whether the value is revealed only once in the UI; it doesn't affect API visibility, which is governed by the token's read:sensitive permission
Responses include both value and real_value fields — only tokens with read:sensitive receive the unredacted real_value
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?