Retry Usage Revocation
Reopens a failed or completed_with_errors revocation request (or re-publishes
an in-progress request) so the worker can continue incomplete fund refund and
Doris mark entries. Idempotency keys and occupied fund details are reused.
POST /v1/projects/:project_id/usage/revocations/:revocation_id/retryAuthentication
Section titled “Authentication”Authorization: Bearer <api-key>Requires usage:revocation.
Path Parameters
Section titled “Path Parameters”| Field | Required | Description |
|---|---|---|
project_id |
Yes | Project that owns the request. |
revocation_id |
Yes | Revocation request ID. |
Request Body
Section titled “Request Body”Empty. Send {} or no body.
Example
Section titled “Example”curl -X POST 'http://127.0.0.1:8080/v1/projects/proj_gateway/usage/revocations/urv_001/retry' \ -H 'Authorization: Bearer <api-key>' \ -H 'Content-Type: application/json' \ -d '{}'Response
Section titled “Response”202 Accepted
{ "revocation_id": "urv_001", "status": "processing"}Completed requests with no remaining work return 400.
If the worker-queue publish fails, the API still returns 202 with
"status": "enqueue_failed"; the request status change is already committed
and can be re-published by calling retry again.