Skip to main content
A workspace (called an organization in the database) is the multi-tenant boundary in Zeptar. Every agent, conversation, member, and invitation belongs to exactly one workspace.

​
Active workspace

Each session has an active workspace — set by the web UI’s workspace switcher. Endpoints that don’t take an explicit orgId in the path read the active workspace from the session. Endpoints that take orgId in the path:
  • POST /v1/organizations/{orgId}/members
  • DELETE /v1/organizations/{orgId}/members/{memberId}
…use the path parameter as the authoritative scope. The active-workspace fallback does not apply.

​
Membership gate

GET /v1/organizations/by-slug/{slug} returns 404 organization_not_found if the requester is not a member of the workspace, even if the slug exists. This prevents slug enumeration.

​
Roles

Three roles are supported: DELETE /v1/organizations/{orgId}/members/{memberId} requires member.delete permission, granted to both admin and owner.