Add a customer to the waitlist or create a booking
waitwhile_create_visitDestructive
WRITE: create ONE visit at a location. Without a date it adds the customer to the waitlist; with a local date-time (YYYY-MM-DDThh:mm) it creates a booking. Needs a location and at least a name, phone or e-mail. Not idempotent: calling it twice creates two visits. Visit notes are not supported here (the field is deprecated): use waitwhile_add_customer_note. By default the request asks Waitwhile to suppress the customer message; this may only stop the immediate confirmation, and scheduled reminders/follow-ups can still go out per the location's settings. With send_notifications=true Waitwhile may text/e-mail this ONE customer. POST /visits.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| date | No | Booking start in the location's local time, YYYY-MM-DDThh:mm. Omit to join the waitlist. | |
| name | No | Customer name. | |
| No | Customer e-mail. | ||
| phone | No | Customer phone, E.164 (+16005551234). | |
| duration | No | Booking duration in seconds. | |
| last_name | No | ||
| first_name | No | ||
| party_size | No | ||
| location_id | Yes | Location id (see waitwhile_list_locations). | |
| service_ids | No | Services the customer wants. | |
| resource_ids | No | Preferred resources (staff, rooms). | |
| send_notifications | No | Default false: the request asks Waitwhile not to send the immediate confirmation/status message. This may not stop everything: scheduled reminders and follow-ups can still go out according to the location's own settings. Set true to let Waitwhile send its normal messages to the customer. |