Push rates and availability into Beds24 API v2 inventory calendar
domain: wiki.beds24.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate and obtain an access token scoped for inventory writes as described in the Beds24 v2 auth flow.
Pull the current baseline with GET /inventory/rooms/calendar for the room(s) and date range you're about to change, to compute an accurate diff.
POST /inventory/rooms/calendar with the roomId and date-keyed price/availability values to update; batch full date ranges rather than one call per date.
Immediately before finalizing a booking, use GET /inventory/rooms/offers to reconfirm the calculated price for the exact stay dates and occupancy.
Re-fetch GET /inventory/rooms/availability or /calendar afterward to confirm the push applied as expected.
Known gotchas
Beds24 enforces strict per-account API usage limits not designed for real-time-per-search traffic; cache offers/pricing and only call /offers right before completing a booking.
Price and availability live on the same per-day calendar record — omitting one field on a partial update may not change or clear it as expected, so send both explicitly.
Bulk pushes are the intended pattern (e.g., a year of data at once, refreshed roughly every 6 hours), not per-date single calls.
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?