The problem
Travel Hub is the new-generation supplier platform: one Python adapter per supplier, each answering the same hub contract. Jumeirah Direct Connect was to be connected to it — and a hotel supplier is only really connected once it has passed the supplier's own certification, not when the code compiles.
The approach
Mapping came before code. The first phase (B1) was a set of mapping documents from the supplier API to the hub contract, step by step — search, rooms, prebook, book, read, cancel — with the error mapping consolidated and the open questions triaged before any adapter code depended on them.
The second phase (B2) was the adapter itself, built on FastAPI and run with uv, pytest, Docker and Helm: search → getrooms → prebook → book → read reservation → cancel. Prebook carries price verification, so the price about to be booked is checked against the supplier again before anything is committed.
Alongside the code: a Postman collection covering the lane, and a LOCAL-DEV guide so the next person can run it without asking.
The result
Jumeirah's UAT certification ran 10 scenarios — 4 availability, 3 single-room and 3 multi-room — and all 10 passed on 21–22 October 2026.
Hold is not implemented, and that is stated plainly rather than left for someone to discover.