ip_not_allowed
- HTTP status
- 403
- Retry
- No
- Execution
- Nothing was done
- Admin needed
- Yes
IP address not allowed. The workspace has an IP allowlist enabled in its security settings and the request's source address is not on it.
What it means
The API returns HTTP 403 with error.code set to ip_not_allowed. The default message is: "Requests from this IP address are not allowed for this workspace."
Common causes
- The workspace IP allowlist does not include the server making the request.
How to identify it
Check the response status (403) and error.code (ip_not_allowed). 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
- Ask a workspace admin to add the server's egress address to the allowlist in the console security 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 nothing was stored (under an Idempotency-Key, if you sent one), so the request can be sent again, with the same key if you used one, once the cause is fixed.
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
See all codes in the error-code reference.