Tenants are the faculty or departmental organizations that own events, spaces, and users within UniEvents. Each tenant belongs to a university and can optionally be tagged with a category. When a tenant is created or its name is updated, a unique URL slug is automatically generated from the name. Tenants are the central multi-tenancy boundary — all events, spaces, and non-superadmin users are scoped to a specific tenant.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/Edfermachado/proyectoSistemas/llms.txt
Use this file to discover all available pages before exploring further.
GET /api/tenants
Returns all tenants across all universities, ordered by creation date (newest first). Authentication: Not required.UUID of the tenant.
Display name of the faculty or department. Must be unique across the platform.
URL-safe identifier auto-generated from the tenant name.
Optional description of the faculty.
UUID of the parent university this tenant belongs to.
UUID of the category that classifies this faculty (e.g. Sciences, Humanities).
Timestamp when the tenant was created.
POST /api/tenants
Creates a new tenant. A unique slug is generated automatically from thename field.
Authentication: Not required at the route level.
Content-Type: application/json
Display name of the new tenant. Must be unique across the platform.
Optional description of the faculty or department.
UUID of the university this tenant belongs to.
UUID of the category to classify the tenant.
GET /api/tenants/{id}
Returns a single tenant by UUID. Authentication: Not required.UUID of the tenant to retrieve.
PUT /api/tenants/{id}
Updates an existing tenant. Only fields included in the request body are modified. Ifname is updated, the slug is automatically regenerated.
Authentication: Not required at the route level.
Content-Type: application/json
UUID of the tenant to update.
Updated display name. Triggers slug regeneration if provided.
Updated description text.
Updated category UUID.
DELETE /api/tenants/{id}
Permanently deletes a tenant. Ensure that all associated users, spaces, and events are removed or reassigned before deletion to avoid orphaned records. Authentication: Not required at the route level.UUID of the tenant to delete.