Product Updates

Check out the latest features, improvements, and product updates from RMS

2 weeks ago

REST API v10.26.118.1 — Live

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
Avatar of authorRaul Lopez
2 weeks ago

REST API Live Environment: Breaking Change - Maximum Query Limit

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:

Notes

Avatar of authorRaul Lopez
2 weeks ago

REST API v10.26.118.1 — Beta

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.

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.

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.

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.

Notes

Avatar of authorRaul Lopez
a month ago

REST API v10.26.105.2 - Live

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:

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


Avatar of authorRaul Lopez
2 months ago

REST API v10.26.105.2 — Beta Only: Breaking Change - Maximum Query Limit

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:

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
Avatar of authorRaul Lopez
2 months ago

REST API v10.26.105.2 — Beta

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
Avatar of authorRaul Lopez
2 months ago

REST API v10.26.90.1 — Beta

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

Avatar of authorRaul Lopez
2 months ago

REST API v10.26.77.4 — Beta

Summary

This Beta release includes one enhancement to company and travel agent note management via the API. Partners are encouraged to validate this change in Beta and report any issues via standard support channels.

New Features

Company & Travel Agent Notes — All Properties Support

The API now supports creating and updating notes scoped to All Properties for both company and travel agent records, by passing propertyId: 0 in POST and PUT requests. This aligns API behaviour with what is already possible in the RMS UI.

Previously, propertyId: 0 was rejected by the API, requiring notes to be managed on a per-property basis only.

Additionally, validation has been added to PUT requests to ensure the propertyId in the request matches the existing note's scope. Attempting to update an All Properties note with a specific property ID (or vice versa) will return a 400 error.

Endpoints affected:

Note: Using propertyId: 0 creates a note that applies across all properties the token has access to. API users should be intentional when using this scope — if your integration does not have access to all properties, use property-specific notes instead.

Notes

Avatar of authorRaul Lopez
3 months ago

REST API v10.26.65.2 — Beta

Summary

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

Fixes & Improvements

NPS Results Report — 500 Error Resolved

  • Issue: A 500 error was being returned for the reports/npsResults endpoint in Beta and Test environments.
  • Fix: The endpoint no longer returns a 500 error and now processes requests as expected.
  • Endpoint: POST /reports/npsResults — SwaggerHub ↗
  • Note: This issue was environment-specific and had no impact on Live environments.

Transaction Receipt — Incorrect HTTP Status for Transient Errors

  • Issue: When a transient database error occurred during payment processing, the API was returning a 400 Bad Request response. This incorrectly signalled a client-side validation error, causing payment workflows to fail rather than retry the request.
  • Fix: Transient errors of this nature now return a 503 Service Unavailable response, correctly signalling to clients that the request should be retried.
  • Endpoint: POST /transactions/receipt — SwaggerHub ↗
  • Note: Partners should ensure their integration retries on 503 responses where applicable.

Notes

Avatar of authorRaul Lopez
4 months ago

REST API Live (AUS) – Version Rollback Applied

Summary

We have rolled back the REST API Live version for Australia-based customers only to address an issue affecting reservation workflow endpoints.
The Live environment in AUS is now running v10.25.319.113. A release note will be published once the fixed version is available.

If you require access to the latest fixes and improvements in the meantime, please use the Beta environment.

Reference Live release:
https://releasenotes.rmscloud.com/rest-api-v10.26.19.2---live-2kTXfG

What happened

Following the Live deployment, an issue was identified that impacted a small number of customers in Australia.
This was related to backend database changes for a limited set of properties, where the API was not yet fully aligned with the updated environment.

To minimize disruption and restore stability, we have rolled back the Live API version for AUS-based customers only to the previous stable release.

Impact

  • Scope: Limited to a small number of customers in Australia
  • Affected functionality: Reservation workflow endpoints
  • Current Live version for AUS: 10.25.319.113
  • No action is required from partners at this time
  • API behavior has returned to the previous stable state for impacted customers

What’s next

  • A fix will be validated before a future Live release is scheduled.
  • A release note will be published when the fixed version is deployed
  • Partners who need access to the latest fixes and improvements should continue using Beta in the interim

Please report any issues or questions through standard support channels:
https://rmsapi.zendesk.com/hc/en-gb/requests


Avatar of authorRaul Lopez