Cancel a reservation
/api/v1/reservations/{id}/cancelCancels 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.
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
Path Parameters
Reservation id.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/api/v1/reservations/string/cancel"{ "data": {}}Change a reservationPATCH
A new time (or, for a table, a new party size) goes through the same change function as the guest's own change on their manage link: the venue's allocator, layouts, locks, hours and every other booking, leaving this booking out of its own way, then the deposit for the new time and party size; the booking window binds a new time. A change never takes money: one that would owe a deposit or a card the booking does not hold (a new time's service-period deposit, or a bigger party crossing the venue's deposit or card rule) is a `409 payment_required`. A party size change on a booking that already holds a deposit or a card is refused outright, for the venue to settle. The guest is told about a new time with the venue's usual change notice. Only a `confirmed` or `pending` booking that has not started can change. Send only the fields you are changing.
Seat a walk-in at a table (API key, POS)POST
For 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.