As part of our design update, the screenshots are currently being revised.

TABLE OF CONTENTS

Introduction

GO Distributors are now equipped with the functionality to automatically populate the hotel list and hotel product data. This advancement eliminates the necessity for distributors to code to Hotel APIs, thereby significantly reducing the onboarding time.


When this feature is employed, the system will operate as follows: 

  • In an ARI pull model, it will simulate the scenario where the distributor has invoked the HotelSetup API with all properties activated.
  • In an ARI push model, it will function as if the distributor has exposed the endpoints for HotelLists and HotelProducts and has successfully retrieved all hotels and products made available by the supplier.



Use of Auto Populate

For New Distributors

During the onboarding process, a Pull/Push customer has the option to refrain from implementing the HotelAPIs. A comprehensive description will be displayed on the screen to ensure that you fully understand this decision. By default, the HotelAPIs will be activated.

Should you decide to enable the auto-populate function during onboarding, this setting will be applied automatically across all connections. It is important to note that this decision is irreversible, as the HotelAPIs are not initially coded.



For Existing Distributors (who have integrated HotelAPIs)

You are permitted to activate the function at the level of individual connections. Once this function is enabled, you will have access to all hotels and hotel products that the supplier has made available for that specific connection.

Impoartant:

-When you elect not to implement HotelAPIs during the onboarding phase (i.e.,accept the automated updating of hotel lists and products), the backend will not establish a job schedule.
-In a Pull model, if the connection is set up as Autopopulate, you shall NOT call the HotelSetup API anymore. If you do, GO will return the following error:
{
    "errorCode": "AccessDenied",
    "errorMessage": "Request denied, in conflict with existing setup."
}