Generate the X-Signature header by computing SHA-256(ApiKey + SecretKey + Unix timestamp)
POST to /hotel-api/1.0/hotels with a checkIn, checkOut, occupancies array, and geolocation filter
Parse the hotels response to extract hotel code, room code, net rate, cancellationPolicies, and rateKey
POST to /hotel-api/1.0/bookings with the chosen rateKey, holder name, and pax details to create the booking
Store the booking reference and cancellationPolicies deadlines in the reservation record
To cancel, POST to /hotel-api/1.0/bookings/{reference}/cancellation and parse the cancellationAmount
Known gotchas
The X-Signature timestamp must be within 60 seconds of server time; clock skew on the client side causes systematic 403 errors that look like credential failures
rateKey values are session-scoped and expire; the rateKey from an availability search must be used within the session TTL or the booking will fail with a 'rate not available' error
HotelBeds net rates are always exclusive of local city taxes (tourist taxes) that must be collected at the property; displaying net rates as total price is a compliance risk
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp