permission_already_exists

err:unkey:data:permission_already_exists

A permission with the same slug already exists in your workspace, so permissions.createPermission didn’t create one. You get HTTP 409.

Example response

{
  "meta": {
    "requestId": "req_2c9a0jf23l4k567"
  },
  "error": {
    "detail": "A permission with slug 'documents.read' already exists in this workspace",
    "status": 409,
    "title": "Conflicting Resource",
    "type": "/errors/unkey/data/permission_already_exists"
  }
}

Likely causes

You already created this permission. Slugs are unique per workspace.

How to fix

Reuse the existing permission (find it with permissions.listPermissions), or pick a different slug.

In provisioning code, treat a 409 as success and continue.

err:unkey:data:permission_not_found: a referenced permission doesn’t exist.
err:unkey:data:role_already_exists: a role name collides.

Last modified on October 6, 2026

⌘I

Get started

Workspace

Audit logs

Billing

Root keys

API

CLI

AI coding

Security

Errors

permission_already_exists

Likely causes

How to fix

​Likely causes

​How to fix

​Related errors

Likely causes

How to fix

Related errors