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.
Query key verification data with SQL. Use the key_verifications_v1 table, or the rolled-up key_verifications_per_minute_v1, key_verifications_per_hour_v1, key_verifications_per_day_v1, and key_verifications_per_month_v1. The query must be one SELECT with a FROM, using only allowed functions and documented columns. The rules and their error codes are on err:user:bad_request:invalid_analytics_query. Responses over 4 MiB fail with err:user:unprocessable_entity:query_memory_limit_exceeded. Query time and result rows are limited too. Calls POST /v2/analytics.getVerifications. See key_verifications tables, Analytics restrictions and quotas, and Analytics troubleshooting.

Usage

Flags

string
required
The SQL SELECT to run.

Shared flags

Every resource command takes these. See CLI output and shared flags.
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 single-response trees, or json for the unchanged full response envelope, including all fields and pagination. Trees wrap long values without truncation. 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.
string
Send this JSON as the whole request body instead of using the command’s flags. You can’t combine it with them.

Required permissions

api.*.read_analytics, or api.<apiId>.read_analytics for one or more APIs, which limits results to those keyspaces. See Root key permissions.

Examples

Outcomes in the last day
Or send the whole request as JSON:
Raw body
Last modified on October 28, 2026