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