Get Plugin Usage changedapi/admin/analytics/plugins/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+23added
Lines−16removed
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 Plugin Usage ## Query parameters ## Returns ## Example ### Response (200) ## Get Plugin Usage ### Query Parameters ### Returns ### Example #### Response
The whole hunk
from line 1, old and new numbered
/
from line 1
1---
2title: Get Plugin Usage
3url: https://platform.claude.com/docs/en/api/admin/analytics/plugins/list
4---
1# Get Plugin Usage
52
6## Get Plugin Usage
3**GET** `/v1/organizations/analytics/plugins`
74
8**get** `/v1/organizations/analytics/plugins`
9
105Get per-plugin install + invocation usage for a given day, with pagination.
116
127Returns plugin usage metrics for the organization across Cowork and Claude
from line 16
2116`read:analytics` scope. `starting_date` / `ending_date` select
2217range-rollup mode like /skills.
2318
24### Query Parameters
19## Query parameters
2520
2621- `date: optional string`
2722
2823 UTC date in YYYY-MM-DD format. The day to get plugin 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.
2924
25 format: date
26
3027- `ending_date: optional string`
3128
3229 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.
3330
31 format: date
32
3433- `filter: optional array of string`
3534
3635 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: plugin_name, product, rbac_group_id, user_id. Value forms: plugin_name matches case-insensitively; product is claude_code or cowork (the only surfaces with plugin attribution); 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.
3736
37 maxItems: 100
38
3839- `group_by: optional array of "product" or "rbac_group_id" or "user_id"`
3940
4041 Dimensions to break results out by (e.g. group_by[]=user_id). Supported on this endpoint: product, rbac_group_id, user_id. On this endpoint product takes the values claude_code or cowork only (the surfaces with plugin attribution). 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.
4142
43 maxItems: 100
44
4245 - `"product"`
4346
4447 - `"rbac_group_id"`
from line 52
4952
5053 Number of results per page (1-1000, default 100).
5154
55 minimum: 1, maximum: 1000
56
5257- `order: optional "asc" or "desc"`
5358
5459 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 74
6974
7075 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.
7176
72### Returns
77 format: date
7378
74- `PluginUsage object { data, next_page }`
79## Returns
7580
81- `PluginUsage object`
82
7683 Response for GET /v1/organizations/analytics/plugins.
7784
78 - `data: array of object { claude_code_metrics, cowork_metrics, distinct_user_count, 8 more }`
85 - `data: array of object`
7986
80 - `claude_code_metrics: object { distinct_session_plugin_used_count }`
87 - `claude_code_metrics: object`
8188
8289 Claude Code activity metrics for a single plugin on a given day.
8390
from line 92
8592
8693 Number of distinct Claude Code sessions in which the plugin was invoked. Null on aggregated rows where a distinct count cannot be computed.
8794
88 - `cowork_metrics: object { distinct_session_plugin_used_count }`
95 - `cowork_metrics: object`
8996
9097 Cowork activity metrics for a single plugin on a given day.
9198
from line 140
133140
134141 Opaque cursor for the next page, or null if no more results
135142
136### Example
143## Example
137144
138```http
145```bash
139146curl https://api.anthropic.com/v1/organizations/analytics/plugins \
140147 -H 'anthropic-version: 2023-06-01' \
141148 -H "X-Api-Key: $ANTHROPIC_ADMIN_API_KEY"
142149```
143150
144#### Response
151### Response (200)
145152
146153```json
147154{
No line in this hunk matches that.