Delete role
Remove a role from your workspace. This also removes the role from all assigned API keys.
Important: This operation cannot be undone and immediately affects all API keys that had this role assigned.
Required Permissions
Your root key must have the following permission:
rbac.*.delete_role
Authorizations
Unkey uses bearer tokens for authentication. Public integrations use root keys, while the dashboard proxy uses short-lived JWTs. To authenticate, include the token in the Authorization header of each request:
Root keys have specific permissions attached to them, controlling what operations they can perform. Legacy permissions use tuple strings like api.*.create_key; resource permissions use Unkey Resource Names plus actions, like unkey:v1:ws_123:keyspaces/*#create_key.
Security best practices:
- Keep root keys secure and never expose them in client-side code
- Use different root keys for different environments
- Rotate keys periodically, especially after team member departures
- Create keys with minimal necessary permissions following least privilege principle
- Monitor key usage with audit logs.
Body
Unique identifier of the role to permanently delete from your workspace. Must either be a valid role ID that begins with 'role_' or the given role name and exists within your workspace.
WARNING: Deletion is immediate and irreversible with significant consequences:
- All API keys assigned this role will lose the associated permissions
- Access to resources protected by this role's permissions will be denied
- Any authorization logic depending on this role will start failing
- Historical analytics referencing this role remain intact
Before deletion, ensure:
- You've updated any dependent authorization logic or code
- You've migrated any keys to use alternative roles or direct permissions
- You've notified relevant team members of the access changes
1 - 128"role_dns_manager"
Response
Role deleted successfully