Restrict API access
Understand organization, widget and domain boundaries.
Last updated · Oct 23, 2026
One organization per key
The organization selected when creating a key is its tenant boundary. Replace orgId in a request with that organization’s identifier. A different organization is denied, even if you personally belong to both. Create separate keys for multi-organization integrations.
One logical widget
A workspace is an organization with one logical widget. Domain allowlists control where visitors can use that widget; they do not grant additional API access. Historical website IDs remain internal compatibility identifiers. Keys do not bypass the organization boundary or expose another organization’s conversations.
Membership changes
Access requires the key’s issuer to retain an active owner/admin membership. Removal or loss of that role disables access. Revoke unused keys explicitly. Manage scopes.