Get Connector Usage changedapi/admin/analytics/connectors/list
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+29added
Lines−22removed
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
# Get Connector Usage ## Query parameters ## Returns ## Example ### Response (200) ## Get Connector Usage ### Query Parameters ### Returns ### Example #### Response
The whole hunk
from line 1, old and new numbered
/
from line 1
1---
2title: Get Connector Usage
3url: https://platform.claude.com/docs/en/api/admin/analytics/connectors/list
4---
1# Get Connector Usage
52
6## Get Connector Usage
3**GET** `/v1/organizations/analytics/connectors`
74
8**get** `/v1/organizations/analytics/connectors`
9
105Get per-connector usage for a given day, with cursor-based pagination.
116
127Returns connector usage metrics for the organization, sorted by connector
from line 13
1813organizations on a Claude Enterprise plan. Requires an API key with the
1914`read:analytics` scope.
2015
21### Query Parameters
16## Query parameters
2217
2318- `date: optional string`
2419
2520 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.
2621
22 format: date
23
2724- `ending_date: optional string`
2825
2926 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.
3027
28 format: date
29
3130- `filter: optional array of string`
3231
3332 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.
3433
34 maxItems: 100
35
3536- `group_by: optional array of "product" or "rbac_group_id" or "user_id"`
3637
3738 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.
3839
40 maxItems: 100
41
3942 - `"product"`
4043
4144 - `"rbac_group_id"`
from line 49
4649
4750 Number of results per page (1-1000, default 100).
4851
52 minimum: 1, maximum: 1000
53
4954- `order: optional "asc" or "desc"`
5055
5156 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 71
6671
6772 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.
6873
69### Returns
74 format: date
7075
71- `ConnectorUsage object { data, next_page }`
76## Returns
7277
78- `ConnectorUsage object`
79
7380 Response for GET /v1/organizations/analytics/connectors.
7481
75 - `data: array of object { chat_metrics, claude_code_metrics, connector_name, 13 more }`
82 - `data: array of object`
7683
77 - `chat_metrics: object { distinct_conversation_connector_used_count }`
84 - `chat_metrics: object`
7885
7986 Claude.ai activity metrics for a single connector on a given day.
8087
from line 89
8289
8390 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.
8491
85 - `claude_code_metrics: object { distinct_session_connector_used_count }`
92 - `claude_code_metrics: object`
8693
8794 Claude Code activity metrics for a single connector on a given day.
8895
from line 101
94101
95102 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.
96103
97 - `cowork_metrics: object { distinct_session_connector_used_count }`
104 - `cowork_metrics: object`
98105
99106 Cowork activity metrics for a single connector on a given day.
100107
from line 113
106113
107114 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.
108115
109 - `office_metrics: object { excel, outlook, powerpoint, word }`
116 - `office_metrics: object`
110117
111118 Office Agent activity metrics for a single connector on a given day, broken out by Office product.
112119
from line 181
174181
175182 Opaque cursor for the next page, or null if no more results
176183
177### Example
184## Example
178185
179```http
186```bash
180187curl https://api.anthropic.com/v1/organizations/analytics/connectors \
181188 -H 'anthropic-version: 2023-06-01' \
182189 -H "X-Api-Key: $ANTHROPIC_ADMIN_API_KEY"
183190```
184191
185#### Response
192### Response (200)
186193
187194```json
188195{
No line in this hunk matches that.