Aug 4, 2021 - Sandbox API Release
over 2 years ago by Mike
- Rename ResourceAllocations routes to maintain consistency with EventAllocation routes. ResourceAllocations continues to be a work in progress. They are not yet connected to availability
MaxCapacity/GroupSize Fixes
Availability
- The slots now disappear when available capacity is exhausted in addition to
bookingLimit
- Availability now checks for
allowableAppointments
on a slot before booking an appointment
Appointments:
POST/PUT Appointments
endpoints now validatesgroupSize
with correlation to the Service'smaxCapacity
,maxGroupSize
settings
Services:
POST/PUT Services
endpoints now validatemaxCapacity
,maxGroupSize
settings- The default values of allowableCapacity and availableCapacity are 0. When both are 0, they are ignored by availability/appointments endpoints
Note: If you are using maxCapacity
with the intention of booking multiple appointments in a single (1) slot, make sure you update the bookingLimit
in the service to reflect that. Good practice is to make the bookingLimit
equivalent to the maxCapacity
. Assumption: If every booking is a single booking, you need to allow the maxCapacity
number of booking in that slot. By default bookingLimit=1