Skip to main content
Long lists come one page at a time. The request sends page and pageSize. The response puts those values, plus hasNext and hasPrevious, under pagination. The list itself stays beside that object, for example bookings. page starts at 1 and is at most 100. Omit it for page 1. pageSize is 500 when omitted, and at most 1000. The offset is (page - 1) * pageSize. There is no separate offset field.
hasNext is true when more entries follow this page. The next request raises page by one. hasPrevious is true when page is greater than 1. A page past the end returns an empty list and hasNext false. hasPrevious follows the page number. The response does not include a total count. page below 1 or above 100, pageSize outside 1 to 1000, or a value that is not an integer returns 400 and INVALID_FILTER. Bookings use this today. The endpoint sets the order. Bookings are ordered by date and booking id, newest first.