Create and manage rate plans on Booking.com using OTA_HotelRatePlanNotif
domain: developers.booking.com/connectivity · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate using machine account credentials against the Booking.com Connectivity APIs using either token or credential-based scheme
POST an OTA_HotelRatePlanNotif payload to supply-xml.booking.com to create a new rate plan, specifying plan code, description, and cancellation policy linkage
To create a derived (child) rate plan, include a reference to the parent rate plan code and specify the percentage or absolute offset
Rename or update an existing rate plan by sending OTA_HotelRatePlanNotif with the existing rate plan code and updated attributes
Verify the rate plan is visible in the Booking.com extranet and linked to the correct room types before pushing availability or price updates against it
Send OTA_HotelRateAmountNotif messages separately to set the actual nightly rates for the newly created plan
Known gotchas
Derived rate plans inherit pricing from a parent; sending explicit price updates to a derived plan can be rejected or overridden by the parent relationship
Rate plan codes must be unique per property; reusing an existing code in a create request updates the existing plan rather than creating a new one
All XML must use UTF-8 encoding and OTA version 2003B; mismatched version identifiers return schema validation errors
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?