Get API key usage stats
GET
/v1/admin/keys/{keyId}/usage-statsReturn lifetime and rolling-window request statistics for a specific API key.
How to call this endpoint
Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.
Path, query, and header parameters
These parameters control which ACP object the endpoint acts on and how the request is processed.
Path parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
| keyId | path | string | Yes | API key ID |
Query parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
| windows | query | string | No | Comma-separated list of day windows to summarize. |
Body schema
This endpoint does not require a request body.
None.
What the API returns
Each response code below includes the documented payload shape for the ACP API.
200API key usage summaryapplication/json
| Field | Type | Required | Description |
|---|---|---|---|
| keyId | string | No | API key ID. |
| lastUsedAt | string | No | ISO 8601 timestamp. |
| lifetime | object | No | — |
| lifetime.totalRequests | integer | No | — |
| lifetime.successRate | number | No | — |
| lifetime.lastUsed | string | No | — |
| windows | object | No | — |