List User Activity changedapi/admin/analytics/users/list
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.
Recorded here
Lines+23added
Lines−11removed
From line
5
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits5to this page, all time
The whole hunk
from line 5, old and new numbered
/
from line 5
55Get per-user activity for a given day, with cursor-based pagination.
66
77Returns activity metrics for each user in the organization, sorted by email
8address. Use group_by[] for per-RBAC-group aggregates, or filter[] to
8address. Use `group_by[]` for per-RBAC-group aggregates, or `filter[]` to
99scope results to specific members, groups, or a chat project. Available
1010to organizations on a Claude Enterprise plan. Requires an API key with
1111the `read:analytics` scope.
from line 20
2020
2121- `ending_date: optional string`
2222
23 UTC date in YYYY-MM-DD format. End of the date range (exclusive); only valid with starting_date. Data is typically available with a 1-day lag (varies by query; the error for a too-recent date names the latest available day), so this can be at most today — which is also the default when omitted, resolved once when the first page is served and reused for the rest of the pagination sequence. At most 366 days after starting_date.
23 UTC date in YYYY-MM-DD format. End of the date range (exclusive); only valid with `starting_date`. Data is typically available with a 1-day lag (varies by query; the error for a too-recent date names the latest available day), so this can be at most today — which is also the default when omitted, resolved once when the first page is served and reused for the rest of the pagination sequence. At most 366 days after `starting_date`.
2424
2525 format: date
2626
2727- `filter: optional array of string`
2828
29 Filters as 'dimension:value', e.g. filter[]=rbac_group_id:<id>. Repeat the param for OR within a dimension and across dimensions for AND. Supported dimensions on this endpoint: project_id, rbac_group_id, user_id. Value forms: project_id takes a tagged project id (claude_proj_...) and scopes each member's row to their claude.ai chat activity within that project (it cannot be combined with group_by[] or an rbac_group_id filter); rbac_group_id takes 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 covered UTC day (time-of-usage attribution); user_id takes a tagged user id (user_...), as emitted in responses. An unsupported dimension returns 400. At most 100 entries.
29 Filters as `dimension:value`, e.g. `filter[]=rbac_group_id:{id}`. Repeat the param for OR within a dimension and across dimensions for AND. Supported dimensions on this endpoint: `project_id`, `rbac_group_id`, `user_id`. Value forms: `project_id` takes a tagged project id (`claude_proj_...`) and scopes each member's row to their claude.ai chat activity within that project (it cannot be combined with `group_by[]` or an `rbac_group_id` filter); `rbac_group_id` takes 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 covered UTC day (time-of-usage attribution); `user_id` takes a tagged user id (`user_...`), as emitted in responses. An unsupported dimension returns 400. At most 100 entries.
3030
3131 maxItems: 100
3232
3333- `group_by: optional array of "rbac_group_id"`
3434
35 Dimensions to break results out by (e.g. group_by[]=rbac_group_id). Supported on this endpoint: rbac_group_id. Rows are already per-member, so the one supported grouping aggregates them per RBAC group instead. Grouped rows carry the requested dimension values as additional fields and paginate like ungrouped responses via next_page; an unsupported dimension returns 400. rbac_group_id attributes a user to every group they held at any point during each covered UTC day, so grouped rows are not an exclusive partition and can sum above org-level totals. At most 100 entries.
35 Dimensions to break results out by (e.g. `group_by[]=rbac_group_id`). Supported on this endpoint: `rbac_group_id`. Rows are already per-member, so the one supported grouping aggregates them per RBAC group instead. Grouped rows carry the requested dimension values as additional fields and paginate like ungrouped responses via `next_page`; an unsupported dimension returns 400. `rbac_group_id` attributes a user to every group they held at any point during each covered UTC day, so grouped rows are not an exclusive partition and can sum above org-level totals. At most 100 entries.
3636
3737 maxItems: 100
3838
from line 44
4444
4545- `order: optional "asc" or "desc"`
4646
47 Sort direction: 'asc' or 'desc'. Defaults to 'asc' for the endpoint's sort column and to 'desc' when order_by names a metric (a top-N ranking). Applies to order_by, or to the endpoint's default sort field when order_by is omitted.
47 Sort direction: `asc` or `desc`. Defaults to `asc` for the endpoint's sort column and to `desc` when `order_by` names a metric (a top-N ranking). Applies to `order_by`, or to the endpoint's default sort field when `order_by` is omitted.
4848
4949 - `"asc"`
5050
from line 56
5656
5757- `page: optional string`
5858
59 Opaque cursor from a previous response's next_page field.
59 Opaque cursor from a previous response's `next_page` field.
6060
6161- `starting_date: optional string`
6262
63 UTC date in YYYY-MM-DD format. Start of a date range (inclusive). Enables rollup mode: one row per entity aggregated over the whole range — addable counters are summed across days, and a distinct count is never summed where summing could double-count (a field's range value is recomputed exactly over the window, approximate via HLL with typical error under 2%, null, or — for the creation-event counts, whose per-day values cannot overlap — a per-day sum that is itself exact; each field's own description says which). Use either date or starting_date, not both. Data is typically available with a 1-day lag (varies by query; the error for a too-recent date names the latest available day) and may be revised by a few percent over the following days. No earlier than 2026-01-01.
63 UTC date in YYYY-MM-DD format. Start of a date range (inclusive). Enables rollup mode: one row per entity aggregated over the whole range — addable counters are summed across days, and a distinct count is never summed where summing could double-count (a field's range value is recomputed exactly over the window, approximate via HLL with typical error under 2%, null, or — for the creation-event counts, whose per-day values cannot overlap — a per-day sum that is itself exact; each field's own description says which). Use either `date` or `starting_date`, not both. Data is typically available with a 1-day lag (varies by query; the error for a too-recent date names the latest available day) and may be revised by a few percent over the following days. No earlier than 2026-01-01.
6464
6565 format: date
6666
from line 132
132132
133133 Core Claude Code activity metrics for a single user on a given day.
134134
135 - `artifacts_created_count: number`
136
137 Number of artifacts created in Claude Code sessions: an artifact counts once, on the day a session first saves it. Counted from 2026-08-17; 0 on earlier days. Exact in date-range mode: a creation belongs to exactly one day, so the per-day counts never overlap and their sum over the window is the exact count of distinct creations in it.
138
135139 - `commit_count: number`
136140
137141 Number of commits made via Claude Code
from line 196
192196
193197 Number of tool actions completed in Cowork sessions
194198
199 - `artifacts_created_count: number`
200
201 Number of artifacts created in Cowork sessions: an artifact counts once, on the day a session first saves it. Counted from 2026-08-17; 0 on earlier days. Exact in date-range mode: a creation belongs to exactly one day, so the per-day counts never overlap and their sum over the window is the exact count of distinct creations in it.
202
195203 - `connectors_used_count: number`
196204
197205 Total number of connector invocations in Cowork sessions
from line 358
350358
351359 - `last_activity_date: optional string or null`
352360
353 Most recent UTC day (YYYY-MM-DD) on which the user had any counted activity, within the requested window: equal to the requested date in single-day mode, and to the latest active day in [starting_date, ending_date) in date-range rollup mode — never a day earlier than the window start. On filtered requests (`filter[]`) only days matching the filter count: with `filter[]=rbac_group_id` it is the last day the user was active while a member of that group, consistent with the row's other metrics. Null on grouped (`group_by[]`) rows. Omitted from the response while last-activity reporting is not enabled for this organization.
361 Most recent UTC day (YYYY-MM-DD) on which the user had any counted activity, within the requested window: equal to the requested `date` in single-day mode, and to the latest active day from `starting_date` (inclusive) to `ending_date` (exclusive) in date-range rollup mode — never a day earlier than the window start. On filtered requests (`filter[]`) only days matching the filter count: with `filter[]=rbac_group_id:{id}` it is the last day the user was active while a member of that group, consistent with the row's other metrics. On grouped (`group_by[]`) rows it is the latest day any member of the group was active (the requested `date` in single-day mode). Omitted from the response while last-activity reporting is not enabled for this organization.
354362
363 format: date
364
355365 - `rbac_group_id: optional string or null`
356366
357367 Tagged RBAC group identifier (`rbac_group_...`), matching the spend-limits API spelling. Present only when the request grouped by `rbac_group_id`.
from line 372
362372
363373 - `user: optional AnalyticsUser or null`
364374
365 User identifier.
375 A user in the organization, identified by tagged id and email address.
366376
367377 - `id: string`
368378
from line 382
372382
373383 Email address of the user
374384
375 - `type: optional "user"`
385 - `type: "user"`
376386
377387 Object type. Always `user`.
378388
from line 422
412422 },
413423 "claude_code_metrics": {
414424 "core_metrics": {
425 "artifacts_created_count": 0,
415426 "commit_count": 0,
416427 "distinct_session_count": 0,
417428 "lines_of_code": {
from line 452
441452 },
442453 "cowork_metrics": {
443454 "action_count": 0,
455 "artifacts_created_count": 0,
444456 "connectors_used_count": 0,
445457 "dispatch_turn_count": 0,
446458 "distinct_connectors_used_count": 0,
from line 518
506518 },
507519 "web_search_count": 0,
508520 "distinct_user_count": 0,
509 "last_activity_date": "last_activity_date",
521 "last_activity_date": "2019-12-27",
510522 "rbac_group_id": "rbac_group_id",
511523 "rbac_group_name": "rbac_group_name",
512524 "user": {
No line in this hunk matches that.