Connectors changedapi/admin/analytics/connectors
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+31added
Lines−24removed
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: Connectors
3url: https://platform.claude.com/docs/en/api/admin/analytics/connectors
4---
5
61# Connectors
72
83## Get Connector Usage
94
10**get** `/v1/organizations/analytics/connectors`
5**GET** `/v1/organizations/analytics/connectors`
116
127Get per-connector usage for a given day, with cursor-based pagination.
138
from line 15
2015organizations on a Claude Enterprise plan. Requires an API key with the
2116`read:analytics` scope.
2217
23### Query Parameters
18### Query parameters
2419
2520- `date: optional string`
2621
2722 UTC date in YYYY-MM-DD format. The day to get connector usage 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.
2823
24 format: date
25
2926- `ending_date: optional string`
3027
3128 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.
3229
30 format: date
31
3332- `filter: optional array of string`
3433
3534 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: connector_name, product, rbac_group_id, user_id. Value forms: connector_name matches case-insensitively, a display name such as 'GitHub MCP' also matches its normalized stored form ('github'), and for rows whose connector_name is an opaque connector id the connector's display name (connector_display_name) also matches; product is one of chat, claude_code, cowork, or office_agent; 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.
3635
36 maxItems: 100
37
3738- `group_by: optional array of "product" or "rbac_group_id" or "user_id"`
3839
3940 Dimensions to break results out by (e.g. group_by[]=user_id). Supported on this endpoint: product, 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.
4041
42 maxItems: 100
43
4144 - `"product"`
4245
4346 - `"rbac_group_id"`
from line 51
4851
4952 Number of results per page (1-1000, default 100).
5053
54 minimum: 1, maximum: 1000
55
5156- `order: optional "asc" or "desc"`
5257
5358 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 73
6873
6974 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.
7075
76 format: date
77
7178### Returns
7279
73- `ConnectorUsage object { data, next_page }`
80- `ConnectorUsage object`
7481
7582 Response for GET /v1/organizations/analytics/connectors.
7683
77 - `data: array of object { chat_metrics, claude_code_metrics, connector_name, 13 more }`
84 - `data: array of object`
7885
79 - `chat_metrics: object { distinct_conversation_connector_used_count }`
86 - `chat_metrics: object`
8087
8188 Claude.ai activity metrics for a single connector on a given day.
8289
from line 91
8491
8592 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.
8693
87 - `claude_code_metrics: object { distinct_session_connector_used_count }`
94 - `claude_code_metrics: object`
8895
8996 Claude Code activity metrics for a single connector on a given day.
9097
from line 103
96103
97104 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.
98105
99 - `cowork_metrics: object { distinct_session_connector_used_count }`
106 - `cowork_metrics: object`
100107
101108 Cowork activity metrics for a single connector on a given day.
102109
from line 115
108115
109116 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.
110117
111 - `office_metrics: object { excel, outlook, powerpoint, word }`
118 - `office_metrics: object`
112119
113120 Office Agent activity metrics for a single connector on a given day, broken out by Office product.
114121
from line 185
178185
179186### Example
180187
181```http
188```bash
182189curl https://api.anthropic.com/v1/organizations/analytics/connectors \
183190 -H 'anthropic-version: 2023-06-01' \
184191 -H "X-Api-Key: $ANTHROPIC_ADMIN_API_KEY"
185192```
186193
187#### Response
194#### Response (200)
188195
189196```json
190197{
from line 238
231238}
232239```
233240
234## Domain Types
241## Domain types
235242
236243### Connector Usage
237244
238- `ConnectorUsage object { data, next_page }`
245- `ConnectorUsage object`
239246
240247 Response for GET /v1/organizations/analytics/connectors.
241248
242 - `data: array of object { chat_metrics, claude_code_metrics, connector_name, 13 more }`
249 - `data: array of object`
243250
244 - `chat_metrics: object { distinct_conversation_connector_used_count }`
251 - `chat_metrics: object`
245252
246253 Claude.ai activity metrics for a single connector on a given day.
247254
from line 256
249256
250257 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.
251258
252 - `claude_code_metrics: object { distinct_session_connector_used_count }`
259 - `claude_code_metrics: object`
253260
254261 Claude Code activity metrics for a single connector on a given day.
255262
from line 268
261268
262269 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.
263270
264 - `cowork_metrics: object { distinct_session_connector_used_count }`
271 - `cowork_metrics: object`
265272
266273 Cowork activity metrics for a single connector on a given day.
267274
from line 280
273280
274281 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.
275282
276 - `office_metrics: object { excel, outlook, powerpoint, word }`
283 - `office_metrics: object`
277284
278285 Office Agent activity metrics for a single connector on a given day, broken out by Office product.
279286
No line in this hunk matches that.