Managing Tenants
Create, list, update, and delete tenants. Tenant lifecycle and attributes.
Tenant attributes
| Attribute | Description |
|---|---|
| name | Display name (e.g. "Acme Corporation") |
| slug | URL-friendly unique identifier. Auto-generated from name if omitted. |
| abbreviation | Short code (3–5 chars). Used in references. Auto-generated if omitted. |
| status | ACTIVE, SUSPENDED, INACTIVE. Only ACTIVE tenants accept API requests. |
Slug and abbreviation must be unique across all tenants.
When to create a tenant
Create a tenant when you need a new isolated workspace—e.g. a new customer, brand, or business unit. After creation:
- Add environments via
POST /tenants/:id/environments - Configure settings via
PATCH /tenants/:id/settings - Assign users via the Users API
Operations
| Operation | Method | Endpoint |
|---|---|---|
| Create a tenant | POST | /tenants |
| List tenants | GET | /tenants |
| Retrieve a tenant | GET | /tenants/:id |
| Update a tenant | PATCH | /tenants/:id |
| Delete a tenant | DELETE | /tenants/:id |
For full parameter definitions, request/response samples, and code examples, see the API Reference.
Update and delete
- Update — Change name, slug, abbreviation, or status. Slug and abbreviation remain unique.
- Delete — Permanently removes the tenant and all related data (environments, settings, expected/incoming transactions, matches, data sources, webhooks, jobs). Use with caution.
Related
- Environments — Add and list environments per tenant
- Settings — Configure per-environment behavior
- Update tenant settings — API reference for settings