Erase User — POST /api/v1/users/{user_id}/erasure
Erase User
Erase (pseudonymise) this person: refusals in E-1’s order, the exact typed username, then the lock-out committed in ONE transaction and the worker enqueued. An unfinished erasure is resumed.
Endpoint: POST /api/v1/users/{user_id}/erasure
Authentication: Send a signed-in user’s access token in Authorization: Bearer <access token>. API keys are refused.
- Your role must be Admin or higher.
Parameters
Section titled “Parameters”| Name | In | Required | Type | Default | Description |
|---|---|---|---|---|---|
user_id | path | yes | string (uuid) | ||
X-API-Key | header | no | string or null | API key, as an alternative to the access token (see Authentication). |
Request body
Section titled “Request body”| Content type | Body | Required |
|---|---|---|
application/json | ErasureRequest | yes |
Responses
Section titled “Responses”| Status | Meaning | Body |
|---|---|---|
202 | Successful Response | SubjectJobRead (application/json) |
422 | Validation Error | HTTPValidationError (application/json) |
It can also return 401 if your credential is missing or expired, 403 if your credential does not allow this request, and 404 if the item does not exist or you cannot see it. Your role, your project membership and the key’s scope decide what a credential allows. See Errors and retries.
More details
Section titled “More details”- Group: User Management
- Operation ID:
erase_user_api_v1_users__user_id__erasure_post - Source code:
backend/app/routers/subject_erasure.py, line 92 - Specification: OpenAPI JSON