Copy page

Error codes

api_access_not_enabled

API access not enabled. The v1 API is in private preview and must be enabled for each workspace.

What it means

The API returns HTTP 403 with error.code set to api_access_not_enabled. The default message is: "API access is not enabled for this workspace."

Common causes

• The workspace has not been enabled for the v1 API yet.

How to identify it

Check the response status (403) and error.code (api_access_not_enabled). 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

• Write to support@relationsai.com to request access for the workspace.

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

Write to support@relationsai.com to request access, quoting the request_id. 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
{
  "error": {
    "code": "api_access_not_enabled",
    "message": "API access is not enabled for this workspace.",
    "details": {},
    "request_id": "req_vrsfwbas6p3uz55gn4huiryv",
    "retry": "no",
    "doc_url": "https://docs.relationsai.com/errors/api_access_not_enabled"
  }
}

See all codes in the error-code reference.