Update to the /unit_calendars endpoint to resolve an issue where calendars were being returned incorrectly when a rate set was not configured, or when the endpoint attempted to apply fallback automatically.
The calendar response now reflects the actual end of the configured rate set:
If there is a break in the rate set within the requested time span, the calendar will end at the break.
If the rate set is continuous but ends before the requested end date, the calendar will return only up to the last configured date in the rate set.
Update to the /unit_calendars endpoint to support the fallback_rates parameter. When enabled, this parameter creates a fallback rate set that extends the calendar view beyond explicitly configured rates.
Note: The calendar is designed to show absolute availability. To distinguish between standard configured rates and fallback coverage, compare responses with and without the fallback_rates parameter enabled to identify which dates are being filled by fallback.
Resolved an intermittent issue with the **DELETE** /reservations endpoint where, in some cases, the response body returned null instead of the expected detailed response object.
Adjusted "commission" handling logic to improve stability. When "commission" values for a reservation "category" are not explicitly configured, the API will now safely default to 0 rather than returning an exception.