Build on Gaplessly
Two booking engines, appointments and table reservations, behind one API. Scoped keys, an OpenAPI 3.1 document, and an MCP connector for AI assistants.
Read this first: the two enginescurl https://gaplessly.com/api/v1/organization \ -H "Authorization: Bearer sk_live_..."{ "data": { "id": "8f6e2a4c-0b7d-4c1e-9a53-2d1f6b8e7c90", "name": "Example Studio", "slug": "example-studio", "businessType": "appointments", "timezone": "Australia/Sydney", "currency": "AUD" }}Recently shipped
Full changelog- 21 OctYour venue's own role namesRestaurants and bars now see role names that fit a venue. Manager reads as Management and Front desk as Host (front door), on the Team page, in invites and in help. What each role can do is unchanged.
- 21 OctNew cocktail picturesEvery drink in the cocktail library has a new picture, with clear drinks tinted by their glass so they read properly.
- 21 OctAcademy and the bar on every venue planEvery venue plan now includes Academy and the bar tools. Each plan has room for your own courses, assignments, cocktail recipes and counted bottles, with more on higher plans. Core courses, drills and the full cocktail library stay unlimited.
- 20 OctGaplessly Academy for your teamRestaurants get a training section of their own. Short courses on service, the floor, the bar and safety, each lesson with a quick check, plus drills built from your own cocktails, tables and menu. Managers can assign a course to a role or a person with a due date, and write their own courses for house rules or opening and closing.
The basics
- Two enginesAppointments and table reservations are separate products. Read this first.
- AuthenticationScoped API keys for /api/v1, and the public endpoints that need none.
- ErrorsOne JSON error shape, with stable codes to match on.
- Rate limits120 requests a minute per key by default, stated on every response.
- Versioningv1 keeps answering for at least 6 months after a v2 ships.
- OpenAPI documentThe full OpenAPI 3.1 schema, for SDK generators and Postman.