Chat Projects changedapi/admin/analytics/chat_projects
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+23added
Lines−16removed
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
### Query parameters #### Response (200) ## Domain types ### Query Parameters #### Response ## Domain Types
The whole hunk
from line 1, old and new numbered
/
from line 1
1---
2title: Chat Projects
3url: https://platform.claude.com/docs/en/api/admin/analytics/chat_projects
4---
5
61# Chat Projects
72
83## Get Chat Project Usage
94
10**get** `/v1/organizations/analytics/apps/chat/projects`
5**GET** `/v1/organizations/analytics/apps/chat/projects`
116
127Get per-project activity for a given day, with cursor-based pagination.
138
from line 12
1712supported dimensions. Available to organizations on a Claude Enterprise
1813plan. Requires an API key with the `read:analytics` scope.
1914
20### Query Parameters
15### Query parameters
2116
2217- `date: optional string`
2318
2419 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.
2520
21 format: date
22
2623- `ending_date: optional string`
2724
2825 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.
2926
27 format: date
28
3029- `filter: optional array of string`
3130
3231 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.
3332
33 maxItems: 100
34
3435- `group_by: optional array of "rbac_group_id" or "user_id"`
3536
3637 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.
3738
39 maxItems: 100
40
3841 - `"rbac_group_id"`
3942
4043 - `"user_id"`
from line 46
4346
4447 Number of results per page (1-1000, default 100).
4548
49 minimum: 1, maximum: 1000
50
4651- `order: optional "asc" or "desc"`
4752
4853 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 68
6368
6469 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.
6570
71 format: date
72
6673### Returns
6774
68- `ChatProjectUsage object { data, next_page }`
75- `ChatProjectUsage object`
6976
7077 Response for GET /v1/organizations/analytics/apps/chat/projects.
7178
72 - `data: array of object { distinct_user_count, message_count, project_id, 8 more }`
79 - `data: array of object`
7380
7481 - `distinct_user_count: number`
7582
from line 114
107114
108115 Object type. Always `user`.
109116
110 - `"user"`
117 default: user
111118
112119 - `distinct_conversation_count: optional number or null`
113120
from line 142
135142
136143### Example
137144
138```http
145```bash
139146curl https://api.anthropic.com/v1/organizations/analytics/apps/chat/projects \
140147 -H 'anthropic-version: 2023-06-01' \
141148 -H "X-Api-Key: $ANTHROPIC_ADMIN_API_KEY"
142149```
143150
144#### Response
151#### Response (200)
145152
146153```json
147154{
from line 175
168175}
169176```
170177
171## Domain Types
178## Domain types
172179
173180### Chat Project Usage
174181
175- `ChatProjectUsage object { data, next_page }`
182- `ChatProjectUsage object`
176183
177184 Response for GET /v1/organizations/analytics/apps/chat/projects.
178185
179 - `data: array of object { distinct_user_count, message_count, project_id, 8 more }`
186 - `data: array of object`
180187
181188 - `distinct_user_count: number`
182189
from line 221
214221
215222 Object type. Always `user`.
216223
217 - `"user"`
224 default: user
218225
219226 - `distinct_conversation_count: optional number or null`
220227
No line in this hunk matches that.