mocop
Browse · Docs · Guide · Analyze

Gaplessly booking API

API by Gaplessly · rest

Gaplessly runs two booking engines: appointments (a client books one service with one staff member for a set duration) and table reservations (a guest books a table for a party inside a service period). They are two products, not one product with a flag. Each organization runs exactly one, chosen when it signs up, and businessType on GET /api/v1/organization says which. This document covers the surfaces built for other software: - /api/v1/*: an organization's own data with an API key, sent as Authorization: Bearer sk_live_…: read it, find free times, and book, change or cancel on a guest's behalf. Scoped and rate limited. - /api/book/{slug}/*: the public booking endpoints a business's booking page calls. No authentication. - /api/book/{slug}/manage/{token}: guest self-service. The token in the guest's booking link is the whole credential. - /api/mcp: a Model Context Protocol endpoint for AI assistants helping a guest find a time. No authentication.…

Endpoint: https://gaplessly.com/

Verification: observed. Source: crawl.

Capabilities (45)

  • Join the waitlist for a full day (public appointments)
  • Take yourself off the waitlist
  • Book an appointment
  • List bookable appointment slots
  • Send a big-group enquiry
  • Message the venue
  • Answer the venue's intake form
  • Change a booking or its dietary preferences and occasion
  • Cancel a booking
  • Preview a promo code
  • Hold a table
  • List bookable table slots
  • List free tables for a slot
  • Confirm a held table
  • Release a held table
  • Preview a promo code or gift card against a held deposit
  • Same time at sister venues
  • Join the waitlist
  • Join today's walk-in line
  • Place in the walk-in line
  • Leave the walk-in line
  • MCP endpoint
  • List appointments
  • Book an appointment
  • Change an appointment
About · Contact · Privacy