REST API v10.26.191.2 — Beta
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 includingchargeRequiredDailyandchargeDailyIncludeToDateGET /reservations/requirements— Search reservation requirements, now includingchargeRequiredDailyandchargeDailyIncludeToDate
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 RequirementPOST /requirements/master/{id}/categoryAccess— Add categories to the access list for a master RequirementPUT /requirements/master/{id}/categoryAccess— Replace the category access list for a master RequirementDELETE /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