Disponibilidad por fecha específica
Availability
GET /v1/scheduling/availability
Availability for a specific date. Returns free slots per professional for a given service.
GET
Disponibilidad por fecha específica
Computes the free slots for a service on a single date. The engine takes into account professional schedules, existing appointments, service buffers (
bufferBefore, bufferAfter), and time restrictions (time_rules.earliest_start, time_rules.latest_end). If no branchId is provided, the tenant’s first branch is used.
Endpoint
Required scope
scheduling:availability:read
Query params
| Param | Type | Required | Description |
|---|---|---|---|
serviceId | string | Yes | Service to book. Defines slot duration and restrictions. |
date | string | Yes | Date in YYYY-MM-DD format. If earlier than today in the branch’s tz, returns results: []. |
branchId | string | No | Branch. If omitted, the tenant’s first branch is used. |
professionalId | string | No | Restrict the computation to a specific professional. |
Example request
Response
200 OK
| Field | Type | Description |
|---|---|---|
results[].id | string | Professional id. |
results[].timeSlots[].time | string | Slot start time (HH:mm) in the branch’s tz. |
400 Bad Request
date with an invalid format, missing serviceId, or no branch exists for the tenant.
401 Unauthorized · 403 Forbidden
Same semantics as the rest of the public API.Common patterns
”Date → professional → time” picker UI
- The user picks a date.
- Your app calls
GET /availability?date=<date>&serviceId=...&branchId=.... - The response groups slots by professional, ready to render as columns or rows.
Authorizations
Personal Access Token con prefijo kbai_pk_. Generar desde el portal con permiso developer.manage_tokens.
Query Parameters
Servicio (requerido)
Fecha en formato YYYY-MM-DD
Example:
"2026-05-02"
Sucursal (default: primera del tenant)
Profesional específico
Response
200
Disponibilidad por profesional para la fecha