Take yourself off the waitlist
/api/book/{slug}/appointment-waitlist/{token}The button on the page a waitlist email links to. token is the signed value in that link and names one entry. A POST because mail scanners prefetch links, so nothing else may change the 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.
The signed token from the email.
Response Body
application/json
application/json
application/json
curl -X POST "https://example.com/api/book/string/appointment-waitlist/string"{ "ok": true, "alreadyRemoved": true}Find free timesGET
Free times at the key's own organization, from the same slot engine its booking page uses, so a time this returns is one `POST /api/v1/reservations` or `POST /api/v1/appointments` will accept (until someone else books it). **Shared**: the organization's engine decides the question. - A table-reservations venue: `date` and `partySize`. - An appointments business: `date` and `serviceId`, optionally `providerId` (omit it for any available team member; each slot then names the `providerId` it was found for). `days` walks forward from `date`, up to 14 days in one call. Each day carries its `slots` and, for a venue, the `reason` an empty day is empty (`closed`, `full`, `too_large` and so on), so a fully booked day and a closed one never look alike. **Appointment start times sit on one grid per day** (behaviour change, 2026-10-13): every `appointmentSlotMinutes` from the business's opening time that day, or from midnight when it has no opening hours. A team member whose hours start off that grid joins it at the next tick, so with any available team member the slots no longer mix, say, 9:00 and 9:10 starters. The public MCP's `find_appointment_times` answers from the same engine and changed the same way. **Slot times are the venue's wall clock wearing a `Z`**, exactly like `startsAt` on a booking. Send one back to create unchanged; never convert it, or it moves by the venue's whole offset. Also limited per calling IP, 240 requests a minute, by the booking page's own limiter: a `429` here can come from either limit, and both carry `Retry-After`.
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.