POS and till integration
For a till vendor: map tables, seat bookings and walk-ins, move tables, report check totals and finish the visit.
For a point-of-sale or till vendor connecting to a Gaplessly venue. A few calls cover the night: map the tables, find the booking, seat it, move it, report what it spent, and finish it. Table reservations only; an appointments business gets a 403.
The money rule: Gaplessly takes payment for the booking (a deposit, a no-show fee) and never for the meal. The till stays the record of what was sold. We store one total per check, never line items, and recording a check never charges anyone.
The key
The venue makes a key under Developer with reservations:read and reservations:write (and organization:read to read its name and timezone). One key per till system: checks are numbered within the key, so two tills at one venue can both use check 1001. A test key (sk_test_) works against the venue's sandbox, which emails nobody. See Authentication.
1. Map your tables
GET /api/v1/tables lists the venue's tables with their names and seats. Match them to your own table numbers once and keep the Gaplessly id.
2. Find tonight's bookings
GET /api/v1/reservations?from=...&to=... lists bookings in a window, each with its tableId, partySize and status. Subscribe to booking.created, booking.updated and booking.cancelled (Webhooks) instead of polling.
3. Seat the party
When a check opens on a booked table: POST /api/v1/reservations/{id}/status with {"status": "seated"}. The Floor view in the dashboard updates as if the host had pressed Seat. Send ifStatus to change it only if nobody else has.
A party nobody booked: POST /api/v1/walk-ins with {"partySize": 2, "tableId": "..."} and an Idempotency-Key header. They are seated now, with no guest attached and no email, and you get a reservation id back to post the check against. A table already in use is a 409 table_in_use.
4. Move a table
A check transferred to another table: POST /api/v1/reservations/{id}/table with the new tableId. The venue's capacity setting and that night's floor layout apply, and two parties can never hold one table at once.
5. Report the spend
POST /api/v1/reservations/{id}/checks with your own check number as externalId, the totalCents and optionally covers and status (open, closed or voided). Send it again whenever the check changes: the same externalId updates the one record (a tip added, a reopen, a void), so a resend never counts the visit twice and needs no Idempotency-Key. The guest's total across visits comes back on GET /api/v1/clients as lifetimeSpend, and the venue sees it on the guest's profile.
6. Finish
When the check is paid: {"status": "completed"} on the same status route. An early finish frees the table for the next booking and queues the venue's usual thank-you. A party that never came is no_show, which never charges a fee from here; that stays the venue's decision.
A loyalty or CRM tool can hear each check as it lands by subscribing to check.updated (Webhooks).
Testing
A test key (sk_test_) acts on the venue's sandbox: four sample tables and nothing that reaches a guest. An admin can reset it from Developer to start a run from a clean book; test keys and their webhooks keep working.
Retries and order
Every write is safe to resend: status changes to the status a booking already has succeed without changing anything, walk-ins use Idempotency-Key, and checks use your check number. Errors carry a code; see Conventions and the API reference for each route's answers.