You need a root key with the permissions listed on this page. Create one in the dashboard under Settings > Root Keys, and pass it as
Authorization: Bearer <root key>. See Permission reference for every permission.keys verify-key --permissions. Calls POST /v2/permissions.createPermission. See Roles and permissions.
Usage
Flags
string
required
Display name, 1 to 512 characters.
string
required
Name used when granting and checking the permission. Unique per workspace. Reusing one returns 409
err:unkey:data:permission_already_exists. 1 to 128 characters matching ^[a-zA-Z0-9_:\-\.\*]+$: letters, digits, underscores, colons, hyphens, periods, and asterisks.string
What the permission allows, for the dashboard. Up to 512 characters.
Shared flags
Everyunkey api command takes these. See CLI output and shared flags.
string
Root key used for the request. Falls back to
UNKEY_ROOT_KEY, then to the key stored by unkey auth login.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 config file written by
unkey auth login. Falls back to UNKEY_CONFIG.string
Output format. Falls back to
UNKEY_OUTPUT. json prints the full response. Any other value prints the request ID and data.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
rbac.*.create_permission. See Root key permissions.
Examples
Create
Raw body