The Sedes API lets you model the physical branch structure of your organization. Each branch (Documentation Index
Fetch the complete documentation index at: https://mintlify.com/Glemynart/SaaS/llms.txt
Use this file to discover all available pages before exploring further.
sede) is linked to a validated DANE municipality record and can be activated or deactivated without removing historical data. Employees, contracts, and bulk-import batches all reference sedes by their UUID. All endpoints require a valid JWT and an active tenant context.
Endpoints
List branches
nombre. The response embeds the associated municipality object (id, nombre, departamento).
Query parameters
Case-insensitive partial match against the branch
nombre.When
true, returns only active branches. When false, returns only inactive branches. Omit to return all branches regardless of status.Response
Unique branch identifier (UUID).
Branch display name, unique among active branches within the tenant.
Street address of the branch.
Whether the branch is currently active.
ISO 8601 creation timestamp.
ISO 8601 last-updated timestamp.
Embedded DANE municipality record.
Create a branch
municipioId must correspond to a valid record in the DANE catalogue (see GET /dane/municipios below). If the branch will be active, its nombre must not conflict with any other currently-active branch in the same tenant (case-insensitive).
Required role: ADMIN
Request body
Branch display name. Must be unique among active branches within the tenant (case-insensitive comparison).
UUID of the DANE municipality where this branch is located. Obtain valid values from
GET /dane/municipios.Street address of the branch.
Initial active state. Defaults to
true if omitted.Response
Returns the created branch object including the embeddedmunicipio record.
Get a branch
404 if the branch does not exist or belongs to a different tenant.
Path parameters
UUID of the branch to retrieve.
Update a branch
400 Bad Request. If a new municipioId is provided, it is validated against the DANE catalogue before the update is applied.
Required role: ADMIN
Path parameters
UUID of the branch to update.
Request body
New branch name. Must remain unique among active branches within the tenant.
New DANE municipality UUID. Must exist in the DANE catalogue.
Updated street address.
Set to
false to deactivate the branch (logical/soft deactivation — the record is not removed from the database and all historical references remain intact).DANE municipality catalog
Get DANE municipality catalog
id from any result as the municipioId when creating or updating a sede or an employee record.
Response
Each item in the returned array contains:UUID — use this as
municipioId in branch and employee requests.Official DANE code (e.g.,
"11001" for Bogotá D.C.).Municipality name.
Department the municipality belongs to.
Deactivation and soft-delete behavior
Settingactivo: false on a branch performs a logical deactivation — the record persists in the database with all historical linkages (contracts, employees, import batches) intact. Deactivated branches are excluded from the uniqueness check for nombre, so a new active branch may reuse the name of a deactivated one.
Branches cannot be hard-deleted through the API.
Uniqueness rule
Active branch names must be unique within a tenant, regardless of letter case. Attempting to create or rename a branch to a name already used by another active branch in the same tenant returns400 Bad Request with the message "Ya existe una sede activa con este nombre".
Employees reference branches by their UUID
sedeId in all API operations. However, the bulk-import template (CSV/Excel) uses the branch name (nombre) as the lookup key. Ensure branch names in your import file exactly match the names registered in the system — mismatches will cause row-level validation errors during the import job.