---
title: "Delete a user"
method: DELETE
path: "/v2/users/{user_id}"
tags: ["Users"]
---

# Delete a user

`DELETE /v2/users/{user_id}`

Permanently block a user from the account. The user's status is set to
`inactive` and they can no longer log in. The operation cascades to:
- Organization memberships
- Space memberships
- User API keys
- Role bindings

Blocked users cannot be re-invited via the create endpoint — `inactive`
is a terminal state. Callers cannot delete themselves. The operation is
idempotent — blocking an already-inactive user returns 204.

Requires account admin role or USER_DELETE permission.

<Note>This endpoint is in beta, read more [here](https://arize.com/docs/ax/rest-reference#api-version-stages).</Note>

## Path parameters

- `user_id` string, required — A universally unique identifier (base64-encoded opaque string).

## Response `204`

User successfully removed from the account

## Other responses

- `400` — Invalid request
- `401` — Authentication is required
- `403` — Insufficient permissions to access this resource
- `404` — Not found
- `429` — Rate limit exceeded

---

[API](https://skmtc.net/arize-ai/apis/arize-rest-api.md) · [All operations](https://skmtc.net/arize-ai/apis/arize-rest-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/arize-ai/arize-rest-api/versions/2ce448f1de13/schema)