lizard keys
Create, list, and delete API keys. Alias: lizard apikey.
Usage
lizard keys create <name> [flags]
lizard keys list
lizard keys rm <name-or-id> [flags]API keys start with liz_. Use one wherever you can’t log in through a browser:
LIZARD_TOKENorLIZARD_API_KEYfor the CLI in CIlizard login --token liz_…on a machineLIZARD_API_KEYfor the Lizard SDKlizard sandbox create --with-token liz_…to uselizardinside a sandbox
Subcommands
lizard keys create <name>
Create a key and print it once. Copy it then; Lizard does not show it again. A key without a scope has full access to every workspace and project you can reach. Scope it with these flags, each repeatable:
| Flag | Description |
|---|---|
-p, --project <id> | Limit the key to this project (name, slug, or ID) |
-w, --workspace <id> | Limit the key to this workspace (name, slug, or ID) |
A scoped key can’t see account billing or settings.
lizard keys list
List your keys with a short preview, scope, creation time, and last use (alias ls).
lizard keys rm <name-or-id>
Delete a key (alias delete). If two keys share a name, delete by ID.
| Flag | Description |
|---|---|
-y, --yes | Skip confirmation |
Examples
Create a key for CI
lizard keys create github-actions --project my-projectStore the printed key as a CI secret named LIZARD_TOKEN.
Create a key for a sandbox
lizard keys create sandbox-agent --workspace my-team
lizard sandbox create --with-token liz_xxxDelete a key
lizard keys rm github-actions --yesSee also
- lizard login — log in with a key on a machine
- JSON & Automation — using the CLI from CI
- lizard sandbox —
--with-tokeninstalls a key in a sandbox
Updated