Read and set Escapia unit booking restrictions (minimum stay, check-in/checkout availability) via GraphQL Gateway operations
domain: developer.escapia.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate to the Escapia GraphQL Gateway as with other operations.
Query bookingRestrictionsByDateRange for a unit to retrieve per-date check-in and checkout availability plus minimum-night-stay, distinguishing date-level overrides from the effective value.
Set restrictions with the bookingRestriction_SetDateBookingRestrictionsByUnit mutation, keeping minimum-night-stay within the documented 1-98 range.
Restrict the date range to today through two years out, matching the same window used for nightly rates.
Watch the rate-limit response headers and back off exponentially on too-many-requests errors.
Known gotchas
Like nightly rates, booking restrictions can only be set via this mutation, not removed - there is no documented way to clear an override back to default via the API.
Exact numeric rate limits are not published in the docs; rely on the response headers rather than hardcoding a limit.
Reservation, guest, and trust-accounting operations were not found on the current GraphQL Gateway docs - do not assume they exist on this surface without separately confirming.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?