Approves or denies one pending Budget limit increase request. A successful approval also applies the Budget limit change.

The API key's creator must retain Budget-management access for the target Workspace; write:budgets alone is insufficient. The approved amountUsd is the final limit, not an increment, and must exceed the current limit. An amount at or below the current limit returns 409 (conflict).

For a workspace_group_limit request, approval increases the shared limit of the group identified by groupId, not the requester's individual limit. Other applicable usage limits remain in effect.

Send the list item's reviewEtag or the detail response's strong ETag unchanged in If-Match. A new event on the request makes an earlier review token stale; changes to the requester's profile, Workspace details, or group name alone do not. A missing header returns 428 (precondition_required); a malformed or weak value returns 400 (invalid_request); a stale version returns 412 (precondition_failed); and a current tag on a request that is no longer pending returns 409 (request_already_resolved). A concurrent budget update can instead return 409 (budget_update_in_progress) with Retry-After: 1.

A successful review returns 200 with the updated request, its public history, a new ETag, and Cache-Control: no-store, no-transform. Both requester and workspace are always null in review responses. Group requests retain groupId, but group is also null, even when the key also has read:*. The ETag can differ from a subsequent detail GET's ETag at the same request version. Either token can be used for a review; use the detail GET's ETag for conditional detail reads. This operation returns the updated request, not a separate review resource.

A read made immediately after a review can briefly return the request's previous state. If the response is lost, wait briefly and read the request again. If it is resolved, do not retry; if still pending, retry only if the decision is still intended and use the latest read's ETag.

{
  "data": {
    "createdAt": "2026-08-04T10:00:00Z",
    "updatedAt": "2026-08-04T10:05:00Z",
    "events": [
      {
        "occurredAt": "2026-08-04T10:00:00Z"
      }
    ]
  }
}