Delete a user

DELETE $BASE_URL/v1/users/:id

Auth: Authorization: Bearer <accessToken> — an organization-scoped token from Authentication.

​

Path parameters

​

Example

curl --request DELETE \
  --url "$BASE_URL/v1/users/fa000708-10f6-47ea-a35d-d3e1acbd4be5" \
  --header 'Authorization: Bearer <accessToken>'

​

Response

{
  "id": "fa000708-10f6-47ea-a35d-d3e1acbd4be5",
  "fullname": "Jane Cashier",
  "email": "jane@example.com",
  "status": -99,
  "organization": "ca5495d7-36ee-4f6d-8149-0dd082f7c745",
  "branch": "377ec3ad-28c8-4008-b3df-005a434dcf8b",
  "authBranches": [],
  "opaqueId": "pos-user-7",
  "createdAt": "2026-10-08T12:00:00.000Z",
  "updatedAt": "2026-10-08T13:00:00.000Z"
}

• This is a soft delete — the record is kept with status: -99 and is excluded from lists; the user can no longer sign in or be used.
• The delete response does not include roles.
• Deleting a user that does not exist returns entity_not_found (400); a user outside your organization returns auth_error (400).
• Deleting a user whose roles are not branch-level returns user_not_deletable (400); API users return api_user_not_deletable (400).
• The deleted user’s email stays reserved — creating a new user with the same email still returns user_already_exists (400).