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