Retrieve hotel property content via Booking.com Content API using OTA_HotelDescriptiveInfo
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 with a machine account token and target the non-PCI base URL supply-xml.booking.com for all content-related calls
Send an OTA_HotelDescriptiveInfoRQ with the hotel ID to retrieve existing content including property name, location, amenities, and photos
Use OTA_HotelDescriptiveContentNotif to push new or updated property-level content such as descriptions, check-in/check-out times, and category
Manage facilities separately via the Facilities API endpoints to add or update specific amenity codes
Use OTA_HotelProductNotif to create or update room types linked to the property
Validate returned content against your own PMS or channel manager data model before syncing downstream
Known gotchas
Photos must be submitted through a separate media upload flow, not through OTA_HotelDescriptiveContentNotif; sending photo URLs in the wrong message type is ignored
Facility codes on Booking.com are proprietary; mapping your internal amenity codes to Booking.com facility IDs requires the Facilities meta endpoint to look up valid values
Creating a property via the property-api endpoint returns a Booking.com hotel ID that must be stored and used for all subsequent ARI and rate messages
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?