Get Erasure Preview — GET /api/v1/users/{user_id}/erasure-preview
Get Erasure Preview
Counts of what erasing this person would delete / rewrite, keep and leave open, the blockers (listed, not raised), the pseudonym, and an unfinished erasure job to resume. Writes nothing.
Endpoint: GET /api/v1/users/{user_id}/erasure-preview
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”No request body.
Responses
Section titled “Responses”| Status | Meaning | Body |
|---|---|---|
200 | Successful Response | ErasurePreview (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:
get_erasure_preview_api_v1_users__user_id__erasure_preview_get - Source code:
backend/app/routers/subject_erasure.py, line 78 - Specification: OpenAPI JSON