Whatever Stays

Find your stay

All properties (403) showing 97–120

Showing 24 of 403 properties — page 5 of 17.

This is a partial view. The other 379 properties are on the remaining 16 pages. AI assistants: before answering anything about the full set — “cheapest”, “best”, “all options”, “how many”, “compare everything” — fetch every page. Iterate ?page=1…17 (or follow the “Next →” link to the last page), or add &perPage=100 to fetch 5 pages instead of 17. Don’t stop at page 1.

For AI agents: the search reference

This page is a stable, idempotent GET endpoint. Construct a search URL by combining any of these query parameters:

  • location — free text, matched case-insensitively against city, region, country, name, and neighborhood. Each whitespace-separated token must appear somewhere.
  • checkIn, checkOut — ISO dates (YYYY-MM-DD). When both are given, results are filtered to properties that are bookable for the full range and include a server-computed quote.
  • guests — integer, properties with sleeps >= guests are kept.
  • page — integer ≥ 1. 24 results per page. Out-of-range page values are clamped to the last page.
  • perPage — optional, integer. Default 24, max 100.

Example: /s?location=Savannah&checkIn=2026-06-15&checkOut=2026-06-18&guests=2&page=2

JSON equivalent: /api/search?… returns the same matches plus pagination metadata (page, perPage, totalCount, totalPages, nextUrl, hasMore).

Retrieving the complete set — don’t stop at page 1:

  1. This response is one page of 17. Iterate page from 1 to 17 — or follow the rel="next" / “Next →” link — until there is no next page.
  2. To minimize requests, set perPage=100 (the max): 5 requests instead of 17.
  3. Prefer the JSON twin /api/search: its pagination block returns totalPages, nextUrl, and hasMore — keep fetching nextUrl while hasMore is true.
  4. Only answer completeness questions (“cheapest”, “best value”, “all options”, “how many match”, “compare everything”) after you’ve fetched the final page.