Skip to main content
POST
Add a client to the waiting list

Autorizaciones

Authorization
string
header
requerido

API key created in the dashboard under Settings → API Keys. Send it as Authorization: Bearer pk_....

Cuerpo

application/json

Body of POST /calendar/waitlist/entries.

Identify the client with EITHER client_id (a contact already in this workspace) OR phone (E.164; the contact is matched by phone or created with the given names/email). Name the services by service_ids or service_names. waitlist_id is optional: left out, each service is routed to the active list that contains it.

client_id
integer | null

An existing contact's id

phone
string | null

E.164 phone, e.g. +573001112233 (alternative to client_id)

first_name
string | null

Given name, used only when the contact is created.

Maximum string length: 100
last_name
string | null

Family name, used only when the contact is created.

Maximum string length: 100
email
string | null

Email, used only when the contact is created.

Maximum string length: 255
waitlist_id
integer | null

Target list; omitted → resolved per service

service_ids
integer[] | null

Services by id

service_names
string[] | null

Services by exact name (case-insensitive)

priority
integer | null

0 urgent, 1 high, 2 normal (default), 3 low

Rango requerido: 0 <= x <= 3
preferred_professional_id
integer | null

calendar_profile_id the client would rather wait for

earliest_date
string | null

YYYY-MM-DD

latest_date
string | null

YYYY-MM-DD

time_preference
string | null

any | morning | afternoon | evening

notes
string | null

Free text shown to the team on the entry.

Maximum string length: 2000

Respuesta

OK

Response for POST /calendar/waitlist/entries (always 200 on success: the call is an upsert).

data
PublicWaitlistEntryCreateDataSchema · object
requerido

Upsert result.

status
string
predeterminado:success

Always success.

Allowed value: "success"