Update a visit (state, tags, time, party)
waitwhile_update_visitDestructiveIdempotent
WRITE: change ONE visit — its state (e.g. WAITING to SERVING to COMPLETE, or BOOKED), add/remove tags (e.g. ARRIVED, CONFIRMED, NO-SHOW), booking date/duration or party size. Only the fields you pass change. By default the request asks Waitwhile to suppress the customer message; this may only stop the immediate status message, 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. Use waitwhile_cancel_visit to cancel. POST /visits/{visitId}.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| date | No | New booking start, local time YYYY-MM-DDThh:mm. | |
| state | No | New state. | |
| add_tags | No | Tags to add. | |
| duration | No | New booking duration in seconds. | |
| visit_id | Yes | Visit id. | |
| party_size | No | ||
| remove_tags | No | Tags to remove. | |
| 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. |