Remove a permission from your workspace. This also removes the permission from all API keys and roles.
Important: This operation cannot be undone and immediately affects all API keys and roles that had this permission assigned.
Required Permissions
Your root key must have the following permission:
rbac.*.delete_permissionUnkey uses API keys (root keys) for authentication. These keys authorize access to management operations in the API. To authenticate, include your root key in the Authorization header of each request:
Authorization: Bearer unkey_123Root keys have specific permissions attached to them, controlling what operations they can perform. Key permissions follow a hierarchical structure with patterns like resource.resource_id.action (e.g., apis.*.create_key, apis.*.read_api).
Security best practices:
Specifies which permission to permanently delete from your workspace.
This can be a permission ID or a permission slug.
WARNING: Deleting a permission has immediate and irreversible consequences:
Before deletion, ensure you:
3 - 255"perm_1234567890abcdef"
Permission deleted successfully
Metadata object included in every API response. This provides context about the request and is essential for debugging, audit trails, and support inquiries. The requestId is particularly important when troubleshooting issues with the Unkey support team.
Empty response object by design. A successful response indicates this operation was successfully executed.