Attribution Data API
List distinct dimension keys
Returns distinct metadata dimension keys from usage events within a date range, sorted alphabetically. Call it with a GET request to /attribution-data/dimension-keys, authenticated with a restricted API key and the "costs:read" scope.
Returns distinct metadata dimension keys from usage events within a date range, sorted alphabetically. Enables dynamic population of dimension selectors. The response is not paginated and is capped at 1000 keys. `truncated` is `true` when that cap was reached. Reaching it means your events carry a per-request metadata key (an id, a timestamp) rather than a fixed set of dimensions, since the cap counts distinct KEY NAMES, not values. Requests count toward your per-API-key rate limit; sustained overruns return 429 with the standard error envelope.
Authentication and scopes
Authenticate with a restricted API key in the Authorization: Bearer <key> header. This endpoint requires the costs:read scope.
Parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
start_date | query | string | Yes | Start of date range (ISO 8601, inclusive). |
end_date | query | string | Yes | End of date range (ISO 8601, exclusive). |
Response fields
Fields returned in the 200 response body. Nested objects are listed under their parent. A field marked optional may be absent from the body; one marked nullable is always present but its value may be null.
| Field | Type | Description |
|---|---|---|
keys | string[] | Distinct metadata dimension keys. |
truncated | boolean | True when the key list hit the server ceiling and was truncated. Always present, `false` on a complete list: stated rather than omitted, so a truncated list is detectable on the wire instead of leaving the caller to assume a short list is the whole list. Same contract as the `truncated` flag on the dimension-values, agents and workflows responses. |
Error codes
Errors return the standard error envelope with a code, message, and a correlationId you can quote to support.
| Status | When it happens |
|---|---|
400 | Invalid request data. Check that start_date and end_date are valid ISO 8601 dates and fix the field named in error.message. |
401 | Missing or invalid API key. Send your key as Authorization: Bearer YOUR_API_KEY. |
403 | API key lacks the costs:read scope. Create or update an API key with the costs:read scope, then retry. |
429 | Rate limit or plan quota exceeded. Slow down and retry after the current window resets. |
Rate limits and retries
Rate limit or plan quota exceeded. Slow down and retry after the current window resets.