Skip to main content

Hotel-X API Credentials

Review your API Key, Clients, Accesses and Contexts

Once you have configured your account, you can access our APP and check your Hotel-X credentials and accesses by following this simple guide:

Apikey☑️

An Apikey is a unique alphanumeric code that serves as a form of authentication required for accessing Hotel-X API. This key must be included in the HTTP Authorization request header to verify and authenticate the user agent with the server. It acts as a secure identifier, ensuring that only authorized users can make requests and access the API's functionalities. You can find your Apikey (encrypted) and generate new ones in section Connections > API Settings.

  1. APP access: Log in with your credentials here.

  2. Connections: Click on "Connections" in the top menu. Then, click on "API Settings".

  3. API Settings: List of API Keys associated with your Organization (encrypted). Simply click in the "You can manage your API Keys here" in the yellow callout in order to visualize this information. Please note that API Keys cannot be retrieved; therefore, ensure you keep a record of yours once created.

    info

    Please keep in mind that the Apikey will remain consistent across both test and production environments.

Access☑️

An access refers to the combination of credentials and authentication configuration that allows a Buyer to establish a connection with a Seller. It serves the purpose of distinguishing between different Sellers and filtering different credentials and configurations from the same Seller (e.g., B2B and B2C feeds). You can check this information in My Connections.

For Hotel-X implementation and testing, we recommend using the following accesses (they have already been activated on your account and are ready to use):

  • TravelgateX Test Seller (tgx): Access 2 with context HOTELTEST
  • Smyrooms Test: Access 5647 with context LOGITEST

How can I obtain an access code from an actual Seller? To get your access code, simply establish a commercial agreement with the desired Partner and request activation through our website using the Auto-Activations Form.

info

Please note it is highly advisable to avoid making live bookings during the Hotel-X implementation process until your development has been certified by TravelgateX.

Client☑️

A client refers to a party that buys accommodation services through the Hotel-X API implementation. Client codes remain consistent throughout all TravelgateX implementations and they are used to identify the business that is making the request and to confirm that they have a configuration assigned to it.

It is possible to have multiple client codes, for instance, in order to differentiate traffic between B2B and B2C credentials (e.g., client_b2b, client_b2c). As all accesses are compatible with any of your client codes, it is important to use the appropriate one according to your needs. You can find this information in your API Settings.

Context☑️

Context refers to the content codes utilized by both Buyers and Sellers. Each Seller has its own unique context, which may differ between test and production environments. The context includes specific codes for hotels, boards, rooms, etc. You can check this information in My Connections. Additionally, when you activate a new Seller, you will receive the context information along with the credentials in the confirmation email.

Buyers also have the flexibility to either use their own context or choose content providers. In either case, they can create their own context using our Mapping Plugin. This allows Buyers to align their own context with the Suppliers' context.

What is the difference between access and context?

The distinction between the two is that an access holds your credentials for a specific connection, while a context is the internal TravelgateX code required to request either the original Supplier hotel codes or your own hotel codes (previously mapped and uploaded to our FTP).

Explore our Hotel-X Buyers API Documentation to learn more about Hotel-X credentials and API Settings.