Summary

This Beta release introduces a new endpoint for retrieving reservation repeat charge schedules, a way to brand RMSPay hosted payment pages with custom CSS, and several new fields across sundries, transactions, reservations, and booking sources. It also includes a fix for audit trail logging on API-created sundries. There are no breaking changes in this release.

New Features

RMSPay — Custom CSS Branding

You can now apply your own branding to the RMSPay hosted payment page by passing an optional cssCustomUrl field with a link to your own CSS file. This lets you style elements such as button and border colors to match your brand. Requests that omit the field continue to work exactly as before, with no change in behavior. RMS does not host, validate, or modify the CSS file — you're responsible for hosting it at a URL that's publicly accessible without authentication.

Endpoints affected:

• POST /guests/{id}/rmsPayPayment — accepts the new cssCustomUrl field
• POST /guests/{id}/rmsPayToken — accepts the new cssCustomUrl field
• POST /guests/{id}/rmsPayToken/preAuth/{resId} — accepts the new cssCustomUrl field

Repeat Charges — New Endpoint & Sundry Field

You can now retrieve repeat charge schedules directly from the API instead of relying on a database mirror. The new endpoint returns each schedule's amount, frequency, linked sundry and account, start/cutoff dates, and related settings for up to 1,000 reservation IDs per call. Reservations with no repeat charge schedule simply won't appear in the results. Alongside this, sundries now expose whether repeat charges using that sundry post as a single combined transaction rather than one per occurrence.

New endpoints:

• POST /reservations/repeatCharges/search — Retrieve repeat charge schedules for a list of reservation IDs

Endpoints affected:

• GET /sundries — now returns postSingleTransactionForRepeatCharges
• GET /sundries/{id} — now returns postSingleTransactionForRepeatCharges

Transactions — Virtual Card Identification

Receipt transactions now indicate whether the credit card token used for the receipt is flagged as a virtual card, regardless of whether the token came from an existing saved card or a new charge auto-tokenized by the payment gateway.

Endpoints affected:

• POST /transactions/search — now returns isVirtualCard
• GET /transactions/{id} — now returns isVirtualCard

Reservations — Rate Posted Indicator

The full reservation object now includes a boolean showing whether the accommodation rate has been posted for that reservation, so integrators can track rate postings ahead of guest arrival.

Endpoints affected:

• POST /reservations/search — now returns rateCreated (when modelType: full)
• GET /reservations/{id} — now returns rateCreated (when modelType: full)

Booking Sources — Grouping Link

Booking sources now return a grouping identifier, so you can tell which grouping a booking source belongs to without a separate lookup.

Endpoints affected:

• GET /bookingSources — now returns groupingId

Fixes & Improvements

Sundries — Audit Trail Logging

Creating a sundry via the REST API did not previously write an audit trail entry, unlike creating the same sundry through the RMS9+ UI, leaving no record of who created API-originated sundries. Creating a sundry through this endpoint now records an audit trail entry consistent with UI-created sundries.

Endpoint affected:

• POST /sundries — now writes an audit trail entry on creation

Notes

• This release is now available in Beta
• Release Date: September 29, 2026 (AEST) 
• Please report any issues through standard support channels: https://rmsapi.zendesk.com/hc/en-gb/requests