Tenants
PlatformManage the secure workspaces that isolate Mediloop data, configuration, access and usage.
Isolation
Tenant-scoped by design
Hierarchy
Organizations + sub-organizations
Access
Membership + role context
Configuration
Policies, modules & branding
Overview
Every tenant is an explicit security and operational context. API requests that act on tenant-owned resources must carry a valid tenant context.
Tenant model
| Field | Type | Description |
|---|---|---|
| id | string | Immutable tenant identifier |
| organization_id | string | Owning organization |
| tenant_type | enum | Operational tenant category |
| status | enum | provisioning, active, suspended, archived |
| region | string | Data / hosting region |
| settings | object | Tenant-specific non-secret configuration |
List tenants
GET /v1/tenantsCopy
curl -X GET "https://api.mediloop.lu/v1/tenants?organization_id=org_01" \
-H "Authorization: Bearer $ACCESS_TOKEN"Tenant types
| Type | Typical use |
|---|---|
| doctor | Independent practice / doctor context |
| pharmacy | Pharmacy operations |
| clinic | Clinic or care facility |
| hospital | Hospital operations |
| supplier | Supplier / manufacturer context |
| application | Approved HealthTech application context |
Status values
| Status | Meaning |
|---|---|
| provisioning | Tenant resources are being created |
| active | Operational and available |
| suspended | Temporarily blocked from normal operations |
| archived | Retained for history; no new operational activity |