Reservations
Reservation routes manage room reservations and scheduling blocks connected to rooms, customers, or meetings.
Reservation Data
- Reservations usually require room_id and start/stop date-time values.
- They can also include customer_id, meeting_id, notes, owner, or status when documented.
- Use UTC Y-m-d H:i:s for date/time values.
Availability
- Check Rooms.Availability before adding or editing reservations when the UI lets users choose a room/time.
- The UI should show conflicts clearly and avoid saving overlapping reservations when the server rejects them.
Common Flow
- Load room/reservation permissions from User.Basic.
- Check room availability for the selected time range.
- Add or edit the reservation.
- Refresh room calendar and reservation lists after success.