unkey/authorization/insufficient_permissions

{
  "meta": {
    "requestId": "req_2c9a0jf23l4k567"
  },
  "error": {
    "detail": "Insufficient permissions to access this resource.",
    "status": 403,
    "title": "Insufficient Permissions",
    "type": "/errors/unkey/authorization/insufficient_permissions"
  }
}

​

Likely causes

• The root key was never given this permission.
• The permission names the wrong resource ID, for example an API ID where the URN needs a keyspace ID.
• The request asks for a broader scope than the key’s permission, such as listing deployments without environment filters.
• Someone saved the key in Edit root key and left the permission unchecked. Saving replaces the whole set.

​

How to fix

1. Identify the required resource and action. In unkey:v1:{workspace_id}:{resource_path}#{action}, the path selects the resource and the part after # selects the action.
2. Check the workspace and resource IDs, including every parent in the path. Narrow the request’s filters if it asks for more resources than the task needs.
3. Assign the missing permission through the dashboard or API. For example, unkey:v1:ws_demo:projects/proj_shop/keyspaces/ks_customers/keys/*#write permits creating and updating keys in one keyspace. Replace the example IDs with your own.

​

Related errors

• err:unkey:authorization:forbidden: the operation isn’t allowed for a reason other than a missing permission.
• err:unkey:authentication:key_not_found: the bearer token isn’t a root key at all.
• err:user:bad_request:permissions_query_syntax_error: a permissions query you wrote for keys.verifyKey couldn’t be parsed.