Skip to main content
DELETE
/
v1beta1
/
users
/
{id}
Delete User
curl --request DELETE \
  --url https://api.example.com/v1beta1/users/{id}
{
  "400": {},
  "401": {},
  "403": {},
  "404": {},
  "500": {}
}
Permanently delete a user and all associated relations from Frontier. This operation cannot be undone.

Authentication

This endpoint requires authentication with appropriate permissions. Include a valid bearer token in the Authorization header.

Path Parameters

id
string
required
User ID (UUID) of the user to delete. Must be a valid UUID format.

Response

Returns an empty response with status code 200 on successful deletion.

Example Request

curl -X DELETE 'https://api.frontier.example.com/v1beta1/users/9f256f86-4a1e-4b2a-9c45-6d2c8f5a3b7e' \
  -H 'Authorization: Bearer <token>'

Example Response

{}

What Gets Deleted

When a user is deleted:
  1. The user record is permanently removed from the database
  2. All authorization relations where the user is the subject are deleted
  3. User memberships in organizations, projects, and groups are removed
  4. Any policies directly assigned to the user are removed
Note: This is a cascade delete operation that cleans up all user-related data.

Error Codes

400
error
Bad Request - Invalid user ID format (must be a valid UUID).
401
error
Unauthorized - Invalid or missing authentication token.
403
error
Forbidden - Insufficient permissions to delete users.
404
error
Not Found - User does not exist with the provided ID.
500
error
Internal Server Error - An unexpected error occurred during deletion.

Important Considerations

  • This operation is irreversible - deleted users cannot be recovered
  • Ensure you have proper authorization before deleting users
  • Consider disabling users instead of deleting them if you need to maintain audit trails
  • Use the Disable User endpoint for temporary deactivation

Build docs developers (and LLMs) love