Get Per-User Token Usage changedapi/beta/organization/analytics/user_usage_report/list
Nearest release: v2.1.314, published 6 hours after this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+5added
Lines−9removed
From line
7
where the diff opens
First seen
1 Oct 2026
this site's first read of the page
Recorded edits8to this page, all time
The whole hunk
from line 7, old and new numbered
/
from line 7
77
88**GET** `/v1/organizations/analytics/user_usage_report`
99
10Get per-user token usage across a date range.
10[Legacy] Get per-user token usage across a date range.
1111
12Returns one row per user, ranked by the chosen token metric. Use this to
13see which users consume the most tokens. Only usage attributable to a
14seat user is included; for organization-wide totals including direct
15API-key and automation traffic, use the bucketed
16`/v1/organizations/analytics/usage_report` endpoint. Available to
17organizations on a Claude Enterprise plan. Requires an API key with the
18`read:analytics` scope.
12Returns usage per user, ranked by the chosen token metric; `group_by[]` or `bucket_width` splits a user across several rows. Use this to see which users consume the most tokens. Only usage attributed to a user account is included; usage with no user attributed to it, such as requests attributed only to an API key, is left out. Available to organizations on a Claude Enterprise plan. Requires an API key with the `read:analytics` scope.
13
14This endpoint is one of the legacy Claude Enterprise usage and cost reports. For new integrations, use [`GET /v1/organizations/analytics/usage`](https://platform.claude.com/docs/en/api/beta/organization/analytics/usage/list?sdk_languages=http) in the Usage and Cost Analytics API instead. To move an existing integration, see [Migrate from the Claude Enterprise usage and cost reports](https://platform.claude.com/docs/en/manage-claude/usage-cost-analytics-api?sdk_languages=http#migrate-from-enterprise-analytics-reports).
1915
2016## Query parameters
2117
No line in this hunk matches that.