Chelabase
ManagementApp users

Delete a user

DELETE
/v1/projects/{id}/users/{user_id}

Ends the user's sessions and deletes the identity user; the users table's row follows the project's on_delete setting. The sessions are revoked first, so a 503 still ended them.

Authorization

bearer
AuthorizationBearer <token>

In: header

Path Parameters

id*string

Project id

Formatuuid
user_id*string

User id

Formatuuid

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

application/json

curl -X DELETE "https://example.com/v1/projects/497f6eca-6276-4993-bfeb-53cbbbba6f08/users/497f6eca-6276-4993-bfeb-53cbbbba6f08"
Empty

Change a user's email PATCH

Sending `email` ends the user's sessions, also when it's the address they already have, so a retry finishes a change whose answer was an error. A `5xx` for a new address may mean the address changed: send the same request again. `email_verified: true` alone marks the current address verified; a verified address can only become unverified with a new `email`. A password can't be changed here. The users table follows through the sync job.

Deactivate a user POST

Bans the user: they can't sign in, and their sessions end. The sessions are revoked first, so a `503` still ended them.