List Usage Revocation Entries
GET /v1/projects/:project_id/usage/revocations/:revocation_id/entriesAuthentication
Section titled “Authentication”Authorization: Bearer <api-key>Requires usage:read.
Path Parameters
Section titled “Path Parameters”| Field | Required | Description |
|---|---|---|
project_id |
Yes | Project that owns the task. |
revocation_id |
Yes | Revocation request ID. |
Query Parameters
Section titled “Query Parameters”| Field | Required | Description |
|---|---|---|
limit |
No | Page size, 1–200, default 50. Capped at 200 so large revocations cannot produce unbounded responses. |
offset |
No | Zero-based page offset, default 0. |
status |
No | Filter by entry status (pending, processing, completed, failed). |
Request Body
Section titled “Request Body”Empty.
Example
Section titled “Example”curl 'http://127.0.0.1:8080/v1/projects/proj_gateway/usage/revocations/urv_001/entries?limit=50&offset=0&status=failed' \ -H 'Authorization: Bearer <api-key>'Response
Section titled “Response”{ "entries": [ { "id": "ure_001", "request_id": "urv_001", "target_id": "urt_001", "entry_type": "fund_refund", "status": "completed", "raw_event_id": "raw_001", "amount": "12.50", "currency": "USD", "idempotency_key": "fund_refund:ufdd_001", "created_at": 1781222401, "completed_at": 1781222402, "updated_at": 1781222402 } ], "total": 1}total is the number of entries matching the current filter, so clients can
page with offset += limit until the returned page is empty. Results are
ordered by created_at, id ascending for stable paging.
Revocation never reverses usage-limit counters. Only fund refund entries are
exposed here; the internal analytics revoked_at mark is applied automatically
and is not listed as a separate entry.
For the full-request totals behind very large revocations, prefer List Usage Revocation Entry Summary: it aggregates entries by type/status/currency in one response.