Implement Booking SaaS

Booking SaaS is an API-first booking system for yoga teachers, studios, and other event businesses. Use the administration interface for day-to-day operations or integrate the REST API into your own website, mobile application, or member portal.

Current release status

The current release is an implementation foundation, not a finished payment production system. Read Production readiness before processing customer data or money.

Choose an implementation path

Goal	Start here
Operate a studio using the built-in interface	Administration guide
Add booking to another website or application	API integration
Understand tenants, roles, events, and entitlements	Accounts and users
Host your own deployment	Operations and hosting

End-to-end implementation

1. Create a top-level account with POST /api/auth/signup.
2. Consume the emailed magic link and retain its bearer session.
3. Create events and optionally generate weekly recurring instances.
4. Set instance bookability to everyone or selected groups.
5. Create subscriptions, class passes, workshops, or drop-in products.
6. Connect a MobilePay gateway implementation.
7. Let authenticated attendees purchase products and create bookings.
8. Use the administration dashboard to manage schedules and bookings.

The live Swagger UI is the endpoint reference and the machine-readable contract is available as OpenAPI JSON. Studio operators can open the administration application on the same deployment.

API conventions

• All API routes start with /api.
• JSON is used for request and response bodies.
• Protected routes require Authorization: Bearer <session-id>.
• Tenant scope comes from the session, never from an account identifier supplied by the client.
• Prices are integer minor units: 12500 means DKK 125.00.
• Dates and times use ISO 8601. Recurring schedules currently interpret local-looking values as UTC; see Production readiness.
• Error responses have the shape { "error": "Human-readable message" }.