Requeue Failed Outbox Operations — POST /api/v1/admin/maintenance/outbox/requeue

Requeue Failed Outbox Operations

Put failed post-ingestion work back in the run outbox (re-audit N23).

Endpoint: POST /api/v1/admin/maintenance/outbox/requeue

Authentication: Send a signed-in user’s access token in Authorization: Bearer <access token>, or an API key in X-API-Key: <API key>.

• A minimum role applies. The source code names it.

Parameters

Name	In	Required	Type	Default	Description
X-API-Key	header	no	string or null		API key, as an alternative to the access token (see Authentication).

Request body

Content type	Body	Required
application/json	OutboxRequeueRequest	yes

Responses

Status	Meaning	Body
200	Successful Response	Not documented (application/json)
422	Validation Error	HTTPValidationError (application/json)

Response fields not documented. The API specification does not describe the body of every response this endpoint returns, so this page cannot list those fields. The body is not empty. To see it, call the endpoint on your own installation. All endpoints with undocumented responses.

Errors this endpoint returns, read from its source code:

• 422

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

• Group: Admin Maintenance
• Operation ID: requeue_failed_outbox_operations_api_v1_admin_maintenance_outbox_requeue_post
• Source code: backend/app/routers/admin_maintenance.py, line 333
• Specification: OpenAPI JSON