permission_not_found

{
  "meta": {
    "requestId": "req_2c9a0jf23l4k567"
  },
  "error": {
    "detail": "Permission 'documents.read' was not found.",
    "status": 404,
    "title": "Not Found",
    "type": "/errors/unkey/data/permission_not_found"
  }
}

​

Likely causes

• You attached a permission to a key or role before creating it. The whole request fails if any one slug is missing, and detail names the first.
• The slug has a typo. Slugs aren’t case-sensitive.
• Your root key can’t read the permission. permissions.getPermission and permissions.deletePermission return this 404 instead of a 403. A key that can read the permission but lacks the action gets a 403 err:unkey:authorization:insufficient_permissions that names the missing permission.

​

How to fix

1. Create every permission you need with permissions.createPermission before you reference it.
2. Check the slug. permissions.listPermissions shows what exists.
3. On permissions.getPermission or permissions.deletePermission, check the root key’s permissions before you decide the permission is missing.

​

Related errors

• err:unkey:data:permission_already_exists: a slug collides on create.
• err:unkey:data:role_not_found: a role doesn’t exist.
• err:unkey:data:key_not_found: the key doesn’t exist.