Seat a walk-in at a table (API key, POS)
/api/v1/walk-insFor a till opening a check on a table nobody booked. The party is seated now, with no guest attached, and shows on the Floor view like a host's quick-seat; post the check total against the returned id with POST /api/v1/reservations/{id}/checks, and finish it with /status. The online booking rules (booking window, online party limit, booking pauses) do not apply, because the party is already in the room; the venue's own seating-capacity setting and the date's floor layout do. No email is sent. The booking's source is api.
Idempotency-Key header required: a UUID you generate once per booking attempt and resend unchanged on every retry. The first answer is stored and every retry with the same key, from the same API key, with the same body gets that answer back, so a retried create never books twice. The same UUID with a different body, or from a different API key, is a 409. Stored answers include refusals: a 409 for a taken time replays as a 409, so a new attempt needs a new key. Answers are kept for at least a day.
Authorization
bearerApiKey reservations:writeBuild with a test key (sk_test_...): it works only in your API sandbox and never emails or texts anyone. Scopes, errors and limits.
In: header
Scope: reservations:write
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
application/json
application/json
curl -X POST "https://example.com/api/v1/walk-ins" \ -H "Content-Type: application/json" \ -d '{ "partySize": 1, "tableId": "073fbfcb-cd05-4203-be18-a1ce6f8e4d2d" }'{ "data": {}}Cancel a reservationPOST
Cancels on the guest's behalf, recorded as cancelled by the guest. The row is kept, the guest gets the venue's usual cancellation notice, and a paid deposit is settled by the venue's own refund window: `depositOutcome` says whether it was `refunded`, `forfeited`, `none`, or `failed` (the booking IS cancelled; the money needs a person). Only a `confirmed` or `pending` booking can be cancelled.
Seat, finish or no-show a reservation (API key, POS)POST
For a till or floor system. `seated` when a check opens on the table (from confirmed), `completed` when it is paid (from confirmed or seated), `no_show` (from confirmed only: a party that was seated came), and `confirmed` to undo a seat (from seated only). Cancelling is `POST /api/v1/reservations/{id}/cancel`. The consequences match a host pressing the same button on the Floor view: an early finish ends the sitting now and frees the table, a completion queues the guest's thank-you after a short undo window and the venue's recipes, a no-show queues its follow-up, and `booking.updated` is sent. **A no-show never charges a fee here**; that stays an admin's decision in the dashboard. Sending the status a booking already has is a success that changes nothing, so a till can resend safely. `ifStatus` writes only if the booking is still in that status.