Connectors changedapi/beta/organization/analytics/connectors
Nearest release: v2.1.287, published 4 hours 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+98added
Lines−212removed
From line
82
where the diff opens
First seen
10 Sep 2026
this site's first read of the page
Recorded edits2to this page, all time
## Domain types ### Beta Connector Usage
The whole hunk
from line 82, old and new numbered
/
from line 82
8282
8383### Returns
8484
85- `BetaConnectorUsage object`
85- `data: array of BetaAnalyticsConnectorActivity`
8686
87 Response for GET /v1/organizations/analytics/connectors.
87 - `chat_metrics: BetaAnalyticsConnectorChatMetrics`
8888
89 - `data: array of object`
89 Claude.ai activity metrics for a single connector on a given day.
9090
91 - `chat_metrics: object`
91 - `distinct_conversation_connector_used_count: number or null`
9292
93 Claude.ai activity metrics for a single connector on a given day.
93 Number of distinct conversations in which the connector was used. Approximate (HLL, typical error <2%) in date-range mode. Null on aggregated rows where a distinct count cannot be computed.
9494
95 - `distinct_conversation_connector_used_count: number or null`
95 - `claude_code_metrics: BetaAnalyticsConnectorClaudeCodeMetrics`
9696
97 Number of distinct conversations in which the connector was used. Approximate (HLL, typical error <2%) in date-range mode. Null on aggregated rows where a distinct count cannot be computed.
97 Claude Code activity metrics for a single connector on a given day.
9898
99 - `claude_code_metrics: object`
99 - `distinct_session_connector_used_count: number or null`
100100
101 Claude Code activity metrics for a single connector on a given day.
101 Number of distinct Claude Code sessions in which the connector was used. Approximate (HLL, typical error <2%) in date-range mode. Null on aggregated rows where a distinct count cannot be computed.
102102
103 - `distinct_session_connector_used_count: number or null`
103 - `connector_name: string`
104104
105 Number of distinct Claude Code sessions in which the connector was used. Approximate (HLL, typical error <2%) in date-range mode. Null on aggregated rows where a distinct count cannot be computed.
105 Name of the connector. Some rows carry an opaque connector id here instead of a readable name; `connector_display_name` holds the resolved name for those rows.
106106
107 - `connector_name: string`
107 - `cowork_metrics: BetaAnalyticsConnectorCoworkMetrics`
108108
109 Name of the connector. Some rows carry an opaque connector id here instead of a readable name; `connector_display_name` holds the resolved name for those rows.
109 Cowork activity metrics for a single connector on a given day.
110110
111 - `cowork_metrics: object`
111 - `distinct_session_connector_used_count: number or null`
112112
113 Cowork activity metrics for a single connector on a given day.
113 Number of distinct Cowork sessions in which the connector was used. Approximate (HLL, typical error <2%) in date-range mode. Null on aggregated rows where a distinct count cannot be computed.
114114
115 - `distinct_session_connector_used_count: number or null`
115 - `distinct_user_count: number`
116116
117 Number of distinct Cowork sessions in which the connector was used. Approximate (HLL, typical error <2%) in date-range mode. Null on aggregated rows where a distinct count cannot be computed.
117 Number of distinct users who used the connector 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.
118118
119 - `distinct_user_count: number`
119 - `office_metrics: BetaAnalyticsConnectorOfficeMetrics`
120120
121 Number of distinct users who used the connector 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.
121 Office Agent activity metrics for a single connector on a given day, broken out by Office product.
122122
123 - `office_metrics: object`
123 - `excel: BetaAnalyticsConnectorOfficeProductMetrics`
124124
125 Office Agent activity metrics for a single connector on a given day, broken out by Office product.
125 Office Agent activity metrics for a single connector on a given day within one Office product.
126126
127 - `excel: BetaConnectorOfficeProductMetrics`
127 - `distinct_session_connector_used_count: number or null`
128128
129 Office Agent activity metrics for a single connector on a given day within one Office product.
129 Number of distinct Office Agent sessions in which the connector was used. Approximate (HLL, typical error <2%) in date-range mode. Null on aggregated rows where a distinct count cannot be computed.
130130
131 - `distinct_session_connector_used_count: number or null`
131 - `outlook: BetaAnalyticsConnectorOfficeProductMetrics`
132132
133 Number of distinct Office Agent sessions in which the connector was used. Approximate (HLL, typical error <2%) in date-range mode. Null on aggregated rows where a distinct count cannot be computed.
133 Office Agent activity metrics for a single connector on a given day within one Office product.
134134
135 - `outlook: BetaConnectorOfficeProductMetrics`
135 - `powerpoint: BetaAnalyticsConnectorOfficeProductMetrics`
136136
137 Office Agent activity metrics for a single connector on a given day within one Office product.
137 Office Agent activity metrics for a single connector on a given day within one Office product.
138138
139 - `powerpoint: BetaConnectorOfficeProductMetrics`
139 - `word: BetaAnalyticsConnectorOfficeProductMetrics`
140140
141 Office Agent activity metrics for a single connector on a given day within one Office product.
141 Office Agent activity metrics for a single connector on a given day within one Office product.
142142
143 - `word: BetaConnectorOfficeProductMetrics`
143 - `connector_display_name: optional string or null`
144144
145 Office Agent activity metrics for a single connector on a given day within one Office product.
145 Human-readable display name for rows whose `connector_name` is an opaque connector id rather than a readable name, resolved at request time from the organization's connectors (including connectors that have since been removed). `connector_name` remains the row's stable key for sorting and pagination, and `filter[]=connector_name:{value}` also matches these rows by display name. Display names are not unique, and the same connector's claude.ai usage can appear under a separate row with a readable `connector_name`. Null when `connector_name` is already a readable name, when the id cannot be resolved to one of the organization's connectors, or when display-name resolution is not enabled for this organization.
146146
147 - `connector_display_name: optional string or null`
147 - `individual_auth_distinct_user_count: optional number or null`
148148
149 Human-readable display name for rows whose `connector_name` is an opaque connector id rather than a readable name, resolved at request time from the organization's connectors (including connectors that have since been removed). `connector_name` remains the row's stable key for sorting and pagination, and `filter[]=connector_name:{value}` also matches these rows by display name. Display names are not unique, and the same connector's claude.ai usage can appear under a separate row with a readable `connector_name`. Null when `connector_name` is already a readable name, when the id cannot be resolved to one of the organization's connectors, or when display-name resolution is not enabled for this organization.
149 Number of distinct users whose use of this connector on the requested day ran on their own individual credential, connected through their own consent flow. Companion bucket to `managed_auth_distinct_user_count`, which carries the measurement, attribution, and null rules. Users whose requests used no stored credential count in neither bucket.
150150
151 - `individual_auth_distinct_user_count: optional number or null`
151 - `managed_auth_distinct_user_count: optional number or null`
152152
153 Number of distinct users whose use of this connector on the requested day ran on their own individual credential, connected through their own consent flow. Companion bucket to `managed_auth_distinct_user_count`, which carries the measurement, attribution, and null rules. Users whose requests used no stored credential count in neither bucket.
153 Number of distinct users whose use of this connector on the requested day ran on Enterprise Managed Auth (an organization-managed credential provisioned through the organization's identity provider), read from the token record each request used. Null, never 0, when managed-auth reporting is not enabled for the organization, the value cannot be attributed to the row, no credentialed requests and no managed-token mint events (a managed credential being provisioned for a user's use of the connector) were observed that day, or the day predates 2026-07-01, the first day the backing data exists (forward-only data, no backfill). When credentialed requests or mint events were observed and attributed, both managed-auth fields populate, reporting 0 for a bucket with no users; the two counts are independent, not a partition — a user whose requests that day used both kinds of credential counts in both. Mint events carry user but not surface attribution, so they count as observed auth activity on `user_id` and `rbac_group_id` cuts — attributed to the user the credential was provisioned for — but never on a cut that references `product` (group or filter). Date-range rollup mode (`starting_date`/`ending_date`) computes both fields exactly over the window — distinct users with at least one qualifying day — when the whole window starts on or after 2026-07-01, with the null-versus-0 and mint-event rules applying with the window in place of the day; a range starting earlier reports every managed-auth field as null, never a partial-window value.
154154
155 - `managed_auth_distinct_user_count: optional number or null`
155 - `product: optional string or null`
156156
157 Number of distinct users whose use of this connector on the requested day ran on Enterprise Managed Auth (an organization-managed credential provisioned through the organization's identity provider), read from the token record each request used. Null, never 0, when managed-auth reporting is not enabled for the organization, the value cannot be attributed to the row, no credentialed requests and no managed-token mint events (a managed credential being provisioned for a user's use of the connector) were observed that day, or the day predates 2026-07-01, the first day the backing data exists (forward-only data, no backfill). When credentialed requests or mint events were observed and attributed, both managed-auth fields populate, reporting 0 for a bucket with no users; the two counts are independent, not a partition — a user whose requests that day used both kinds of credential counts in both. Mint events carry user but not surface attribution, so they count as observed auth activity on `user_id` and `rbac_group_id` cuts — attributed to the user the credential was provisioned for — but never on a cut that references `product` (group or filter). Date-range rollup mode (`starting_date`/`ending_date`) computes both fields exactly over the window — distinct users with at least one qualifying day — when the whole window starts on or after 2026-07-01, with the null-versus-0 and mint-event rules applying with the window in place of the day; a range starting earlier reports every managed-auth field as null, never a partial-window value.
157 Product that produced this row's activity: one of `chat`, `claude_code`, `cowork`, or `office_agent` (the canonical Cost & Usage product naming; an `office_agent` row's per-surface breakdown is in its `office_metrics`). On `/plugins` only `cowork` and `claude_code` occur (the only surfaces with plugin attribution); on `/artifacts` only `chat`, `claude_code`, and `cowork` 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`.
158158
159 - `product: optional string or null`
159 - `rbac_group_id: optional string or null`
160160
161 Product that produced this row's activity: one of `chat`, `claude_code`, `cowork`, or `office_agent` (the canonical Cost & Usage product naming; an `office_agent` row's per-surface breakdown is in its `office_metrics`). On `/plugins` only `cowork` and `claude_code` occur (the only surfaces with plugin attribution); on `/artifacts` only `chat`, `claude_code`, and `cowork` 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`.
161 Tagged RBAC group identifier (`rbac_group_...`), matching the spend-limits API spelling. Present only when the request grouped by `rbac_group_id`.
162162
163 - `rbac_group_id: optional string or null`
163 - `rbac_group_name: optional string or null`
164164
165 Tagged RBAC group identifier (`rbac_group_...`), matching the spend-limits API spelling. Present only when the request grouped by `rbac_group_id`.
165 Resolved RBAC group display name, alongside `rbac_group_id` when name resolution is available. Null if the group has been deleted or its name could not be resolved; `rbac_group_id` remains the stable key.
166166
167 - `rbac_group_name: optional string or null`
167 - `read_call_count: optional number or null`
168168
169 Resolved RBAC group display name, alongside `rbac_group_id` when name resolution is available. Null if the group has been deleted or its name could not be resolved; `rbac_group_id` remains the stable key.
169 Number of connector tool calls on the requested day whose trusted read-only annotation marked them read-only. Call count, not distinct users. Every call recorded on a classified surface lands in exactly one of `read_call_count`, `write_call_count`, or `unclassified_call_count`, so the three sum to the day's classified calls. Classification is forward-only per surface: claude.ai from 2026-06-01, Claude Code from 2026-05-30, Claude in Office from 2026-05-29, Cowork from 2026-06-02 (Cowork clients predating annotation forwarding land in `unclassified_call_count`). Null, never 0, when the value cannot be stated: the read/write split is not enabled for this organization, or the day predates 2026-05-29. For a date-range total, sum the per-day values, but treat a window that extends before 2026-05-29 as null rather than summing only its covered days — date-range rollup mode (`starting_date`/`ending_date`) applies both rules server-side.
170170
171 - `read_call_count: optional number or null`
171 - `unclassified_call_count: optional number or null`
172172
173 Number of connector tool calls on the requested day whose trusted read-only annotation marked them read-only. Call count, not distinct users. Every call recorded on a classified surface lands in exactly one of `read_call_count`, `write_call_count`, or `unclassified_call_count`, so the three sum to the day's classified calls. Classification is forward-only per surface: claude.ai from 2026-06-01, Claude Code from 2026-05-30, Claude in Office from 2026-05-29, Cowork from 2026-06-02 (Cowork clients predating annotation forwarding land in `unclassified_call_count`). Null, never 0, when the value cannot be stated: the read/write split is not enabled for this organization, or the day predates 2026-05-29. For a date-range total, sum the per-day values, but treat a window that extends before 2026-05-29 as null rather than summing only its covered days — date-range rollup mode (`starting_date`/`ending_date`) applies both rules server-side.
173 Number of connector tool calls on the requested day with no trusted read-only annotation — the annotation is optional in the MCP spec and is discarded when connector access controls are active, so unclassified calls are common. This field shows how much of the day's classified activity the read/write split actually covers. Call count, not distinct users. One of the three call-classification buckets; see `read_call_count` for the per-surface data-start dates, null conditions, and date-range guidance.
174174
175 - `unclassified_call_count: optional number or null`
175 - `user_id: optional string or null`
176176
177 Number of connector tool calls on the requested day with no trusted read-only annotation — the annotation is optional in the MCP spec and is discarded when connector access controls are active, so unclassified calls are common. This field shows how much of the day's classified activity the read/write split actually covers. Call count, not distinct users. One of the three call-classification buckets; see `read_call_count` for the per-surface data-start dates, null conditions, and date-range guidance.
177 Tagged user identifier (e.g. `user_...`). Present only when the request grouped by `user_id`.
178178
179 - `user_id: optional string or null`
179 - `write_call_count: optional number or null`
180180
181 Tagged user identifier (e.g. `user_...`). Present only when the request grouped by `user_id`.
181 Number of connector tool calls on the requested day whose trusted read-only annotation marked them not read-only. Call count, not distinct users. One of the three call-classification buckets; see `read_call_count` for the per-surface data-start dates, null conditions, and date-range guidance.
182182
183 - `write_call_count: optional number or null`
183- `next_page: string or null`
184184
185 Number of connector tool calls on the requested day whose trusted read-only annotation marked them not read-only. Call count, not distinct users. One of the three call-classification buckets; see `read_call_count` for the per-surface data-start dates, null conditions, and date-range guidance.
185 Opaque cursor for the next page, or null if no more results
186186
187 - `next_page: string or null`
188
189 Opaque cursor for the next page, or null if no more results
190
191187### Example
192188
193189```bash
from line 238
242238 "next_page": "next_page"
243239}
244240```
245
246## Domain types
247
248### Beta Connector Usage
249
250- `BetaConnectorUsage object`
251
252 Response for GET /v1/organizations/analytics/connectors.
253
254 - `data: array of object`
255
256 - `chat_metrics: object`
257
258 Claude.ai activity metrics for a single connector on a given day.
259
260 - `distinct_conversation_connector_used_count: number or null`
261
262 Number of distinct conversations in which the connector was used. Approximate (HLL, typical error <2%) in date-range mode. Null on aggregated rows where a distinct count cannot be computed.
263
264 - `claude_code_metrics: object`
265
266 Claude Code activity metrics for a single connector on a given day.
267
268 - `distinct_session_connector_used_count: number or null`
269
270 Number of distinct Claude Code sessions in which the connector was used. Approximate (HLL, typical error <2%) in date-range mode. Null on aggregated rows where a distinct count cannot be computed.
271
272 - `connector_name: string`
273
274 Name of the connector. Some rows carry an opaque connector id here instead of a readable name; `connector_display_name` holds the resolved name for those rows.
275
276 - `cowork_metrics: object`
277
278 Cowork activity metrics for a single connector on a given day.
279
280 - `distinct_session_connector_used_count: number or null`
281
282 Number of distinct Cowork sessions in which the connector was used. Approximate (HLL, typical error <2%) in date-range mode. Null on aggregated rows where a distinct count cannot be computed.
283
284 - `distinct_user_count: number`
285
286 Number of distinct users who used the connector 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.
287
288 - `office_metrics: object`
289
290 Office Agent activity metrics for a single connector on a given day, broken out by Office product.
291
292 - `excel: BetaConnectorOfficeProductMetrics`
293
294 Office Agent activity metrics for a single connector on a given day within one Office product.
295
296 - `distinct_session_connector_used_count: number or null`
297
298 Number of distinct Office Agent sessions in which the connector was used. Approximate (HLL, typical error <2%) in date-range mode. Null on aggregated rows where a distinct count cannot be computed.
299
300 - `outlook: BetaConnectorOfficeProductMetrics`
301
302 Office Agent activity metrics for a single connector on a given day within one Office product.
303
304 - `powerpoint: BetaConnectorOfficeProductMetrics`
305
306 Office Agent activity metrics for a single connector on a given day within one Office product.
307
308 - `word: BetaConnectorOfficeProductMetrics`
309
310 Office Agent activity metrics for a single connector on a given day within one Office product.
311
312 - `connector_display_name: optional string or null`
313
314 Human-readable display name for rows whose `connector_name` is an opaque connector id rather than a readable name, resolved at request time from the organization's connectors (including connectors that have since been removed). `connector_name` remains the row's stable key for sorting and pagination, and `filter[]=connector_name:{value}` also matches these rows by display name. Display names are not unique, and the same connector's claude.ai usage can appear under a separate row with a readable `connector_name`. Null when `connector_name` is already a readable name, when the id cannot be resolved to one of the organization's connectors, or when display-name resolution is not enabled for this organization.
315
316 - `individual_auth_distinct_user_count: optional number or null`
317
318 Number of distinct users whose use of this connector on the requested day ran on their own individual credential, connected through their own consent flow. Companion bucket to `managed_auth_distinct_user_count`, which carries the measurement, attribution, and null rules. Users whose requests used no stored credential count in neither bucket.
319
320 - `managed_auth_distinct_user_count: optional number or null`
321
322 Number of distinct users whose use of this connector on the requested day ran on Enterprise Managed Auth (an organization-managed credential provisioned through the organization's identity provider), read from the token record each request used. Null, never 0, when managed-auth reporting is not enabled for the organization, the value cannot be attributed to the row, no credentialed requests and no managed-token mint events (a managed credential being provisioned for a user's use of the connector) were observed that day, or the day predates 2026-07-01, the first day the backing data exists (forward-only data, no backfill). When credentialed requests or mint events were observed and attributed, both managed-auth fields populate, reporting 0 for a bucket with no users; the two counts are independent, not a partition — a user whose requests that day used both kinds of credential counts in both. Mint events carry user but not surface attribution, so they count as observed auth activity on `user_id` and `rbac_group_id` cuts — attributed to the user the credential was provisioned for — but never on a cut that references `product` (group or filter). Date-range rollup mode (`starting_date`/`ending_date`) computes both fields exactly over the window — distinct users with at least one qualifying day — when the whole window starts on or after 2026-07-01, with the null-versus-0 and mint-event rules applying with the window in place of the day; a range starting earlier reports every managed-auth field as null, never a partial-window value.
323
324 - `product: optional string or null`
325
326 Product that produced this row's activity: one of `chat`, `claude_code`, `cowork`, or `office_agent` (the canonical Cost & Usage product naming; an `office_agent` row's per-surface breakdown is in its `office_metrics`). On `/plugins` only `cowork` and `claude_code` occur (the only surfaces with plugin attribution); on `/artifacts` only `chat`, `claude_code`, and `cowork` 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`.
327
328 - `rbac_group_id: optional string or null`
329
330 Tagged RBAC group identifier (`rbac_group_...`), matching the spend-limits API spelling. Present only when the request grouped by `rbac_group_id`.
331
332 - `rbac_group_name: optional string or null`
333
334 Resolved RBAC group display name, alongside `rbac_group_id` when name resolution is available. Null if the group has been deleted or its name could not be resolved; `rbac_group_id` remains the stable key.
335
336 - `read_call_count: optional number or null`
337
338 Number of connector tool calls on the requested day whose trusted read-only annotation marked them read-only. Call count, not distinct users. Every call recorded on a classified surface lands in exactly one of `read_call_count`, `write_call_count`, or `unclassified_call_count`, so the three sum to the day's classified calls. Classification is forward-only per surface: claude.ai from 2026-06-01, Claude Code from 2026-05-30, Claude in Office from 2026-05-29, Cowork from 2026-06-02 (Cowork clients predating annotation forwarding land in `unclassified_call_count`). Null, never 0, when the value cannot be stated: the read/write split is not enabled for this organization, or the day predates 2026-05-29. For a date-range total, sum the per-day values, but treat a window that extends before 2026-05-29 as null rather than summing only its covered days — date-range rollup mode (`starting_date`/`ending_date`) applies both rules server-side.
339
340 - `unclassified_call_count: optional number or null`
341
342 Number of connector tool calls on the requested day with no trusted read-only annotation — the annotation is optional in the MCP spec and is discarded when connector access controls are active, so unclassified calls are common. This field shows how much of the day's classified activity the read/write split actually covers. Call count, not distinct users. One of the three call-classification buckets; see `read_call_count` for the per-surface data-start dates, null conditions, and date-range guidance.
343
344 - `user_id: optional string or null`
345
346 Tagged user identifier (e.g. `user_...`). Present only when the request grouped by `user_id`.
347
348 - `write_call_count: optional number or null`
349
350 Number of connector tool calls on the requested day whose trusted read-only annotation marked them not read-only. Call count, not distinct users. One of the three call-classification buckets; see `read_call_count` for the per-surface data-start dates, null conditions, and date-range guidance.
351
352 - `next_page: string or null`
353
354 Opaque cursor for the next page, or null if no more results
355241
No line in this hunk matches that.