Release a held table
/api/book/{slug}/reservations/{id}The guest closed the sheet or hit back. Releases the table immediately rather than waiting out the hold window. Only ever deletes a row whose status is still hold; a confirmed booking is cancelled from the dashboard or the manage link, never dropped by an unauthenticated caller holding an id.
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 reservation id from the hold.
Response Body
application/json
application/json
curl -X DELETE "https://example.com/api/book/string/reservations/string"{ "released": true}Confirm a held tablePATCH
Attaches the guest's details and promotes the hold to `confirmed`. The update is a compare-and-set on `status = hold`, so two racing confirms cannot both succeed; the loser gets 410 and, importantly, does not send a "table confirmed" email for a booking it did not make. `hold_expires_at` is cleared in the same statement because the check constraint is biconditional; setting status alone would fail.
Preview a promo code or gift card against a held depositPOST
H12. Never applies or spends anything: what a promo code and/or gift card would do to the deposit or Experience ticket this hold owes, so the payment step can show the discount, the gift card part and what is left before the card is touched. The confirm (`PATCH /api/book/{slug}/reservations/{id}` with `promoCode`/`giftCardCode`) re-resolves the same codes with the guest's customer id and is the only place they are applied, so a once-per-customer or new-customers-only code can still be refused there. Stripe's minimum charge is respected: the card part is either 0 or at least the minimum. Rate-limited on the 'write' guest bucket.