Retry Usage Reprice

Reopens a failed or completed_with_errors reprice operation and resets failed targets to selected while keeping new_raw_event_id / new_raw_event_id so republish reuses the same StableID revision.

POST /v1/projects/:project_id/usage/events/reprice/:reprice_id/retry

Authentication

Authorization: Bearer <api-key>

Requires usage:reprice.

Path Parameters

Field	Required	Description
project_id	Yes	Project that owns the operation.
reprice_id	Yes	Reprice operation ID.

Request Body

Empty. Send {} or no body.

Example

curl -X POST 'http://127.0.0.1:8080/v1/projects/proj_gateway/usage/events/reprice/urp_001/retry' \
  -H 'Authorization: Bearer <api-key>' \
  -H 'Content-Type: application/json' \
  -d '{}'

Response

202 Accepted

{
  "reprice_id": "urp_001",
  "status": "processing"
}

If the worker-queue publish fails, the API still returns 202 with "status": "enqueue_failed"; the operation status change is already committed and can be re-published by calling retry again.