All about Mapping at TravelgateX

TravelgateX behaves as a bridge between Buyers and Sellers, ensuring 100% of transparency in all the transactions.

Keeping to our commitment to transparency, there are no TravelgateX hotel codes (we always return the Seller native codes), so that the mapping between a Buyer and a Seller can be easily optimized by both parties without any interference from TGX: Buyers are in charge of mapping each of their Sellers.


When a Seller returns the same hotel id for different properties, we concatenate those hotel ids with their destination code in order to make them unique. That will be the only exception where we modify the Seller information. In that case, the hotelCode will be the one returned through our API (concatenated if needed) and the hotelCodeSupplier will be the native code of the supplier.

You should always map the "hotelCode" since it will be the one used in Search


Please note that you choose the amount of hotels to be mapped so we recommend you contact the Seller directly in order to confim which hotels to map according to your own business needs, thus avoiding unnecessary requests and reducing your L2B.

Additionally, remember that content Queries return the static information provided by Sellers as a whole, not at a hotel level: you will receive the total amount of rooms, boards, destinations and categories returned for your credentials.

Finally, if you are a Buyer connected to our Hotel-X Buyers API, you can upload your own mapping files to our FTP (credentials should be provided by our Customer Care team) in order to use your own hotel codes in the booking flow - You will find more information on Hotel-X Mapping here.


Can we use Universally Unique Identifier Codes (UUIDs) in our mapping?

Yes! We don't have any limitation on the amount (and type) of characters used to map the Seller's hotelcodes.