Chat changedapi/beta/organization/analytics/apps/chat
Recorded here
Lines+23added
Lines−28removed
From line
39
where the diff opens
First seen
1 Oct 2026
this site's first read of the page
Recorded edits6to this page, all time
The whole hunk
from line 39, old and new numbered
/
from line 39
3939
4040 maxItems: 100
4141
42- `group_by: optional array of "rbac_group_id" or "user_id"`
42- `group_by: optional array of BetaAnalyticsProjectGroupBy`
4343
4444 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.
4545
from line 55
5555
5656 minimum: 1, maximum: 1000
5757
58- `order: optional "asc" or "desc"`
58- `order: optional BetaAnalyticsOrder`
5959
6060 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.
6161
from line 89
8989
9090- `data: array of BetaAnalyticsProjectActivity`
9191
92 - `distinct_user_count: number`
92 - `created_at: string or null`
9393
94 Number of distinct users who used the project on the requested day, or, in date-range mode, over the requested window — recomputed as an exact distinct count over the window's per-member daily rows, never a sum of per-day values.
95
96 - `message_count: number`
97
98 Number of messages sent in the project on the requested day
99
100 - `project_id: string`
101
102 Tagged project identifier (e.g. `claude_proj_...`)
103
104 - `project_name: string`
105
106 Name of the project
107
108 - `created_at: optional string or null`
109
11094 Project creation timestamp in RFC 3339 format. Null if the project was deleted before attribution was recorded.
11195
11296 format: date-time
11397
114 - `created_by: optional BetaAnalyticsUser or null`
98 - `created_by: BetaAnalyticsUser or null`
11599
116100 User who created the project. Null if the project was deleted before attribution was recorded, or if the creator's account no longer exists.
117101
from line 113
129113
130114 Email address of the user
131115
132 - `distinct_conversation_count: optional number or null`
116 - `distinct_conversation_count: number or null`
133117
134118 Number of distinct conversations in the project. Null on aggregated rows where a distinct count cannot be computed.
135119
136 - `product: optional string or null`
120 - `distinct_user_count: number`
137121
138 Product that produced this row's activity: one of `chat`, `claude_code`, `cowork`, `office_agent`, or `chat_cowork_unified` (Chat and Cowork unified). These are the canonical Cost & Usage product names; an `office_agent` row's per-surface breakdown is in its `office_metrics`. On `/plugins` only `cowork`, `claude_code` and `chat_cowork_unified` occur (the only surfaces with plugin attribution); on `/artifacts` only `chat`, `claude_code`, `cowork` and `chat_cowork_unified` occur (the surfaces that create artifacts); `/apps/chat/projects` does not support the product dimension (a `product` entry in `group_by[]` or `filter[]` there is rejected). Present only when the request grouped by `product`.
122 Number of distinct users who used the project on the requested day, or, in date-range mode, over the requested window — recomputed as an exact distinct count over the window's per-member daily rows, never a sum of per-day values.
139123
124 - `message_count: number`
125
126 Number of messages sent in the project on the requested day
127
128 - `project_id: string`
129
130 Tagged project identifier (e.g. `claude_proj_...`)
131
132 - `project_name: string`
133
134 Name of the project
135
140136 - `rbac_group_id: optional string or null`
141137
142138 Tagged RBAC group identifier (`rbac_group_...`), matching the spend-limits API spelling. Present only when the request grouped by `rbac_group_id`.
from line 163
167163{
168164 "data": [
169165 {
170 "distinct_user_count": 0,
171 "message_count": 0,
172 "project_id": "project_id",
173 "project_name": "project_name",
174166 "created_at": "2019-12-27T18:11:19.117Z",
175167 "created_by": {
176168 "id": "id",
from line 170
178170 "type": "user"
179171 },
180172 "distinct_conversation_count": 0,
181 "product": "product",
173 "distinct_user_count": 0,
174 "message_count": 0,
175 "project_id": "project_id",
176 "project_name": "project_name",
182177 "rbac_group_id": "rbac_group_id",
183178 "rbac_group_name": "rbac_group_name",
184179 "user_id": "user_id"
No line in this hunk matches that.