List Usage Revocation Entry Summary
GET /v1/projects/:project_id/usage/revocations/:revocation_id/entries/summaryAuthentication
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”None. The request body is empty.
Example
Section titled “Example”curl 'http://127.0.0.1:8080/v1/projects/proj_gateway/usage/revocations/urv_001/entries/summary' \ -H 'Authorization: Bearer <api-key>'Response
Section titled “Response”{ "summary": [ { "entry_type": "fund_refund", "status": "completed", "currency": "USD", "count": 2, "amount": "25.00" }, { "entry_type": "fund_refund", "status": "failed", "currency": "USD", "count": 1, "amount": "0.25" } ]}Each bucket groups the request’s entries by entry_type, status, and
currency, with the entry count and the summed amount. The response size
is bounded by the number of distinct buckets, not by the number of entries,
so it stays small even for revocations covering 100k+ events. Use the paged
List Usage Revocation Entries
endpoint for individual rows.
Internal analytics marks (doris_revoke_mark) are never included.