The spend limit request object
⚠️
Preview — this feature is being built; the design below is the spec.
The spend_limit_request object as the API returns it. Every field below appears in every response that returns this object; fields with no value are null rather than missing.
Example
{
"id": "slr_01JCQ3R5T7V9X1Z3B5D7",
"type": "spend_limit_request",
"workspace_id": "wrkspc_01JC0A2C4E6G8J0L2N4Q",
"requested_by": "user_01J9Y0A2C4E6G8J0L2N4",
"current_limit_usd": "500.00",
"requested_limit_usd": "1500.00",
"period": "month",
"reason": "Quarter-end batch backfill of 2M support tickets.",
"status": "approved",
"decided_by": "user_01J9X1B3D5F7H9K1M3P5",
"decision_note": "Approved through 31 December.",
"created_at": "2026-11-05T10:00:00Z",
"decided_at": "2026-11-05T12:00:00Z",
"approved_limit_usd": "1200.00"
}Fields
| Field | Type | Description |
|---|---|---|
id | string | Unique id of this object. |
type | string | The object type, always spend_limit_request. |
workspace_id | string | The workspace it belongs to. |
requested_by | string | See the endpoint pages below. |
current_limit_usd | string | The workspace limit when the request was made. |
requested_limit_usd | string | What the requester asked for. |
period | string | See the endpoint pages below. |
reason | string | See the endpoint pages below. |
status | string | pending, approved, denied or expired (no decision in 14 days). |
decided_by | string or null | The admin who approved or denied it. |
decision_note | string | See the endpoint pages below. |
created_at | string | When it was created, RFC 3339 UTC (some older objects use Unix seconds). |
decided_at | string | See the endpoint pages below. |
approved_limit_usd | string | See the endpoint pages below. |
Returned by
POST /v1/organizations/spend_limits/requestsPOST /v1/organizations/spend_limits/requests/{request_id}/decisionGET /v1/organizations/spend_limits/requestsGET /v1/organizations/spend_limits/requests/{request_id}
Was this page helpful?