spend_limit_reached
- HTTP status
- 402
- Retry
- No
- Execution
- Nothing was done
- Admin needed
- Yes
Monthly spend limit reached. A workspace admin set a monthly spend limit in the console and this month's calling spend has reached it. New calls are refused until the limit is raised or the month rolls over.
What it means
The API returns HTTP 402 with error.code set to spend_limit_reached. The default message is: "This workspace has reached the monthly spend limit set by its admin."
Common causes
- Calling spend this month reached the limit configured in the console.
How to identify it
Check the response status (402) and error.code (spend_limit_reached). Branch on error.code, not on the message text: messages can be reworded, codes do not change within v1. Log error.request_id (also sent as the X-Request-Id header) so support can find the request.
How to fix it
- A workspace admin raises or removes the limit in the console settings.
Retry guidance
Sending the request unchanged fails the same way. Fix the cause first (see How to fix it), then send it again.
Did anything happen?
This request was refused before any call was placed and before anything was charged.
Idempotency
Nothing was done and the refusal is not stored under the Idempotency-Key. Fix the cause, then send the same request (with the same key if you sent one).
Who can fix it
A workspace administrator usually has to act, in the RelationsAI console.
When to contact support
If the error persists after the steps above, contact support@relationsai.com. See Support for what to include (the request_id, the time in UTC, the operation, and whether you used a test or live key) and what never to send (API keys, Authorization headers, webhook signing secrets, recording links, transcripts or customer data).
Example error response
JSON
Operations that can return this error
POST /calls: Place a callPOST /campaigns/{campaign_id}/start: Start a campaignPOST /campaigns/{campaign_id}/resume: Resume a campaign
See all codes in the error-code reference.