spend-limits-api changedmanage-claude/spend-limits-api
Nearest release: v2.1.250, published an hour 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+37added
Lines−4removed
From line
197
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits13to this page, all time
### Temporarily raise a member's spend limit during an incident
The whole hunk
from line 197, old and new numbered
/
from line 197
197197For complete parameter details and response schemas, see [List spend limit increase requests](https://platform.claude.com/docs/en/api/admin/spend_limits/increase_requests/list) in the API reference.
198198
199199```bash cURL
200curl "https://api.anthropic.com/v1/organizations/spend_limit_increase_requests?status[]=pending&limit=50" \
200curl --globoff "https://api.anthropic.com/v1/organizations/spend_limit_increase_requests?status[]=pending&limit=50" \
201201 --header "x-api-key: $ANTHROPIC_ADMIN_KEY"
202202```
203203
from line 242
242242
243243## Example workflows
244244
245These workflows combine the Spend Limits API with the [Analytics APIs](https://platform.claude.com/docs/en/manage-claude/analytics-api) cost endpoints. The Analytics cost endpoints are designed for organization-wide spend reporting across a date range. `GET /spend_limits/effective` returns the cap that currently applies to each member. Start a sweep with Analytics to discover which members to look at, then read their current caps with `/effective`.
245Some of these workflows combine the Spend Limits API with the [Analytics APIs](https://platform.claude.com/docs/en/manage-claude/analytics-api) cost endpoints. The Analytics cost endpoints are designed for organization-wide spend reporting across a date range. `GET /spend_limits/effective` returns the cap that currently applies to each member. Start a sweep with Analytics to discover which members to look at, then read their current caps with `/effective`.
246246
247247Spend Limits endpoints require the `spend_limits` scopes and Analytics cost endpoints require `read:analytics`; see [Analytics APIs](https://platform.claude.com/docs/en/manage-claude/analytics-api) for how to provision access. All monetary values on both are decimal strings in minor units (cents). Both APIs paginate with an opaque cursor. Set an explicit `limit` and page through `next_page` until it's `null` to cover the whole organization.
248248
from line 253
2532531. List pending requests:
254254
255255 ```bash cURL
256 curl "https://api.anthropic.com/v1/organizations/spend_limit_increase_requests?status[]=pending&limit=100" \
256 curl --globoff "https://api.anthropic.com/v1/organizations/spend_limit_increase_requests?status[]=pending&limit=100" \
257257 --header "x-api-key: $ANTHROPIC_ADMIN_KEY"
258258 ```
259259
from line 288
2882882. For the top spenders (or everyone above a dollar threshold), fetch effective caps in batches:
289289
290290 ```bash cURL
291 curl "https://api.anthropic.com/v1/organizations/spend_limits/effective?user_ids[]=user_01Ab...&user_ids[]=user_01Cd...&limit=100" \
291 curl --globoff "https://api.anthropic.com/v1/organizations/spend_limits/effective?user_ids[]=user_01Ab...&user_ids[]=user_01Cd...&limit=100" \
292292 --header "x-api-key: $ANTHROPIC_ADMIN_KEY"
293293 ```
294294
from line 314
3143142. Group rows by `actor.user_id`. For each member, sum the most recent seven days and the prior seven days. Flag members whose recent week exceeds the prior week by your chosen multiple (for example, three). Recent-day cost is provisional and can be revised upward; for repeatable comparisons, set `ending_at` at or before a previously returned `data_refreshed_at` (see [Data availability and freshness](https://platform.claude.com/docs/en/manage-claude/analytics-api#data-availability-and-freshness)).
315315
3163163. Act on flagged members: adjust the cap with `POST /v1/organizations/spend_limits`, or reach out.
317
318### Temporarily raise a member's spend limit during an incident
319
320Give an incident responder room to work while an incident is open: raise their spend cap when the incident starts, and roll it back after the incident closes. Gate the raise on your incident management system, for example by requiring a live incident ID with the member assigned to it.
321
3221. Read the member's current cap, and record it for the rollback:
323
324 ```bash cURL
325 curl --globoff "https://api.anthropic.com/v1/organizations/spend_limits/effective?user_ids[]=user_01AbCdEfGh&period[]=monthly" \
326 --header "x-api-key: $ANTHROPIC_ADMIN_KEY"
327 ```
328
3292. Raise the cap:
330
331 ```bash cURL
332 curl --request POST "https://api.anthropic.com/v1/organizations/spend_limits" \
333 --header "content-type: application/json" \
334 --header "x-api-key: $ANTHROPIC_ADMIN_KEY" \
335 --data '{"scope": {"type": "user", "user_id": "user_01AbCdEfGh"}, "amount": "500000", "period": "monthly"}'
336 ```
337
3383. If responders need broader access during an incident, pre-provision an incident-responders group whose [custom role](https://platform.claude.com/docs/en/manage-claude/user-management#custom-roles) grants it, and add the member for the duration:
339
340 ```bash cURL
341 curl --request POST "https://api.anthropic.com/v1/organizations/rbac_groups/rbac_group_01UvWxYzAbCdEfGhIjKlMn/members" \
342 --header "content-type: application/json" \
343 --header "x-api-key: $ANTHROPIC_ADMIN_KEY" \
344 --data '{"user_id": "user_01AbCdEfGh"}'
345 ```
346
347 See [User management](https://platform.claude.com/docs/en/manage-claude/user-management#groups) for the group endpoints.
348
3494. When your incident system marks the incident closed, roll both changes back: restore the spend limit you recorded in step 1 (or delete the override with `DELETE /v1/organizations/spend_limits/{spend_limit_id}` if the member had none), and remove the member from the group with `DELETE /v1/organizations/rbac_groups/{group_id}/members/{user_id}`.
317350
318351## Frequently asked questions
319352
No line in this hunk matches that.