Night Audit Report has been Enhancement with New Option to Build Screen "Include Inactive Category" When the Option is Ticked, the Report will include All Rooms which were/are assigned to Inactive Categories covering the Build Selection Date 

Help Article - Night Audit Report

Generic Financial Export has been Enhancement with New Option to Build Screen "Include Inactive Category" When the Option is Ticked, the Report will include All Rooms which were/are assigned to Inactive Categories covering the Build Selection Date 

Help Article - Generic Financial Export

Add on Bookings Report has been Enhanced to Show "Guest No".

Help Article - Add on Reservation

AR Statements Report has been Enhanced with New Filter "As of Date". Selection of the Date on this Filter would enable to user to see Account Details For Transactions Selected Date Range as of the Selected Date 

Flash Report has been Enhancement with New Option to Build Screen "Include Inactive Category" When the Option is Ticked, the Report will include All Rooms which were/are assigned to Inactive Categories covering the Build Selection Date 

Help Article - Flash Report

Advance Deposit Report has been enhanced to show the Receipts which are made on the Reservation Account on the Day of the Arrival. To View the Receipts made on the Reservation Arrival Date, the New Option on the Build Screen "Include Receipts on Arrival Date" must be Selected 

Help Article - Advance Deposit Report

We’ve fixed discrepancies with category banners and messaging on the Booking Engine 🏷️. Sold-out banners and minimum night stay restrictions now display correctly, even for multi-night bookings where some nights have no available inventory.

What’s Changed?

• Sold-out banners now accurately reflect availability.
• Minimum night stay restrictions are correctly applied and shown.
• Multi-night bookings display accurate messaging when some nights are restricted or unavailable.
• Guests now see consistent and reliable information when selecting dates and categories.

We’ve added a country code dropdown on the guest mobile number field 📱. This ensures that when a property uses SMS for triggered correspondence, guests will reliably receive messages.

What’s Changed?

• Guests can now select their country code when entering mobile numbers.
• SMS communications from properties are correctly routed to the guest’s number.
• Improves reliability of triggered SMS messages for all bookings.

Summary

This Live release brings together the improvements and fixes previously delivered across the Beta cycle, with a focus on availability and rate calculation workflows, guest correspondence support, and reservation reliability.

Included in this Live release:

• Availability & Rate Calculation Enhancements
  Improvements to availability and rate calculation workflows, along with new API support for managing guest correspondence notes.
  👉 Beta details: https://releasenotes.rmscloud.com/rest-api-v10.26.10.1----beta-3ECvn2
• Reservation Workflow Fixes & Stability Improvements
  Fixes to reservation creation and update workflows, ensuring rate-based configuration fields are correctly applied and resolving timeout issues when overriding rates.
  👉 Beta details: https://releasenotes.rmscloud.com/rest-api-v10.26.19.2----beta-1eL7Q4

Notes

• This release is now available in Live
• Release Date: February 11, 2026 (AEDT)
• Partners can begin using these changes in production immediately
• Please report any issues through standard support channels:
  https://rmsapi.zendesk.com/hc/en-gb/requests

Important Notice: API Rate Limit Updates

We’re introducing new global rate limits for a set of Group Allotment and reference data REST API endpoints (including Companies and Travel Agents).

These endpoints return low‑change data and are intended to be used with caching and webhooks, rather than continuous polling. The changes below are designed to improve platform stability and ensure consistent performance for all partners.

Why this change is being made

We’ve observed sustained high‑volume polling on several Group Allotment endpoints that return low‑change data. In most cases, these resources are expected to be:

• Cached after initial retrieval
• Refreshed only when changes occur via webhook notifications

Continuous polling creates unnecessary load and can impact overall platform performance.

What’s changing (Effective Date: February 23, 2026)

The following endpoints will be limited to 60 requests per minute:

• GET /groupAllotments
• GET /groupAllotments/{id}
• GET /groupAllotments/{id}/allotments
• GET /groupAllotments/{id}/companies
• GET /groupAllotments/{id}/travelAgents
• GET /companies
• GET /travelAgents

Webhooks (recommended approach)

Webhooks should be used as the primary mechanism for detecting changes:

Group Allotments

• Events: create, update, delete
• Payload includes groupAllotmentId, which can be used to re‑query the specific resource if needed

Agents

• Events: create, update
• Payload includes agentId for retrieving updated agent details

Using webhooks avoids unnecessary polling and ensures updates are processed only when changes occur.

Webhook schema:
Webhooks

What you need to do

• Cache responses from the affected endpoints
• Use webhooks to detect changes
• Re‑query only the affected resource when a webhook event is received
• Avoid continuous polling
• Ensure any manual refreshes stay within the new rate limits

Enforcement

• Rate limits are applied globally
• Sustained traffic above the limits may be throttled or blocked

Need help?

If you have questions or would like assistance reviewing your implementation, please contact API Support:
Partner & API Support