One change
Get Activity Summaries
api/admin/analytics/retrieve_summaries
Nearest release: v2.1.250, published an hour before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
api/admin/analytics/retrieve_summaries Changed · +17 / -12 lines
from line 4
Get organization-wide activity summaries for a date range. -Returns one entry per day in [starting_date, ending_date). Data is -typically available with a 1-day lag and may be revised by a few percent -over the following days: when ending_date is omitted it defaults to the -most recent available day + 1, so the last entry covers the most recent -available day. The series can be scoped to an RBAC group via -filter[]=rbac_group_id:<id>. Available to organizations on a Claude -Enterprise plan. Requires an API key with the `read:analytics` scope. +Returns one entry per day from `starting_date` (inclusive) to `ending_date` +(exclusive). Data is typically available with a 1-day lag and may be +revised by a few percent over the following days: when `ending_date` is +omitted it defaults to the most recent available day + 1, so the last +entry covers the most recent available day. The series can be scoped to +an RBAC group via `filter[]=rbac_group_id:{id}`. Available to +organizations on a Claude Enterprise plan. Requires an API key with the +`read:analytics` scope. ## Query parameters
from line 29
- `filter: optional array of string` - Filters as 'dimension:value'. Only rbac_group_id is supported (e.g. filter[]=rbac_group_id:<id>); repeat the param to OR across groups. Scopes the whole day series to members of the matching group(s), re-aggregated from member-level activity — org-wide seat/invite fields and the adoption rates derived from them are null on scoped rows. rbac_group_id accepts the tagged id (rbac_group_..., as emitted in responses and by the spend-limits API) or a bare group UUID, and matches users who held the group at any point during each UTC day (time-of-usage attribution). At most 100 entries. + Filters as `dimension:value`. Only `rbac_group_id` is supported (e.g. `filter[]=rbac_group_id:{id}`); repeat the param to OR across groups. Scopes the whole day series to members of the matching group(s), re-aggregated from member-level activity — org-wide seat/invite fields and the adoption rates derived from them are null on scoped rows. `rbac_group_id` accepts the tagged id (`rbac_group_...`, as emitted in responses and by the spend-limits API) or a bare group UUID, and matches users who held the group at any point during each UTC day (time-of-usage attribution). At most 100 entries. maxItems: 100
from line 67
- `ending_at: string` - End time in UTC of aggregation period (e.g. 2026-01-16T00:00:00Z) + End of the aggregation period (exclusive), UTC midnight in RFC 3339 format (e.g. `2026-01-16T00:00:00Z`). + format: date-time + - `monthly_active_user_count: number` Number of users with token consumption in the 30-day rolling window
from line 85
- `starting_at: string` - Start time in UTC of aggregation period (e.g. 2026-01-15T00:00:00Z) + Start of the aggregation period (inclusive), UTC midnight in RFC 3339 format (e.g. `2026-01-15T00:00:00Z`). + format: date-time + - `weekly_active_user_count: number` Number of users with token consumption in the 7-day rolling window
from line 181
"cowork_weekly_active_user_count": 0, "daily_active_user_count": 0, "daily_adoption_rate": 0, - "ending_at": "ending_at", + "ending_at": "2019-12-27T18:11:19.117Z", "monthly_active_user_count": 0, "monthly_adoption_rate": 0, "pending_invite_count": 0, - "starting_at": "starting_at", + "starting_at": "2019-12-27T18:11:19.117Z", "weekly_active_user_count": 0, "weekly_adoption_rate": 0, "chat_daily_active_user_count": 0,