Enqueue Retention Purge — POST /api/v1/projects/{project_id}/retention-policy/purge
Enqueue Retention Purge
Enqueue an execute-mode purge for THIS project (202).
Endpoint: POST /api/v1/projects/{project_id}/retention-policy/purge
Authentication: Send a signed-in user’s access token in Authorization: Bearer <access token>, or an API key in X-API-Key: <API key>.
- Your role must be Admin or higher.
- You must be a member of the project. Admins always have access.
Parameters
Section titled “Parameters”| Name | In | Required | Type | Default | Description |
|---|---|---|---|---|---|
project_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 | RetentionPurgeRequest | yes |
Responses
Section titled “Responses”| Status | Meaning | Body |
|---|---|---|
202 | Successful Response | RetentionPurgeQueued (application/json) |
422 | Validation Error | HTTPValidationError (application/json) |
Errors this endpoint returns, read from its source code:
404409422
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: Retention
- Operation ID:
enqueue_retention_purge_api_v1_projects__project_id__retention_policy_purge_post - Source code:
backend/app/routers/retention.py, line 320 - Specification: OpenAPI JSON