Add pagination to responses
There are some endpoints (for example: the /reservations/search endpoint) that allow us to query certain objects like reservations that were created or modified in a certain time interval. If the time interval causes Mews to fetch too many objects, it will return a 408. This can be less straightforward for the caller as the caller does not know in which time interval most creations/modifications happened and the caller will thus keep calling the endpoint until the time interval is finally small enough for the request to succeed. As you can see, this can/will result in several consecutive failing calls which results in a longer wait time for the caller (you need to wait for the response to know if the time interval is ok and if not, you actually waited for nothing) and several unnecessary queries in your database as the result isn't used.
To overcome this, we would like to suggest adding pagination to your endpoint. Pagination means that you will only return X objects in the response (lowering the impact on your database) and let the user know if there are more objects that match the time interval filter so they can crawl the next page. This means that each call be the caller will also be successful and the wait wasn't for nothing
Review of Mews Search starting and in exploration phase