Core concepts
Availability
Slots are generated from schedules, then filtered by bookings, holds, and capacity-served via dashboard or widget APIs.
How it is built
- Schedules define rules per resource (including auto-generation where enabled).
- Slots materialize concrete bookable windows (or support multi-day ranges depending on configuration).
- Bookings and temporary holds reduce
capacity_remainingor block dates.
APIs
- GET /api/availability. session-authenticated, for dashboard tools.
- GET /api/widget/availability. publishable key, for public sites and embeds.
Holds during checkout
Pending flows can place a short-lived hold so two customers rarely claim the same slot. Holds expire if checkout is abandoned, and scheduled cleanup should release expired holds.