Skip to main content
DELETE
/
api
/
v1
/
users
/
delete
/
{id}
Delete User
curl --request DELETE \
  --url https://api.example.com/api/v1/users/delete/{id}
(Empty response body)
This endpoint permanently removes a user and their associations from the library management system.

Authentication

This endpoint requires JWT authentication. Include a valid JWT token in the Authorization header.
Authorization: Bearer <your_jwt_token>

Path Parameters

id
string
required
The unique identifier (UUID) of the user to delete

Response

This endpoint returns no content on success (HTTP 204).

Example Request

cURL
curl -X DELETE "https://api.library.com/api/v1/users/delete/550e8400-e29b-41d4-a716-446655440000" \
  -H "Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."

Example Response

(Empty response body)

Status Codes

CodeDescription
204Successfully deleted user (no content returned)
400Bad request - Invalid UUID format
401Unauthorized - Invalid or missing JWT token
404User not found
500Internal server error

Notes

  • This operation is permanent and cannot be undone
  • Deleting a user removes their associations with books but does not delete the books themselves
  • The endpoint returns no content body on successful deletion
  • Consider implementing soft deletion in production environments for data recovery purposes

Build docs developers (and LLMs) love