Summary

This Live release delivers enhancements to reservation requirement responses, a new guest image upload endpoint, full CRUD support for Requirement Category Access, and a fix for a 503 error on reservation search by guest surname.

Included in this Live release:

• Reservation Requirements — chargeRequiredDaily and chargeDailyIncludeToDate fields added to requirement responses, enabling accurate fee calculation in kiosk and self-check-in flows.
• Guest Image Upload — New PUT /guests/{id}/image endpoint allows guest images to be uploaded directly via the API.
• Requirement Category Access — New endpoints to get, add, replace, and remove category access entries on master Requirements.
• Reservation Search Fix — POST /reservations/search no longer returns a 503 when filtering by guest surname.

👉 Beta details: https://releasenotes.rmscloud.com/rest-api-v10.26.191.2----beta-1Ph3uE

Notes

• This release is now available in Live
• Release Date: July 14, 2026 (AEST)
• 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

Summary

This Beta release adds new fields to reservation requirement responses, a new endpoint for uploading guest images, and a new set of endpoints for managing Requirement Category Access. It also includes a fix for a 503 error returned by POST /reservations/search when filtering by guest surname. 

New Features

Reservation Requirements — chargeRequiredDaily and chargeDailyIncludeToDate Fields

Two new boolean fields have been added to reservation-level requirement responses. chargeRequiredDaily indicates whether a requirement is charged on a per-day basis; chargeDailyIncludeToDate controls whether the departure date is included in that daily charge calculation. These fields allow integrators to accurately calculate requirement fees without relying on additional lookups or UI-side logic.

Endpoints affected:

• GET /reservations/{id}/requirements — Returns requirements for a reservation, now including chargeRequiredDaily and chargeDailyIncludeToDate
• GET /reservations/requirements — Search reservation requirements, now including chargeRequiredDaily and chargeDailyIncludeToDate

Guest Image Upload — New Endpoint

Integrators can now upload an image (such as a passport or ID document scan) directly to a guest profile via the REST API. Previously this was only possible through the RMS UI.

New endpoint:

• PUT /guests/{id}/image — Upload an image to a guest profile

Requirement Category Access — New Endpoints

A new set of endpoints enables integrators to manage Category Access on master Requirements. Category Access controls which property categories a Requirement appears in, using an allow-list model. This gives integrators programmatic control over Requirement visibility across a multi-category property setup, without requiring manual configuration in the RMS UI.

New endpoints:

• GET /requirements/master/{id}/categoryAccess — Retrieve the category access list for a master Requirement
• POST /requirements/master/{id}/categoryAccess — Add categories to the access list for a master Requirement
• PUT /requirements/master/{id}/categoryAccess — Replace the category access list for a master Requirement
• DELETE /requirements/master/{id}/categoryAccess — Remove categories from the access list for a master Requirement

Fixes 

Reservation Search — 503 Error When Filtering by Guest Surname

POST /reservations/search was returning a 503 Service Unavailable error when the request included a guestSurname filter. The endpoint now returns a valid result set, or an empty array when no matches are found.

Notes

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

Summary

This Live release delivers two fixes to reservation tariff handling. Properties using Nightly Rate accounting will now see correct per-night tariff records from API-created reservations, and pencil reservations will correctly recalculate tariffs when the rate type is updated more than once.

Included in this Live release:

• Reservations — Nightly Rate accounting — API-created reservations now generate per-night tariff records when the property is configured for Nightly Rate accounting. 
• Reservations — Pencil reservation tariff recalculation — Tariff values now recalculate correctly on every rate type change, not just the first assignment.

👉 Beta details: https://releasenotes.rmscloud.com/rest-api-v10.26.167.3----beta-20B5m0?psig=Mpx7z7vJgO61MKzP9abenS5geFulmT0aAI2Nubz

Notes

• This release is now available in Live
• Release Date: 24 June 2026 (AEST) 
• 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

Summary

This Beta release delivers two fixes to reservation tariff behavior. Reservations created via the API now correctly inherit the property-level Nightly Rate accounting configuration, and rate type changes on pencil reservations now trigger a full tariff recalculation in all cases. 

Fixes & Improvements

Reservations — Nightly Rate accounting now applied correctly on creation

When a property was configured to use Nightly Rate from their accounting configuration, reservations created through the API were incorrectly generating a single total tariff for the entire stay rather than individual nightly tariffs. The API now correctly inherits the property-level accounting configuration.

Affected endpoint: POST /reservations

Reservations — Tariff recalculation on pencil reservation rate type change

When updating a pencil reservation's rateTypeId via PATCH /reservations/{id}, the tariff was only recalculated the first time a rate was assigned. If the rate was subsequently changed to a different rate type, the baseRate and totalRate values in actualAccount retained the original rate's amounts instead of reflecting the new rate. The recalculation logic now triggers whenever the rate type changes to a different value, covering both first-time assignment and subsequent rate changes.

Affected endpoint: PATCH /reservations/{id}

Notes

• Release Date: 23 June 2026 (AEST)  — Beta only
• Please report any issues through standard support channels: https://rmsapi.zendesk.com/hc/en-gb/requests

Summary

This Live release delivers error handling and data accuracy improvements across the API, covering webhooks, transactions, discounts, and reports.

Included in this Live release:

• Webhooks — Fixed 500 error on PUT /webhooks/{id} for inactive or non-existent webhook IDs; endpoint now returns 404 Not Found.
• Transactions — Credit card fee values submitted via POST /transactions/receipt are now rounded to 2 decimal places, preventing account balance mismatches and refund processing errors.
• Reservations — POST /reservations/discounts/search now correctly returns discounts with validation rules applied, instead of returning 204 No Content.
• Reports — POST /reports/auditTrail no longer returns a 500 error when glCodeIds is passed as an empty array.

👉 Beta details: https://releasenotes.rmscloud.com/rest-api-v10.26.118.1----beta-3CuvTy

Notes

• This release is now available in Live
• Release Date: 3 June 2026 (AEST)
• 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

Summary

This Live release enforces a maximum record limit of 50,000 on key search endpoints. The change improves platform stability and ensures consistent behavior across high-volume query patterns. Requests exceeding the limit now return HTTP 400 Bad Request rather than being silently truncated.

Included in this Live release:

• Breaking Change: Maximum Query Limit — A cap of 50,000 records is now enforced on transaction, guest, and reservation search endpoints; requests exceeding this value return HTTP 400 Bad Request.
  👉 Breaking Change Details: https://releasenotes.rmscloud.com/rest-api-v10.26.105.2----beta-only-breaking-change---maximum-query-limit-4CTw1q
• Beta release: 👉 https://releasenotes.rmscloud.com/rest-api-v10.26.105.2----beta-4BL7va

Notes

• This release is now available in Live
• Release Date: 2 June 2026 (AEST)
• Partner notification sent 17 April 2026: https://mail.rmscloud.com/hey-partner-your-rms-live-release-is-here-0-0-0-0-0?hs_preview=TVgGuAQq-211134018457
• Please report any issues through standard support channels: https://rmsapi.zendesk.com/hc/en-gb/requests

Summary

This Beta release delivers four fixes addressing error handling and data accuracy improvements across the API. Partners are encouraged to test the affected endpoints ahead of the Live release.

Fixes & Improvements

Webhooks — PUT /webhooks/{id} Returns 500 for Inactive Webhooks

Calling PUT /webhooks/{id} with an inactive or non-existent webhook ID was incorrectly returning a 500 Internal Server Error instead of a meaningful error response. This has been fixed. The endpoint now returns 404 Not Found in these cases, allowing integrators to handle the response appropriately.

• Endpoint affected: PUT /webhooks/{id}

Transactions — Credit Card Fee Rounding via POST /transactions/receipt

When a credit card fee was submitted via POST /transactions/receipt with more than 2 decimal places (e.g. 0.9608), the value was stored as-is in RMS. This caused a rounding mismatch on the account balance, which prevented users from processing valid refunds — the system would reject a refund that appeared within the available credit balance because the stored fee value didn't align to standard 2-decimal currency precision.

This has been fixed. Credit card fee values are now rounded to 2 decimal places at the point of storage, ensuring account balances are calculated correctly and refunds can be processed without errors.

This fix affects any integration using POST /transactions/receipt that submits credit card fee values with more than 2 decimal places.

• Endpoint affected: POST /transactions/receipt

Reservations — Discounts with Validation Rules Return 204 in POST /reservations/discounts/search

POST /reservations/discounts/search was returning 204 No Content for discounts that had validation rules applied (e.g. date made ranges, stay date ranges), even when the search criteria matched those rules. Discounts without validation rules were unaffected.

This has been fixed. The endpoint now returns all eligible discounts, including those with validation options configured, provided the request parameters fall within the defined rules.

• Endpoint affected: POST /reservations/discounts/search

Reports — POST /reports/auditTrail Returns 500 Internal Server Error

Calling POST /reports/auditTrail with an empty glCodeIds array was causing a 500 Internal Server Error. This affected all requests regardless of other parameters supplied.

This has been fixed. The endpoint now returns audit trail data without filtering by GL code when glCodeIds is passed as an empty array.

• Endpoint affected: POST /reports/auditTrail

Notes

• Release Date: June 02, 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

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

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