spend_limit.request_created

⚠️
Preview — this feature is being built; the design below is the spec.

Sent when: Someone asked for a higher workspace spend limit.

PropertyValue
ScopeThe whole organization. Register with an Admin key at /v1/organizations/webhooks.
AreaBilling
Subscribe with"events": ["spend_limit.request_created"], or a prefix such as "spend_limit.*"

Payload

{
  "id": "evt_01JCA5D7F9H1K3M5P7R9",
  "type": "spend_limit.request_created",
  "created_at": "2026-11-05T10:00:00Z",
  "organization_id": "org_01J9X8Z6B4D2F0H8K6M4",
  "data": {
    "object": {
      "id": "slr_01JCQ3R5T7V9X1Z3B5D7",
      "type": "spend_limit_request",
      "workspace_id": "wrkspc_01JC0A2C4E6G8J0L2N4Q",
      "requested_limit_usd": "1500.00",
      "status": "pending"
    }
  }
}

data.object matches what the corresponding GET endpoint returned when the event happened. Prompt and output text are never included.

What to do

Delivery

Deliveries are signed, retried with back-off for up to 3 days, and may arrive more than once or out of order. De-duplicate on the syntic-event-id header and compare timestamps before acting. See Webhooks.

Was this page helpful?