Push and pull rates, availability, and inventory (ARI) between a booking channel and RMS Cloud using the RMS Channel API.
domain: helpcentre.rmscloud.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Map the property's room/rate combinations between the channel and RMS before enabling live ARI sync.
On initial connection, expect RMS to send ARI data for the next two years so the channel has full future availability, not just near-term dates.
After the initial load, consume delta updates for subsequent rate/availability/inventory changes rather than re-pulling the full two-year window each time.
Choose the PUSH direction (RMS to channel) for RMS-managed rates, or the PULL direction (channel to RMS) if the channel needs to write rates back, depending on which side owns pricing.
Monitor for failed ARI updates and re-request the affected date range rather than assuming a delta update always succeeds silently.
Known gotchas
Rate-write calls are rate-limited (reported around 2,500 requests per 15 minutes for patch/put rate operations) — bulk rate changes need batching, not one call per date/room.
The initial sync pushes two years of ARI as a large burst of data; don't assume the same volume applies to every subsequent 'delta only' update.
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?