An update has been deployed to resolve an issue on the /unit_quotes endpoint affecting "discount_code" evaluation during quote generation. In certain scenarios, discount codes configured with booking conditions (such as minimum nights or date restrictions) were not being applied even when the reservation met the configured criteria. The quote logic has been corrected to ensure that conditional discount codes are properly evaluated and applied when their conditions are satisfied.
An update has been deployed to the /unit_calendars endpoint to enforce proper validation when start is later than end. Invalid date ranges now consistently return a 400 Bad Request response instead of returning inconsistent payloads or internal errors.
An update has been deployed to the /unit_amenities response when requesting with channel=vrbo. The endpoint now returns properly formatted Vrbo amenity codes as expected and no longer includes internal, non-Vrbo tokens in the payload.
An update has been deployed to resolve an issue with the /suppliers endpoint where, in specific scenarios, the response payload could include repeated supplier records. The endpoint now returns a properly de-duplicated supplier list as expected.
Documentation Update – Upcoming Removal of Internal-Only Endpoints
Certain endpoints under /emails/subaccounts and /unit_quotes were previously documented publicly but are intended for internal use only. These endpoints are not required or supported for external partner integrations.
To keep the public documentation accurate and focused, documentation for the following endpoints will be removed on Friday, February 20, 2026:
GET/emails/subaccount
POST/emails/subaccount
PUT/emails/subaccount
DELETE/emails/subaccount
GET/unit_quotes
GETunit_quotes/{unit_id}
PUT/unit_quotes
If you believe your integration depends on these endpoints, please contact [email protected]
before Tuesday, February 17, 2026.
No changes are being made to supported public CiiRUS-API functionality.
An update has been deployed to resolve an inconsistency between the single-reservation and multi-reservation update endpoints. Under certain conditions, equivalent update requests could succeed via PUT/reservations but fail via PUT/reservations/{reservation_id} with an ownership-related validation error. The validation behavior has been aligned so both endpoints now handle equivalent payloads consistently, including updates to non-ownership fields such as "secure_details".
An update has been deployed to resolve an issue where some requests to the /reservations endpoint were returning a 500 Internal Server Error.
The behavior was limited to the API response only — reservations were still being created successfully — but the response payload was failing due to data becoming corrupted under certain conditions.
The update ensures the request is now handled and parsed reliably, and the endpoint returns the appropriate success response as expected.
An update has been deployed to resolve an issue where the "down_payment_amount" returned from POST/unit_quotes, POST/reservations, and the system-side reservation record could become inconsistent under certain conditions. The "down_payment_amount" calculation and persistence flow now align across all endpoints.
The Booking Handler via POST/reservations has been updated to block reservation requests for supplier accounts that are not active.
Reservations will now be rejected when:
The supplier is no longer signed up, or
The supplier’s account has reached its expiration date.
The API now returns an appropriate error response when booking attempts are made into inactive or expired accounts.
A deployment has been released to re-implement support for the Channel Host Fee (CHFSYSTEM) . Partners can now include the Channel Host Fee as a discount line item within the "financials" object when creating reservations through the /reservations endpoint. This ensures accurate calculation for connected channels.
Example usage:
An update was deployed to resolve an issue with the /unit_quotes endpoint where the "item": "Booking Fee" was not being included in the response when configured as a Flat Fee. The "item": "Booking Fee" now returns and calculates correctly for all fee types.
An update has been made to resolve an issue where "extras" configured as "mandatory: true" were not being included in the "financials" object of the /unit_quotes endpoint. These "extras" now return correctly and align with system configurations.
