Access, Supplier and Context

On this page you will learn more about Core Entities used in HotelX. You can also refer to the overarching core concepts that apply to all TravelgateX APIs.


Product segmentation over a Supplier API implementation. Each Supplier has a Supplier code. These are unique values and they are used consistently throughout all TravelgateX implementations. See our Supplier database, or ask us via our Jira Service desk for a list of Supplier codes.

Platform (Provider)

Since not all suppliers have their own API, in some cases they will use a third party platform to return availability and allow you to make reservations. This is generally transparent to you as a customer.


Configuration used when interacting with a Supplier, which includes:

  • URLs 

  • Credentials 

  • Markets 

  • Rate Types 

  • Specific Supplier settings 


Client codes are consistent throughout all TravelgateX implementations. These codes are used to identify the business that is making the request and to confirm that the business has a configuration assigned to it.


Context is the way codes are formed and used in implementations. Each Profile (either a Buyer or Supplier) can manage their own contexts or reuse existing ones. Different buyers or sellers can also manage the same codes context. For example, the SupplierSmyRooms uses SMY contexts for their implementations.

Context applies to:

  • Hotel Codes 

  • Board Codes 

  • Room Codes 

With our built-in solution, you are able to choose the context that you wish to use when requesting a HotelX operation. For example, if you are a Buyer, you can map your context to your Suppliers’ contexts.

Should you be using the aggregator mode, we recommend that you use the widest Context possible (the one that includes more portfolio) or that you use your own context - in doing so, all supplier mappings will be solved/unified.