Skip to main content
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

Example request

Response

200 OK

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

  1. The user picks a date.
  2. Your app calls GET /availability?date=<date>&serviceId=...&branchId=....
  3. The response groups slots by professional, ready to render as columns or rows.

Authorizations

Authorization
string
header
required

Personal Access Token con prefijo kbai_pk_. Generar desde el portal con permiso developer.manage_tokens.

Query Parameters

serviceId
string
required

Servicio (requerido)

date
string
required

Fecha en formato YYYY-MM-DD

Example:

"2026-05-02"

branchId
string

Sucursal (default: primera del tenant)

professionalId
string

Profesional específico

Response

200 - application/json
results
object[]
required