Availability

Availability in MyRentalCalendar is night-based: a stay from the 10th to the 14th occupies the nights of the 10th, 11th, 12th and 13th — the departure date is free again. Double bookings are impossible by construction (one database row per occupied night), so what this endpoint returns is the ground truth, not a cache.

Request

curl "https://api.myrentalcalendar.com/partner/v1/availability?unit=marina-loft-2br&from=2026-09-01&to=2026-10-01" \
  -H "Authorization: Bearer $STAYOS_KEY"

Requires scope read:availability. The range [from, to) may span at most 366 days per request.

Response

{
  "unit": "marina-loft-2br",
  "from": "2026-09-01",
  "to": "2026-10-01",
  "blockedNights": ["2026-09-03", "2026-09-04", "2026-09-05", "2026-09-06"]
}

blockedNights contains every unbookable night, from two sources:

1. Stays — confirmed bookings, options, owner stays, maintenance blocks.
2. Turnover blocks — nights the unit stays off the market after a checkout so housekeeping can finish. They are as real as a booking: a stay may not start or cross them.

Any night not in the list can be sold — subject to the unit’s minimum stay, which POST /quote enforces for you.

Building a calendar UI

Fetch the widest range you display (up to a year) in one call and render every listed night as unavailable. Re-fetch on navigation rather than caching for long: the calendar changes whenever the agency takes a booking.