Fetching appointments in a date range — GET /v1/appointments times out, is Appointment Search the right approach?

Hi,

I'm building a local integration on top of the Daylite API and need to read appointments for a rolling window (e.g. today through +60 days).

I'm currently hitting GET /v1/appointments. As far as I can tell from the reference, this endpoint lists all appointments and only accepts include_trash as a query parameter — there is no date-range filter. On my database (many years of appointment history) this request times out consistently and never returns, so I can't retrieve even a small date window this way.

My questions:

Is GET /v1/appointments expected to return the entire appointment history in a single response, or does it page internally? Is there any documented paging or limit for it?
For fetching appointments within a specific date range, is POST Appointment Search (with a date filter) the intended approach rather than the list endpoint?
If so, could you share a minimal example of the filter JSON for an appointment date range (e.g. start between two ISO 8601 timestamps), plus the recommended way to paginate the results and, if relevant, the maximum page size?
Are there any rate-limit or timeout thresholds I should design around for these calls?

Any guidance — or a pointer to an example — would be much appreciated.

Thanks!