Join the waitlist for a full day (public, appointments)
/api/book/{slug}/appointment-waitlistOne service, one day, any team member or one named, an optional time window. Only a day availability answers full for can be joined. Nothing is held. When a time this guest could really book opens up, they are emailed a link to it, and the first one back gets it. Joining again with the same email, service, day and team member returns the existing entry.
Path Parameters
The organization's public booking slug, i.e. the {slug} in /{slug}. Only orgs with status active resolve; anything else is a 404.
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/api/book/string/appointment-waitlist" \ -H "Content-Type: application/json" \ -d '{ "requestedDate": "2019-08-24", "serviceId": "8f8bb40f-b96b-40fe-9064-5031fbe483f9", "name": "string", "email": "user@example.com", "phone": "string" }'{ "ok": true, "waitlistId": "83bf03b0-e6bc-406b-a1cd-2e6c45d6197b"}List bookable appointment slotsGET
The public availability grid, the same one a business's booking page draws. Slot allocation is first-come: for a given start time the first staff member found free wins it. Slots whose start time has already passed are filtered out, because the booking POST rejects them anyway. **Ranged mode (`days`).** Answers up to 14 consecutive days from `date` in one request. The single-date shape (`{slots}`) stays the default; `days` greater than 1 switches the response to `{days: {"<date>": {slots}, ...}}`, one entry per requested date.
Book an appointmentPOST
Public guest checkout. The requested slot is checked again server-side (not in the past, inside the staff member's working hours, not inside a blocked period), because nothing stops a direct POST inventing a slot the booking page never offered. Overlap is enforced by the database. The client record is matched on email, so a returning customer builds up history on one record. `notes` goes on this booking, never on the client record. This route checks only that the business is active; it is the hospitality endpoints that refuse a business running the other engine.