Skip to main content
Create a root key with the permissions listed on this page under Root Keys in the dashboard sidebar. CLI commands can instead use a session from unkey login with the required permissions. See Permission reference for every permission.
Get every limit of your workspace, with the current value against each limit that has one. Use this before an operation that a limit can reject, for example to see how many custom domains or log drains remain, or how much CPU, memory, and disk a new deployment can still reserve. The request takes no parameters. Each limit has a limit, which is null when unlimited, and a current value when the limit has one. Billable operations count the current calendar month in UTC. The Compute limits are present only when the workspace has a Compute plan. This command takes no request-building flags and does not accept --body.

​
Usage

​
Flags

This command accepts only the shared flags below.

​
Shared flags

These flags control authentication, requests, and output. CLI output and shared flags describes them in full.
​
string
Root key used for the request. Falls back to UNKEY_ROOT_KEY, then stored credentials, including a CLI session. See CLI authentication for the full precedence order.
​
string
default:"https://api.unkey.com"
Base URL of the API. Falls back to UNKEY_API_BASE_URL. You don’t normally need to set it.
​
string
default:"~/.unkey/config.toml"
Path of the TOML config file. Falls back to UNKEY_CONFIG. An explicit --config takes precedence over a stored CLI session. Browser login stores a session, not a root key in this file. See CLI authentication.
​
enum
default:"human"
Use human (default) for name-first summary tables and labeled details, or json for the unchanged full response envelope, including all fields and pagination. Terminal tables use relative timestamps and may shorten display names and descriptions, but never identifiers, slugs, or credentials. Redirected human output keeps complete values and uses RFC3339 UTC timestamps. Falls back to UNKEY_OUTPUT; other values are rejected. --json also selects JSON output. Add --debug to print the request ID to stderr. See Output formats.
​
boolean
Print the successful response’s request ID to stderr, separate from stdout.
​
boolean
Print the full response as JSON. Takes precedence over a valid --output or UNKEY_OUTPUT value.

​
Required permissions

Your root key must have the following permission:
  • unkey:v1:<workspace_id>:limits#read
See Root key permissions.

​
Examples

​
API endpoint

The command calls POST /v2/workspace.getLimits and prints its response. See the endpoint definition for the HTTP contract. The request has no body.
Last modified on October 28, 2026