Summary

This Live release brings together the improvements, fixes, and new features previously delivered across the Beta cycle, spanning error handling improvements, notes management enhancements, guest classification management, reservation reliability fixes, and new headless payment tokenisation support.

Included in this Live release:

• Error Handling & HTTP Status Improvements Fixes to incorrect HTTP status codes returned during transient errors in payment processing, and resolution of a 500 error on the NPS Results Report endpoint in Beta and Test environments. 👉 Beta details: https://releasenotes.rmscloud.com/rest-api-v10.26.65.2----beta-S8aju
  
  
• Company & Travel Agent Notes — All Properties Support New support for creating and updating notes scoped to All Properties for company and travel agent records via propertyId: 0, aligning API behaviour with the RMS UI. Validation added to PUT requests to enforce scope consistency. 👉 Beta details: https://releasenotes.rmscloud.com/rest-api-v10.26.77.4----beta-XO8UM
  
  
• Guest Classifications, Reservation Fixes & Stability Improvements New guest classification endpoints, a fix for dynamic pricing rate consistency on pencil reservations, and a fix for a 404 error incorrectly returned when creating reservation holds. 👉 Beta details: https://releasenotes.rmscloud.com/rest-api-v10.26.90.1----beta-104VXi
  
  
• Guest Classifications, Company Branch Offices & Credit Card Tokenisation New endpoints for managing company branch office relationships, and a merchantReference field for headless payment tokenisation via POST /guests/{id}/creditCard. 👉 Beta details: https://releasenotes.rmscloud.com/rest-api-v10.26.105.2----beta-4BL7va
  
  
• 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: April 22, 2026 (AEST)
• Partners can begin using these changes in production immediately
• ⚠️ Upcoming Breaking Change — June 2, 2026 (AEST): A global maximum record limit of 50,000 will be enforced across POST /transactions/allocations/search, POST /transactions/search, POST /guests/search, and POST /reservations/search. Requests exceeding this limit will return HTTP 400. If your integration requests more than 50,000 records in a single call on any of these endpoints, please reduce your limit or implement pagination before this date. https://releasenotes.rmscloud.com/rest-api-v10.26.105.2----beta-only-breaking-change---maximum-query-limit-4CTw1q
• Please report any issues through standard support channels: https://rmsapi.zendesk.com/hc/en-gb/requests

We've fixed an issue where some guests were seeing a "card type not supported" error when attempting to pay through the new Booking Engine, even when using a valid card. In some cases this also resulted in payment being taken without a receipt appearing in the reservation. Both issues have been resolved.

We've resolved an issue where a small number of bookings made through the new Booking Engine with RMS Pay were being processed and payment taken, but the booking wasn't being saved correctly in RMS - appearing as an abandoned quote with no receipt and the RMSPay merchant account showed the reference number as 'Undefined'. These bookings will now save and receipt correctly.

We've resolved an issue where guests completing a 3D Secure (3DS) payment challenge were not being redirected to the booking confirmation page successfully on the new Booking Engine for RMSPay customers. Guests will now land on the confirmation page as expected after completing their 3DS verification.

We've improved how the new Booking engine recognises accepted card types during checkout. Previously, cards set up in your RMS account using non-standard naming (such as "Vis Cred", "Visa Debit", or "M.Card debit") weren't always being recognised by the payment gateway, causing valid cards to be declined at the point of booking. This has now been resolved - a wider range of card naming conventions are supported, so guests experience fewer payment errors.

Summary

This release introduces a platform-wide maximum record limit of 50,000 across all REST API endpoints that accept a limit parameter. Requests exceeding this value will now return HTTP 400 Bad Request. Previously, oversized requests were silently truncated.

Partners using high-volume search queries should review the affected endpoints below and update their integrations before the Live release.

Breaking Change

Global Maximum Query Limit — 50,000 Records

The following endpoints are affected:

• POST /transactions/allocations/search
• POST /transactions/search
• POST /guests/search
• POST /reservations/search

What's changing:

• Requests with a limit value above 50,000 will return HTTP 400 Bad Request with an explicit error message
• Requests at or below 50,000 are unaffected
• Endpoints that already have their own explicit limit lower than 50,000 are unaffected

Action required: If your integration passes a limit value greater than 50,000 on any of the above endpoints, you will need to update your queries to use pagination or reduce the limit before the Live release. Partners identified as impacted have been contacted directly.

Notes

• Available in Beta only. Live release is tentatively scheduled for 2 June 2026, subject to Beta validation.
• Please report any issues through standard support channels: https://rmsapi.zendesk.com/hc/en-gb/requests

Summary

This Beta release introduces three new feature areas — guest classifications, company branch offices, and headless payment tokenisation — along with a platform-wide query limit change. Partners using high-volume search endpoints should review the Breaking Change section below ahead of Live.

New Features

Guest Classifications — New Endpoints

New endpoints have been added to support full management of guest classifications, enabling retrieval, assignment, replacement, and removal of classifications on a guest record.

New endpoints:

• GET /guestClassifications — Retrieve available classification types
• GET /guests/{id}/classifications — Get classifications assigned to a guest
• POST /guests/{id}/classifications — Add a classification to a guest
• PUT /guests/{id}/classifications — Replace the full classification set for a guest
• DELETE /guests/{id}/classifications/{classificationId} — Remove a specific classification from a guest

Company Branch Offices — New Endpoints

New endpoints have been added to support programmatic management of branch office relationships between company records. This removes the need to maintain these links manually in the RMS UI.

When adding branch offices, you can optionally copy all assigned rates from the master company to each branch office at the time of creation by passing "assignParentRates": true. Note: rate copying occurs at creation time only and does not establish an ongoing sync.

New endpoints:

• POST /companies/{parentId}/branchOffices — Link one or more companies as branch offices of a master company
• GET /companies/{parentId}/branchOffices — Retrieve all branch offices for a master company
• DELETE /companies/{parentId}/branchOffices/{companyId} — Remove a branch office link

Credit Card Tokenisation — merchantReference Field

POST /guests/{id}/creditCard now accepts an optional merchantReference field. This integrator-supplied string (max 100 characters) is stored at token creation time and acts as the lookup key when retrieving token details via searchGuestRmsPayToken.

This enables fully headless payment flows — for example, AI voice agents collecting card details over the phone — to complete the rmsPay flow without requiring any UI interaction from the guest.

• Endpoint affected: POST /guests/{id}/creditCard

Note: RMS does not enforce uniqueness on merchantReference. The integrator is responsible for managing reference values.

⚠️ Breaking Change — Global Maximum Query Limit: 50,000 Records

A global maximum record limit of 50,000 is being introduced across all REST API endpoints that accept a limit parameter. Previously, requests with limits up to 1,000,000 were accepted and silently truncated. From this release, any request exceeding 50,000 will return HTTP 400 Bad Request.

Affected endpoints:

• POST /transactions/allocations/search
• POST /transactions/search
• POST /guests/search
• POST /reservations/search

Action required: If your integration currently requests more than 50,000 records in a single call on any of the above endpoints, you will need to reduce your limit value or implement pagination before this change reaches Live. Partners identified as using limits above 50,000 have been contacted directly.

Endpoints with an existing explicit limit lower than 50,000 are unaffected.

Notes

• Release Date: April 16, 2026 — Beta only
• Please report any issues through standard support channels: https://rmsapi.zendesk.com/hc/en-gb/requests

We've resolved an issue where some RazorPay bookings were not being confirmed after a successful payment.

What was happening? In certain cases, guests who navigated away, refreshed the page, or pressed the back button during the RazorPay payment process would have their payment processed but their booking not confirmed. This was because the frontend was not sending the final request to the booking confirmation API when the payment flow was interrupted by a page navigation.

What's been fixed? Guests are now kept on the payment processing page while their RazorPay transaction completes, preventing accidental navigation away before the booking is confirmed. This ensures the confirmation API is reliably called after a successful payment, so bookings are completed as expected.

Who does this affect? Properties using RazorPay as their payment gateway through IBE+.

Summary

This Beta release includes two fixes and one new feature enhancement. Partners are encouraged to validate these changes in Beta and report any issues via standard support channels.

New Features

Guest Classifications — New Endpoints

New endpoints have been added to support full management of guest classifications, enabling retrieval, assignment, replacement, and removal of classifications on a guest record. 

New endpoints:

• GET /guestClassifications — Retrieve available classification types SwaggerHub ↗
• GET /guests/{id}/classifications — Get classifications assigned to a guest SwaggerHub ↗
• POST /guests/{id}/classifications — Add a classification to a guest SwaggerHub ↗
• PUT /guests/{id}/classifications — Replace the full classification set for a guest SwaggerHub ↗
• DELETE /guests/{id}/classifications/{classificationId} — Remove a specific classification from a guest SwaggerHub ↗

Fixes & Improvements

Pencil Reservation — Dynamic Pricing Rate Consistency

• Issue: When a rate type was applied to a pencil reservation via the API, the quoted rate was not being preserved. If dynamic pricing changed before the pencil was converted to Unconfirmed/Confirmed, the reservation would be re-quoted at the new rate — producing a different rate than originally presented to the guest.
• Fix: Applying a rate type to a pencil reservation via the API now correctly preserves the quoted rate and occupancy snapshot. The rate will be retained when the pencil is subsequently converted.
• Endpoints affected: PATCH /reservations/{id}, PUT /reservations/{id}/status

Reservation Hold — 404 Error on Create

• Issue: When creating a new reservation hold via the API, a 404 Not Found error was returned despite the hold record being successfully created.
• Fix: POST /reservations/{id}/holds now returns the correct 200 OK response with the hold record payload upon successful creation.
• Endpoint: POST /reservations/{id}/holds

Notes

• Release Date: April 8, 2026 Beta only
• Dependencies: None
• There is no impact to Live environments.
• Please report any issues through standard support channels: https://rmsapi.zendesk.com/hc/en-gb/requests

Your guests can now pay with Apple Pay directly from the guest page- making checkout faster, more familiar, and more secure.

How it works

Apple Pay appears as a payment option on the guest page alongside existing methods. Guests on an Apple device can pay instantly. Guests on a non-Apple device will still see the option- they can select it and scan the QR code with their iPhone to complete the payment seamlessly.

Works just like your existing card payments

Tokens and receipts behave exactly the same as credit card transactions, so your team won't need to change a thing. That means:

• ✅ Refunds can be processed as normal
• ✅ Pre-auth tokens can be created for same-day arrivals
• ✅ All existing RMSPay workflows apply

A couple of things to know

Apple Pay will not appear as a payment option when a property's deposit rule is set to No Deposit & Tokenize. In that case, the option is automatically hidden - no action needed on your end.