List Usage Reprice Targets

GET /v1/projects/:project_id/usage/events/reprice/:reprice_id/targets

Authentication

Authorization: Bearer <api-key>

Requires usage:read.

Path Parameters

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

Query Parameters

Field	Required	Description
limit	No	Page size, 1–200, default 50. Capped at 200 so large reprice batches cannot produce unbounded responses.
offset	No	Zero-based page offset, default 0.
status	No	Filter by target status (selected, recalculate_pending, recalculated, failed).

Request Body

Empty.

Example

curl 'http://127.0.0.1:8080/v1/projects/proj_gateway/usage/events/reprice/urp_001/targets?limit=50&offset=0&status=failed' \
  -H 'Authorization: Bearer <api-key>'

Response

{
  "targets": [
    {
      "id": "urpt_001",
      "operation_id": "urp_001",
      "revocation_target_id": "urt_001",
      "tenant_id": "t_001",
      "project_id": "proj_gateway",
      "raw_event_id": "raw_001",
      "new_raw_event_id": "raw_new_001",
      "status": "recalculated",
      "created_at": 1781222501,
      "completed_at": 1781222508,
      "updated_at": 1781222508
    }
  ],
  "total": 1
}

total is the number of targets 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.

new_raw_event_id is set when the reprice worker publishes the clone onto ingest (recalculate_pending). new_raw_event_id is filled when the processor successfully persists the new usage fact.