Get Messages Usage Report changedapi/beta/organization/usage_report/retrieve_messages
Nearest release: v2.1.322, published 2 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+5added
Lines−1removed
From line
42
where the diff opens
First seen
10 Sep 2026
this site's first read of the page
Recorded edits17to this page, all time
The whole hunk
from line 42, old and new numbered
/
from line 42
4242
4343- `context_window: optional array of BetaAnalyticsContextWindow`
4444
45 Restrict usage returned to the specified context window(s).
45 Restrict usage returned to the specified context window(s). See the `context_window` response field for how a request is classified.
4646
4747 - `"0-200k"`
4848
from line 253
253253
254254 - `"webhooks-2026-10-07"`
255255
256 - `"admin-user-sign-out-2026-10-08"`
257
256258 - `"message-threads-2026-08-12"`
257259
258260 - `"analytics-usage-cost-2026-08-24"`
from line 310
308310 - `context_window: BetaAnalyticsContextWindow or null`
309311
310312 Context window used. `null` if not grouping by context window.
313
314 A request is classified by comparing its prompt size with its model's own long-context boundary, the same boundary that billing uses. The two values are labels for the two classes, not literal ranges: where a model's boundary is below 200k, a request whose prompt exceeds that boundary is reported under `200k-1M`, and a `0-200k` filter does not return it. Where the report cannot determine a model's boundary, it uses 200k instead. Hourly usage stored before this classification took effect keeps its earlier value until it expires. Billed amounts are not affected.
311315
312316 - `"0-200k"`
313317
No line in this hunk matches that.