Pull reservations from Booking.com Connectivity API and acknowledge delivery
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 and target the PCI-compliant base URL secure-supply-xml.booking.com for all reservation retrieval calls
Send a GET OTA_HotelResNotif request to retrieve pending reservations; Booking.com returns new, modified, and cancelled bookings that have not yet been acknowledged
Parse each OTA_HotelResNotifRQ payload to extract guest details, room type, rate plan, total amount, and booking reference
POST an acknowledgement for each retrieved reservation using the specified acknowledgement endpoint so the booking is removed from the pending queue
Store the Booking.com booking ID alongside your PMS reservation ID for future modification or cancellation lookups
Implement polling on a schedule appropriate to your volume; reservations accumulate if not retrieved and acknowledged promptly
Known gotchas
Reservations are only removed from the delivery queue after explicit acknowledgement; failing to acknowledge causes the same reservations to be returned on every subsequent poll, leading to duplicate records in your PMS
Reservation retrieval must use the secure PCI base URL; using the non-PCI supply-xml.booking.com URL for reservation calls is rejected
Modified and cancelled bookings arrive on the same queue as new bookings; your parser must inspect the reservation status field to distinguish create, modify, and cancel 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?