Introduction

Selling via XML requires careful and strategic configuration to ensure security, efficiency, and optimal management of data flows and bookings. In this chapter, we give some practical tips to better structure XML accounts and optimize operations​, taking into account the specific needs of your customers and the technical peculiarities of the system.

By following these tips, you will be able to ensure smooth and secure management, minimizing risks and improving control over traffic and reservation flows:

• Separation of accounts: in case the Tour Operator customer needs to make reservations both from web and xml, you need to create two separate accounts. This allows separate management of operations, improving security and traceability. For the XML account, it is advisable to disable the ability to make reservations online (Booking online choosing "Availability only")

• Multiple accounts for distinct streams: if a client needs to differentiate XML streams, such as for traffic management, markup or product reasons, additional accounts dedicated to specific functions can be created. Please note: For clients who wish to view all bookings made from their accounts, a network type client can be configured to provide access to an aggregated view of bookings. It is highly recommended to configure a whitelist (see Authorized IP Addresses) for each XML account, limiting API access to only authorized IP addresses.

For each XML client, we also suggest creating two separate users: one for accessing the backoffice via the Web, which is useful for consulting reservations, and one for using the API, this way, if for example the web user needs to change the password he can do so without affecting the operation of the xml.

The following paragraphs detail the steps to configure each tab.