Booking & Holds

Status: Implemented / controlled release

What it does

Manages availability, temporary holds, booking creation and lifecycle under resource/tenant policy.

Benefits

• protects scarce capacity
• reduces double booking
• links customer intent to operations

Typical usage

1. Check availability
2. Create hold
3. Confirm booking
4. Check in
5. Progress/close/cancel through authorized transitions

Roles

Guest, Customer, Staff, Manager, Owner

API families

• /api/v1/public/availability
• /api/v1/public/booking-hold
• /api/v1/public/booking-register
• /api/v1/booking/*
• /api/v1/bookings/*

Endpoint presence does not automatically make an endpoint a Partner API. See API → API Overview.

Configuration

• Resource policy
• Calendar
• Capacity
• Workflow
• Hold expiry

Current limitations / release notes

External partners should not rely on all first-party mutation routes until a Partner API profile is published.

Related modules

Resources, Capacity, QR, Payments, Notifications