Follow Discord
Sweep 02 Oct 2026 · 18:55Z Build v2.1.288 509 read Stable v2.1.285 Latest v2.1.288 Next v2.1.288 Feeds RSS JSON llms.txt llms-full.txt Unofficial
One change · api

Get Connector Usage changedapi/beta/organization/analytics/connectors/list

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−102removed
From line 80 where the diff opens
First seen 10 Sep 2026 this site's first read of the page
Recorded edits2to this page, all time

The whole hunk

from line 80, old and new numbered
/
lines
from line 80
8080 
8181## Returns
8282 
83- `BetaConnectorUsage object`
83- `data: array of BetaAnalyticsConnectorActivity`
8484 
85 Response for GET /v1/organizations/analytics/connectors.
85 - `chat_metrics: BetaAnalyticsConnectorChatMetrics`
8686 
87 - `data: array of object`
87 Claude.ai activity metrics for a single connector on a given day.
8888 
89 - `chat_metrics: object`
89 - `distinct_conversation_connector_used_count: number or null`
9090 
91 Claude.ai activity metrics for a single connector on a given day.
91 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.
9292 
93 - `distinct_conversation_connector_used_count: number or null`
93 - `claude_code_metrics: BetaAnalyticsConnectorClaudeCodeMetrics`
9494 
95 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.
95 Claude Code activity metrics for a single connector on a given day.
9696 
97 - `claude_code_metrics: object`
97 - `distinct_session_connector_used_count: number or null`
9898 
99 Claude Code activity metrics for a single connector on a given day.
99 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.
100100 
101 - `distinct_session_connector_used_count: number or null`
101 - `connector_name: string`
102102 
103 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.
103 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.
104104 
105 - `connector_name: string`
105 - `cowork_metrics: BetaAnalyticsConnectorCoworkMetrics`
106106 
107 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.
107 Cowork activity metrics for a single connector on a given day.
108108 
109 - `cowork_metrics: object`
109 - `distinct_session_connector_used_count: number or null`
110110 
111 Cowork activity metrics for a single connector on a given day.
111 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.
112112 
113 - `distinct_session_connector_used_count: number or null`
113 - `distinct_user_count: number`
114114 
115 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.
115 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.
116116 
117 - `distinct_user_count: number`
117 - `office_metrics: BetaAnalyticsConnectorOfficeMetrics`
118118 
119 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.
119 Office Agent activity metrics for a single connector on a given day, broken out by Office product.
120120 
121 - `office_metrics: object`
121 - `excel: BetaAnalyticsConnectorOfficeProductMetrics`
122122 
123 Office Agent activity metrics for a single connector on a given day, broken out by Office product.
123 Office Agent activity metrics for a single connector on a given day within one Office product.
124124 
125 - `excel: BetaConnectorOfficeProductMetrics`
125 - `distinct_session_connector_used_count: number or null`
126126 
127 Office Agent activity metrics for a single connector on a given day within one Office product.
127 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.
128128 
129 - `distinct_session_connector_used_count: number or null`
129 - `outlook: BetaAnalyticsConnectorOfficeProductMetrics`
130130 
131 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.
131 Office Agent activity metrics for a single connector on a given day within one Office product.
132132 
133 - `outlook: BetaConnectorOfficeProductMetrics`
133 - `powerpoint: BetaAnalyticsConnectorOfficeProductMetrics`
134134 
135 Office Agent activity metrics for a single connector on a given day within one Office product.
135 Office Agent activity metrics for a single connector on a given day within one Office product.
136136 
137 - `powerpoint: BetaConnectorOfficeProductMetrics`
137 - `word: BetaAnalyticsConnectorOfficeProductMetrics`
138138 
139 Office Agent activity metrics for a single connector on a given day within one Office product.
139 Office Agent activity metrics for a single connector on a given day within one Office product.
140140 
141 - `word: BetaConnectorOfficeProductMetrics`
141 - `connector_display_name: optional string or null`
142142 
143 Office Agent activity metrics for a single connector on a given day within one Office product.
143 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.
144144 
145 - `connector_display_name: optional string or null`
145 - `individual_auth_distinct_user_count: optional number or null`
146146 
147 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.
147 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.
148148 
149 - `individual_auth_distinct_user_count: optional number or null`
149 - `managed_auth_distinct_user_count: optional number or null`
150150 
151 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.
151 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.
152152 
153 - `managed_auth_distinct_user_count: optional number or null`
153 - `product: optional string or null`
154154 
155 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.
155 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`.
156156 
157 - `product: optional string or null`
157 - `rbac_group_id: optional string or null`
158158 
159 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`.
159 Tagged RBAC group identifier (`rbac_group_...`), matching the spend-limits API spelling. Present only when the request grouped by `rbac_group_id`.
160160 
161 - `rbac_group_id: optional string or null`
161 - `rbac_group_name: optional string or null`
162162 
163 Tagged RBAC group identifier (`rbac_group_...`), matching the spend-limits API spelling. Present only when the request grouped by `rbac_group_id`.
163 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.
164164 
165 - `rbac_group_name: optional string or null`
165 - `read_call_count: optional number or null`
166166 
167 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.
167 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.
168168 
169 - `read_call_count: optional number or null`
169 - `unclassified_call_count: optional number or null`
170170 
171 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.
171 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.
172172 
173 - `unclassified_call_count: optional number or null`
173 - `user_id: optional string or null`
174174 
175 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.
175 Tagged user identifier (e.g. `user_...`). Present only when the request grouped by `user_id`.
176176 
177 - `user_id: optional string or null`
177 - `write_call_count: optional number or null`
178178 
179 Tagged user identifier (e.g. `user_...`). Present only when the request grouped by `user_id`.
179 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.
180180 
181 - `write_call_count: optional number or null`
181- `next_page: string or null`
182182 
183 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.
184 
185 - `next_page: string or null`
186 
187 Opaque cursor for the next page, or null if no more results
183 Opaque cursor for the next page, or null if no more results
188184 
189185## Example
190186 
Feedback