Authenticate with a Guesty Bearer token obtained via the client_credentials OAuth flow using your client ID and secret.
GET the availability calendar for a specific listing by calling the calendar endpoint with the listing ID and a date range (startDate, endDate) to retrieve a day-by-day availability and blocking status.
Each calendar day record indicates whether the date is available, blocked (by the host), or booked (by a reservation); it also includes the nightly price and minimum stay for that date.
To block dates (e.g., owner holds, maintenance), send a PUT or POST request to the calendar blocks endpoint with the listing ID, start date, end date, and block reason.
To update pricing for a date range (dynamic pricing override), PATCH the calendar pricing endpoint with the listing ID, date range, and the new nightly rate.
Changes to availability propagate to connected OTA channels (Airbnb, Vrbo, Booking.com) automatically via Guesty's channel management layer; monitor channel sync status in the listing's channel fields.
Known gotchas
Calendar updates to OTA channels are asynchronous; a successful API response from Guesty confirms the update was accepted, not that it has already propagated to all channels.
Minimum stay rules set at the listing level can be overridden at the calendar day level, but some channels (e.g., Airbnb) have their own minimum-stay enforcement that may not respect single-day overrides applied via Guesty.
For portfolios with many listings, batch calendar update endpoints should be used where available; sending individual day-level requests for each listing and each date is not scalable and will trigger rate limiting.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp