List Usage Revocation Targets
GET /v1/projects/:project_id/usage/revocations/:revocation_id/targetsAuthentication
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 a single response stays bounded on large revocations. |
offset |
No | Zero-based page offset, default 0. |
status |
No | Filter by target status (selected, processing, completed, already_revoked, not_found, 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/targets?limit=50&offset=0&status=failed' \ -H 'Authorization: Bearer <api-key>'Response
Section titled “Response”{ "targets": [ { "id": "urt_001", "tenant_id": "t_001", "project_id": "proj_gateway", "raw_event_id": "raw_001", "occurred_at": 1781220000, "usage_version": 42, "owner_request_id": "urv_001", "status": "completed", "created_at": 1781222400, "completed_at": 1781222405, "updated_at": 1781222405 } ], "total": 1}total is the number of targets matching the current filter (all targets
when status is omitted), so clients can page with offset += limit until
the returned page is empty. Results are ordered by created_at, id
ascending for stable paging.