Get Chat Project Usage changedapi/admin/analytics/chat_projects/list
Nearest release: v2.1.245, published an hour 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+22added
Lines−15removed
From line
1
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits5to this page, all time
# Get Chat Project Usage ## Query parameters ## Returns ## Example ### Response (200) ## Get Chat Project Usage ### Query Parameters ### Returns ### Example #### Response
The whole hunk
from line 1, old and new numbered
/
from line 1
1---
2title: Get Chat Project Usage
3url: https://platform.claude.com/docs/en/api/admin/analytics/chat_projects/list
4---
1# Get Chat Project Usage
52
6## Get Chat Project Usage
3**GET** `/v1/organizations/analytics/apps/chat/projects`
74
8**get** `/v1/organizations/analytics/apps/chat/projects`
9
105Get per-project activity for a given day, with cursor-based pagination.
116
127Returns activity metrics for each project in the organization, sorted by
from line 10
1510supported dimensions. Available to organizations on a Claude Enterprise
1611plan. Requires an API key with the `read:analytics` scope.
1712
18### Query Parameters
13## Query parameters
1914
2015- `date: optional string`
2116
2217 UTC date in YYYY-MM-DD format. The day to get project activity for. 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.
2318
19 format: date
20
2421- `ending_date: optional string`
2522
2623 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.
2724
25 format: date
26
2827- `filter: optional array of string`
2928
3029 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_...); 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.
3130
31 maxItems: 100
32
3233- `group_by: optional array of "rbac_group_id" or "user_id"`
3334
3435 Dimensions to break results out by (e.g. group_by[]=user_id). Supported on this endpoint: rbac_group_id, user_id. 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.
3536
37 maxItems: 100
38
3639 - `"rbac_group_id"`
3740
3841 - `"user_id"`
from line 44
4144
4245 Number of results per page (1-1000, default 100).
4346
47 minimum: 1, maximum: 1000
48
4449- `order: optional "asc" or "desc"`
4550
4651 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.
from line 66
6166
6267 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.
6368
64### Returns
69 format: date
6570
66- `ChatProjectUsage object { data, next_page }`
71## Returns
6772
73- `ChatProjectUsage object`
74
6875 Response for GET /v1/organizations/analytics/apps/chat/projects.
6976
70 - `data: array of object { distinct_user_count, message_count, project_id, 8 more }`
77 - `data: array of object`
7178
7279 - `distinct_user_count: number`
7380
from line 112
105112
106113 Object type. Always `user`.
107114
108 - `"user"`
115 default: user
109116
110117 - `distinct_conversation_count: optional number or null`
111118
from line 138
131138
132139 Opaque cursor for the next page, or null if no more results
133140
134### Example
141## Example
135142
136```http
143```bash
137144curl https://api.anthropic.com/v1/organizations/analytics/apps/chat/projects \
138145 -H 'anthropic-version: 2023-06-01' \
139146 -H "X-Api-Key: $ANTHROPIC_ADMIN_API_KEY"
140147```
141148
142#### Response
149### Response (200)
143150
144151```json
145152{
No line in this hunk matches that.