API access for your clients
Whether a client can use the API follows your organisation's API-access setting, which only a platform admin changes — it is not a reseller control.
Whether a client can use the v1 API is not a reseller control. It follows your organisation's API-access setting: a client with no per-workspace override inherits it, and only a platform admin changes either the organisation setting or a per-workspace override. There is no apiAccess field on the reseller limits editor or its endpoint.
What the client sees when it is off
Both key issuance and every /api/v1 call return 403. In the API:
API access is not enabled for this workspace.In their dashboard, the API keys screen shows "API access is not enabled" — "API access is available on request — contact your provider to enable programmatic access to your workspace." That wording sends them to you.
The switch is live
Access is resolved on every request, so a change takes effect immediately — including on keys already issued. Turning access off stops existing keys on the very next call; turning it back on restores them with nothing to reissue.
If a client should have access but is still refused, contact Evoriqa support to confirm the organisation's API-access setting.
Where to go next
Last updated