Skip to main content
The unkey CLI manages Unkey resources from your terminal. Use a resource followed by an action, such as unkey projects list, unkey keys create, or unkey deployments get. Nearly every bearer-authenticated API endpoint has a matching command. Customer portal end-user endpoints use a portal session and aren’t exposed by the CLI. Sign in once, then run a resource command:
The default output is for reading in a terminal. Use --json for scripts and pipes. See Output formats. Delete and remove commands also require confirmation. Review the target in the terminal prompt, or pass --yes explicitly in scripts. See Confirm destructive commands.
The CLI is early and best effort. Commands, flags, and output can change without notice. The HTTP API is versioned and stable, so use the API for scripts that must not break.

Command shape

Commands look like unkey <resource> <action> [flags]. Subresources add a level, such as unkey environments variables list or unkey keys permissions add. unkey --help, unkey projects list --help, and unkey help projects list print usage. unkey version and unkey --version print the installed CLI version. Resource commands share authentication, output, debugging, and raw-body flags. See CLI output and shared flags for their behavior and syntax. The legacy unkey api <group> <command> paths remain available for compatibility. These pages teach the resource paths without changing their existing documentation URLs.

Command groups

Each resource command has its own page in the CLI section of its product.

Compute

, deployments, domains, , gateway policies, and the GitHub App installation are Compute resources.

API Management

Keyspaces, keys, identities, permissions and roles, , and the customer portal are API Management resources. analytics appears in both tables because two of its commands read Compute data and two read API Management data.

Top-level commands

Authentication, deployment, health checks, and the CLI version have their own command forms. unkey version does not manage deployments. To inspect, list, or roll back deployments, use deployments get, deployments list, or deployments rollback.

Next steps

Install the CLI

npm package or GitHub release.

CLI authentication

Where the root key comes from and in which order.

Output and shared flags

Human output, --json, --debug, and request flags.
Last modified on November 2, 2026