account_inactive
- HTTP status
- 403
- Retry
- No
- Execution
- Nothing was done
- Admin needed
- Yes
Workspace account inactive. The workspace trial has ended or the account has been suspended. Reads keep working; calls and campaign dialling are refused.
What it means
The API returns HTTP 403 with error.code set to account_inactive. The default message is: "This workspace cannot place calls because its account is not active."
Common causes
trial_expired: the free trial ended.suspended: the account was suspended.
How to identify it
Check the response status (403) and error.code (account_inactive). 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 can upgrade the plan in the console, or contact support about a suspension.
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
For a suspended account, write to 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.