Skip to content

Two engines

Appointments and table reservations are separate products sharing plumbing: how to tell which one an organization runs, and the 403 you hit first.

Gaplessly runs two separate booking engines behind one product.

  • Appointments: a client books one service with one staff member for a set duration. Salons, clinics, studios.
  • Table reservations (hospitality): a guest books a table for a party size inside a service period, for a turn. Restaurants, bars, cafes.

They are two products, not one product with a flag: separate data, separate overlap rules, separate slot maths. What they share is plumbing, such as clients, the organization profile and notifications.

Which engine is this organization?

An organization picks its engine once, when it signs up, and it cannot change afterwards. businessType on GET /api/v1/organization says which, appointments or hospitality. Read it first, then call that engine's endpoints.

AppointmentsTable reservations
With an API keyservices, providers, appointmentstables, service-periods, reservations
Public bookingFind a time, then book it in one callFind a time, hold a table, then confirm it
Either engineorganization, clients, guest self-service, MCPThe same

The 403 you will hit first

Every engine-owned /api/v1 endpoint checks the engine. A key from a table-reservations organization calling GET /api/v1/appointments gets 403 with code: "wrong_vertical", even if it holds appointments:read: a scope says what a program may ask for, the engine says what the organization is. Engine scopes cannot even be granted to the other kind of organization, so in practice this 403 means the program called the wrong set of endpoints.

The public booking endpoints draw the same line: the hospitality ones answer an appointments business with 404.

On this page