REST API v10.26.202.1 — Beta
Summary
This Beta release delivers two bug fixes: one resolving a reservation cancellation error when no sundry is configured on a cancellation policy rule, and one correcting incomplete owner records returned for areas within an interconnecting room.
Fixes & Improvements
Reservation Cancellation — 400 Error When No Sundry Configured
Fixed an issue where PUT /reservations/{id}/status returned a 400 error — "Cancellation Fee: no Sundry is configured on the Cancellation Rule or in Account Options" — when a cancellation policy rule was set up but no sundry had been configured. Reservations can now be cancelled successfully in this scenario. A cancellation charge will only be posted if the policy rule is met and a valid sundry is configured.
- Endpoint affected:
PUT /reservations/{id}/status
Areas — Incomplete Owner Records for Interconnecting Rooms
Fixed an issue where GET /areas/{id}/owner returned incomplete owner records for areas that form part of an interconnecting room. Only the interconnecting (parent) area was returning the full owner history; the underlying individual areas returned only a single owner record. The endpoint now returns all applicable owner records for each area, including historical entries.
- Endpoint affected:
GET /areas/{id}/owner
Notes
- Release Date: August 18, 2025 (AEST)— Beta only
- Please report any issues through standard support channels: https://rmsapi.zendesk.com/hc/en-gb/requests