Create tenant
PlatformProvision a secure tenant for an organization, location, business unit or approved application.
Isolation
Tenant-scoped by design
Hierarchy
Organizations + sub-organizations
Access
Membership + role context
Configuration
Policies, modules & branding
POST
/v1/tenantsScope: tenants.writeEndpoint summary
| Method | Endpoint | Required scope |
|---|---|---|
| POST | /v1/tenants | tenants.write |
Request body
| Field | Type | Required | Description |
|---|---|---|---|
| organization_id | string | Yes | Owning organization |
| name | string | Yes | Tenant display name |
| tenant_type | string | Yes | Tenant category |
| region | string | No | Approved hosting region |
Provisioning behavior
Tenant creation may return a provisioning state before all backing resources are ready. Clients should treat provisioning as asynchronous and poll or consume lifecycle events where available.
Example request
POST /v1/tenantsCopy
POST /v1/tenants
Authorization: Bearer $ACCESS_TOKEN
Content-Type: application/json
{
"organization_id":"org_clinic_01",
"name":"Clinique Centrale",
"tenant_type":"clinic",
"region":"eu-central"
}Example response
201 CreatedCopy
{
"id":"tnt_01",
"organization_id":"org_clinic_01",
"tenant_type":"clinic",
"status":"active",
"region":"eu-central"
}Validation
| Rule | Behavior |
|---|---|
| Authorization | Caller must have approved organization administration rights |
| Uniqueness | Identifiers are server generated and immutable |
| Ownership | Tenant ownership cannot be forged via request context |
| Audit | Creation is attributed to the authenticated actor and context |