Concepts
Pagination
Paging through results with page and pageSize, and how to read meta.total and hasMore.
The search pages results with page (1-indexed) and pageSize (≤100); follow _links.next until it is absent. meta.hasMore is the source of truth for "is there another page?"
What meta.total means
meta.total is a bounded count of the stays you can page through for this request, and its meaning depends on the request:
| Request | meta.total is | Caveat |
|---|---|---|
| Static (no dates) | Stays matching your geo + predicate filters | Saturates at ~100,000 for very broad viewports |
Priced (checkin/checkout) | Stays that survived availability + price filtering | total and hasMore stay consistent with _links.next |
cluster=top | Candidate areas (H3 cells) in the viewport | A lower bound for very dense viewports |
How to page
Follow _links.next until it is absent or meta.hasMore is false. Don't compute page counts from meta.total alone — treat hasMore/_links.next as authoritative.
What to read next
- Clustering — how
cluster=topchangesmeta.total - Response & supplier model — the shape you're paging through
- Search Accommodation —
page/pageSizeon the search endpoint