Pagination

To improve reliability and performance for everyone, Apaleo is enforcing standard pagination limits on all APIs. We are introducing standard default and maximum page sizes:

Type Default Maximum Pattern
Business data (reservations, folios, units, etc.) 20 200 pageNumber / pageSize
Analytical data (audit logs, usage, exports) 50 500 cursor / limit

If your request doesn’t specify a pageSize, the default applies automatically. If you use pageSize that exceeds maximum value, your request will be rejected.

Why this benefits you:

  • Faster responses: smaller, more consistent payloads reduce latency and timeouts.
  • Higher reliability: queries no longer fail due to size, which improves long-term stability.
  • Predictable load: better experience during peak hours.
  • Clear expectations: all endpoints now behave the same — no more guesswork per API.

Simply put: paging correctly will make your integration more reliable and more scalable.

What you need to do

  1. Check your API calls for endpoints that:
    • Do not specify a pageSize, or
    • Request more than 200 (for business data).
  2. Add proper pagination using pageNumber and pageSize (or cursor and limit for logs).
  3. Handle pagination loops in your integration (fetch until no more data).

Example (business data):

GET /reservations?pageNumber=1&pageSize=100

Example (analytical data):

GET /audit-logs?limit=200&cursor=eyJpZCI6...