Tokens
Create and manage API tokens for programmatic access.
API tokens allow scripts and CI/CD pipelines to authenticate without using your personal credentials. Tokens are scoped to a project and can optionally be restricted to a single environment.
All token commands require a workspace and project.
list
List all tokens for the active project.
edge token list
edge token list --workspace acme-corp --project payments --jsonExample output
SLUG NAME CREATED AT
tok-01j2k3... CI token 2025-05-01T10:00:00Z
tok-01j2k2... Deploy bot 2025-04-15T08:30:00Zcreate
Create a new token. The token value is shown once at creation time — save it immediately.
edge token create <name> [--env <slug>]Flags
| Flag | Description |
|---|---|
--env | Environment slug. Restricts the token to a single environment. If omitted, the token has access to all environments in the project. |
Example
# Project-scoped token
edge token create "CI token"
# Environment-scoped token
edge token create "Prod deploy bot" --env productionExample output
✓ Created token CI token
Token: tok_live_01j2k3...
! Save this token — it will not be shown againThe token value is only returned once. If you lose it, delete the token and create a new one.
Using the token
Pass the token via the CLOUD_TOKEN environment variable or the --token flag:
CLOUD_TOKEN=tok_live_01j2k3... edge deploy up api \
--workspace acme-corp --project payments --env productiondelete
Delete a token by its slug.
edge token delete <token-slug>edge token delete tok-01j2k3...
