List a reservation's POS checks
Every check recorded against the reservation by any till, oldest first, and spendCents, the sum of those not voided. Totals only; Gaplessly never holds line items.
Authorization
bearerApiKey reservations:readBuild 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:read
Path Parameters
Reservation id.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/api/v1/reservations/string/checks"{ "data": [ {} ], "spendCents": 0}Move a party to another table (API key, POS)POST
For a till that transferred a check. The venue's own seating-capacity setting and the date's floor layout apply, as when a host moves the party, and two parties can never hold one table at the same time. A party on several tables moves to the one table given and frees the rest. The time does not change, and the guest is not told (they were never told their table). Moving a party to the table it is already on is a success.
Record what a party spent (API key, POS)POST
A till reports a check's **total**, in the venue's currency's minor units. Never line items: itemised sales stay in the POS. This records spend against the visit and charges nothing. Idempotent by `externalId`, the till's own check number: sending it again updates the same check (reopened, a tip added, `voided`), so no `Idempotency-Key` is needed and a visit is never counted twice; a refund is the same check resent with its new total. Check numbers are kept apart per partner (the key's partner label, or the key itself), so two tills can both use 1001. A check number already on another reservation is refused. Any other field, line items included, is ignored and never stored. The guest's lifetime figure is `lifetimeSpend` on `GET /api/v1/clients`. `201` for a new check, `200` for an update.