Push availability, nightly rates, and minimum-length-of-stay updates to Uplisting via its asynchronous calendar update endpoint
domain: support.uplisting.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Request Uplisting API access (invite-only) and obtain the Basic-auth API key already used for read calls.
POST to the calendar update endpoint for a listing with available, day_rate, minimum_length_of_stay, closed_for_arrival, and closed_for_departure fields, for a single date or a from/to range.
Register an HTTPS notification_url to receive an asynchronous success/failure callback, since the update is applied in the background.
Expect an immediate 202 Accepted response with a request_id, then correlate the later callback to that request_id.
Respect the documented per-IP and per-property rate limits when batching updates across many listings.
Known gotchas
The write call returns 202 immediately - the actual calendar change is applied asynchronously (typically under a minute) and confirmed only via the callback, not the initial response.
The 'to' date in a date range is exclusive, and updates can be scheduled up to three years in advance.
Rate limits are enforced per IP and per property - throttle bulk updates accordingly or expect 429 responses.
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?