Documentation
Booking infrastructure for developers
Headless scheduling, availability, bookings, and Mollie-powered payments-multi-tenant by design. Use the hosted dashboard and APIs, or embed the booking flow on your site.
Quick start
Create a tenant, copy your API key, and call your first endpoints in a few minutes.
API reference
Dashboard routes (session) and public widget routes (publishable key), in one place.
Integration
Embed the booking UI, or build a fully custom front end against the REST API.
Authentication
How session cookies and publishable keys map to different API surfaces.
What you get
- Resources & schedules. Define what can be booked and when it is available.
- Slots & holds. Time-based availability with conflict protection (including holds during checkout).
- Slot-based and multi-day bookings. Appointments or date-range stays from the same engine.
- Mollie. Checkout and webhooks to confirm paid bookings.
- Webhooks. Notify your servers on booking lifecycle events with signed payloads.
- Widget & embed. Pre-built flow at
/embed/[tenant_id]with theming via widget configs.
Two ways to call the API
Dashboard APIs (/api/resources, /api/bookings, …) expect a logged-in user; the browser sends the session cookie from your deployment. Widget APIs (/api/widget/availability, /api/widget/booking, …) use your publishable key in a header or query string-safe for public pages and embeds.
Ready to integrate?
Follow the quick start, then open the endpoints reference while you build.