Web Services

This section has to be filled up in case we want to sell to the client via XML.

If the customer buys exclusively from the web interface, you can simply leave "0" and proceed with the configurations of the other tabs.

If the customer buys via XML, we need to set Level 2 and can configure the following parameters:

• Kalima XML - Blocked in deadline: It allows you to decide if you want to block the booking when already in deadline and which error message you want to return
• Duration of cache of availability search (in seconds): If set, it overrides the default cache time used for customer availability for city/multi-id or single hotel requests. Low values concern more fresh availability
• Timeout threshold for supplier's response (in seconds) - MULTI ID (to be agreed with the client): allows you to indicate how many seconds the system should respond to the client when searching for more than one id
• Timeout threshold for supplier's response (in seconds) - SINGLE ID (to be agreed with the client): allows you to indicate how many seconds the system should respond to the client when searching for one id
• Use the currencies of the supplier: if selected, the system uses the currency of the supplier instead the currency of the customer (you select if you want to resell to the customer with the same currency from which you buy from the supplier)
• Landing url: (only for the B2C) you can choose a specific url where the client will land to finalize the booking
• Block dynamic currency: if active, it ignores the currency requested via XML
• Forced currency: if selected, it overrides the currency selected by the user for the request (if you want to keep the client's browsing currency unchanged, but change that via XML. The currency is always consistent in the booking flow, if the availability is returned in a currency, the booking will be confirmed with this same currency)
• Change room type if innacurate: if selected and the SYS_INACCURATE_BEDDING_TYPE remark is present in the contract, it replaces the room type. Example: dbl/twn is translated to 2px, sgl/tsu is translated to 1px
• Timeout for the confirmation of bookings (to be agreed with the client): if set, it automatically cancels the reservation if more time passes between creation and confirmation than the seconds set as timeout. If only flagged, consider the default of 60 seconds
• Request limitation (per minute):if set, overwrites the maximum number of xml requests per minute that the client can make. This setting works only on multi-id and per-city requests
• Show provider: if selected, returns a tag with the supplier's name in XML messages
• Show net prices: if selected, returns the net prices (owner net) in the availability and booking/track responses
• Show Channel Manager: if enabled, returns a "channel" attribute in the agreement tag of the availability response, indicating the Channel Manager ID linked to the contract
• Custom hotel inventory: possibility to upload a txt file with a specific set of hotels per customer (the file must be composed of a single column with the hotel IDs). Once the file is uploaded, two icons will appear the first allows you to download the file you just uploaded, the second allows you to download the inventory based on the active suppliers for that client
• Authorized IP addresses: allows you to specify a list of IPs (or classes of IPs) that are allowed to make bookings. All IPs not on the list will be blocked. If “Allow ANY IP address” is selected, filtering will be disabled.
• Shadow Limits: this flag is related to the message shown to clients while looking for availability if they reach the traffic limit.
  • If activated, the message will show a generic "No availability"
  • If not activated, the message will be the error of traffic limit reached.
• Availability Multi: Multi hotel query limit per minute (QPM).
• Availability Single: Single hotel query limit per minute (QPM).
• Evaluate: Evaluate limit query (Prebook) per each single tariff per minute (QPM).