Resolve a billing limit-increase request
Update a pending request with an approval decision or denial. Requires admin.usage.limit_increase_requests:write and current billing edit permission. A pending request can record an approved positive increase amount or be denied with an optional resolution note. PERIOD approval retains the request's stored month and requires the current UTC month; expired approvals return 409 before mutation or approval writes. A successful approval write triggers spend-limit cache refresh before reload; refresh failure logs a warning without failing the decision. The existing backend consumes eligible USER current-period grants to raise enforcement headroom without changing standing rules. This does not add capacity for agents or other unsupported targets, integrate usage settings, or promise new delivery or atomicity guarantees. Supported token issuance, experimental opt-in, and request-more enablement are required. Missing opt-in or a disabled flag returns 404. Once enabled and opted in, ONGOING returns typed 503 without reading or modifying the request; its private policy preparation is not shared with this adapter. Use the existing app operation for ongoing user approvals.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 408
- 409
- 413
- 429
- 500
- 503
The resolved request in its current stored state.
Invalid input, with field-level validation details when available.
Authentication is missing or invalid.
The caller lacks the required scope or current resource permission.
Experimental opt-in is missing, the enablement flag is disabled, or the request is missing or inaccessible.
The operation timed out.
The request conflicts with the current stored request state.
The request exceeds the supported body size.
The caller exceeded the request rate limit.
An unexpected internal error prevented completion.
The operation is unsupported or temporarily unavailable; ONGOING approval is unsupported.