daily_call_limit_reached
- HTTP status
- 429
- Retry
- After Retry-After
- Execution
- Nothing was done
- Admin needed
- Yes
Daily call limit reached. Live mode caps how many calls a workspace can place through the API per UTC day, as protection against runaway scripts. Each POST /v1/calls counts one call, and starting a campaign counts one per recipient (refused whole when they do not all fit). Resuming a campaign never counts: its start already did. details says how many calls the request needed and how many were left. The limit resets at 00:00 UTC. Test mode has no daily cap.
What it means
The API returns HTTP 429 with error.code set to daily_call_limit_reached. The default message is: "This workspace has reached its daily limit of calls placed through the API."
Common causes
- A loop or a retry storm placed more calls than intended.
- Legitimate volume above the default cap.
How to identify it
Check the response status (429) and error.code (daily_call_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
- Wait until
Retry-After(the next UTC midnight). - Ask support to review the limit if the volume is expected.
Retry guidance
Wait for the number of seconds in the Retry-After response header, then retry.
Did anything happen?
This request was refused before any call was placed and before anything was charged.
Idempotency
Nothing was done. The request may be sent again after the reset (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
Write to support@relationsai.com to discuss a higher daily limit. 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 campaign
See all codes in the error-code reference.