0% found this document useful (0 votes)
426 views241 pages

Deskline Interface

Uploaded by

szilvivas1
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
426 views241 pages

Deskline Interface

Uploaded by

szilvivas1
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 241

Documentation

Deskline 3.0
Standard Interface (DSI)

Version: 3.173.0.0

Changed by: Christoph Ebner

Last change: 21 June 2017


DESKLINE 3.0 STANDARD INTERFACE

INDEX
INTRODUCTION .......................................................................................................................................................5
GETTING STARTED / FUNCTION OVERVIEW ...........................................................................................................6

QUESTIONNAIRE ......................................................................................................................................................7
TECHNICAL DESCRIPTION ........................................................................................................................................8
AUTHENTICATION....................................................................................................................................................8
TEST ENVIRONMENT ...............................................................................................................................................8

KEY VALUES..............................................................................................................................................................9
REQUEST ...............................................................................................................................................................10
RESPONSE .............................................................................................................................................................13
BASIC DATA FOR SERVICE PROVIDERS..................................................................................................................25

STRUCTURE OF A SERVICE PROVIDER WITH SERVICES AND PRODUCTS ................................................................................25


ADDITIONAL SERVICE PROVIDERS AND ADDITIONAL SERVICES ..........................................................................................26
SCHEDULING THE SYNCHRONIZATION ..........................................................................................................................27
REQUEST WORKFLOW..............................................................................................................................................27
REQUEST ...............................................................................................................................................................28
RESPONSE .............................................................................................................................................................34

ON DEMAND DATA FOR SHOWING AVAILABILITY CALENDAR ............................................................................68


REQUEST ...............................................................................................................................................................68
RESPONSE .............................................................................................................................................................69

CHECK FOR CHANGED SERVICE PROVIDERS .........................................................................................................70


REQUEST ...............................................................................................................................................................70
RESPONSE .............................................................................................................................................................72

BASIC DATA FOR EVENTS ......................................................................................................................................73

REQUEST ...............................................................................................................................................................73
RESPONSE .............................................................................................................................................................76

CHECK FOR CHANGED EVENTS ..............................................................................................................................79


REQUEST ...............................................................................................................................................................80
RESPONSE .............................................................................................................................................................81
BASIC DATA FOR INFRASTRUCTURE .....................................................................................................................82
REQUEST ...............................................................................................................................................................82
RESPONSE .............................................................................................................................................................84
CHECK FOR CHANGED INFRASTRUCTURES ...........................................................................................................87
REQUEST ...............................................................................................................................................................88
RESPONSE .............................................................................................................................................................89
BASIC DATA FOR SHOP ITEMS (BROCHURES AND ARTICLES) ..............................................................................90

REQUEST ...............................................................................................................................................................90

Introduction 2 of 241
DESKLINE 3.0 STANDARD INTERFACE

RESPONSE .............................................................................................................................................................91

BASIC DATA FOR DESTINATION PACKAGES ..........................................................................................................94


STRUCTURE OF A DESTINATION PACKAGE.....................................................................................................................94
OVERVIEW .............................................................................................................................................................99
REQUEST ...............................................................................................................................................................99
RESPONSE ...........................................................................................................................................................101

BASIC DATA FOR HOUSE PACKAGE CONTAINER ................................................................................................110


REQUEST .............................................................................................................................................................110
RESPONSE ...........................................................................................................................................................112
BASIC DATA: DELETED ITEMS ..............................................................................................................................115
REQUEST .............................................................................................................................................................115
RESPONSE ...........................................................................................................................................................116
SEARCH FOR AVAILABILITIES...............................................................................................................................117

REQUEST .............................................................................................................................................................117
DEFAULT RESPONSE (REPONSETYPE=”STANDARD”) ....................................................................................................126
RESPONSE (REPONSETYPE=”EXPANDED”) .................................................................................................................129
GET CANCELLATION INFORMATION ...................................................................................................................135
GET PAYMENT INFORMATION ............................................................................................................................137
SEARCH FOR ADDITIONAL SERVICES...................................................................................................................139
REQUEST .............................................................................................................................................................139
RESPONSE ...........................................................................................................................................................141
SEARCH FOR DESTINATION PACKAGES...............................................................................................................144
REQUEST .............................................................................................................................................................144
RESPONSE ...........................................................................................................................................................145
SEARCH FOR DESTINATION PACKAGE DETAILS ..................................................................................................148
REQUEST .............................................................................................................................................................148
RESPONSE ...........................................................................................................................................................149
SEARCH FOR EVENTS ...........................................................................................................................................152
REQUEST .............................................................................................................................................................152
RESPONSE ...........................................................................................................................................................153
GUEST ADDRESS MANIPULATION.......................................................................................................................155
CREATING A NEW GUEST ADDRESS ..........................................................................................................................157
SEARCHING A GUEST ADDRESS ................................................................................................................................157
UPDATING A GUEST ADDRESS .................................................................................................................................158
DELETING A GUEST ADDRESS ..................................................................................................................................159
BOOKING PROCESS ..............................................................................................................................................160
IMPORTANT INFORMATION .....................................................................................................................................160
PAYMENT TYPES AND PAYMENT METHODS ................................................................................................................161
MANDATORY SHOPPING CART PARAMETERS ..............................................................................................................161
CREATING A NEW SHOPPING CART ..........................................................................................................................162
Introduction 3 of 241
DESKLINE 3.0 STANDARD INTERFACE

ADDING ACCOMMODATION ITEMS TO A SHOPPING CART.............................................................................................163


ADDING ADDITIONAL SERVICES TO A SHOPPING CART .................................................................................................164
ADDING BROCHURES TO A SHOPPING CART ...............................................................................................................166
ADDING SHOP ARTICLES TO A SHOPPING CART...........................................................................................................166
ADDING DESTINATION PACKAGES TO A SHOPPING CART ..............................................................................................167
REMOVING SHOPPING CART ITEMS...........................................................................................................................169
CALCULATE OPTIONAL FEES FOR SHOPPING CART ........................................................................................................170
UPDATE SHOPPING CART SETTINGS ..........................................................................................................................171
UPDATE SHOPPING CART PAYMENT METHOD ............................................................................................................172
UPDATE EXTERNAL SHOPPING CART SETTINGS ............................................................................................................173
SET OPTIONAL GUARANTEE.....................................................................................................................................175
READING A SHOPPING CART ...................................................................................................................................176
PRE-PAYMENT INFORMATION ORGANISATION ............................................................................................................184
PRE-PAYMENT INFORMATION SERVICE PROVIDER .......................................................................................................185
COMMITTING A TRANSACTION ................................................................................................................................189
CREDIT CARD GUARANTEE OR PAYMENT WITH DATATRANS ..........................................................................................194
CHECK STATUS OF SHOPPING CART...........................................................................................................................205
READING A BOOKING .............................................................................................................................................206
READING A TRANSACTION/BOOKING LIST ..................................................................................................................207
CANCELING A BOOKING ..........................................................................................................................................211
GET SETTLER INFORMATION ....................................................................................................................................212

SAVING REQUESTS...............................................................................................................................................216

DIFFERENT USAGE CASES ....................................................................................................................................223


TYPE LIST ..............................................................................................................................................................224

XSD FILES, TARGET URL/WSDL ............................................................................................................................226


GLOSSARY ............................................................................................................................................................227
CHANGE LOG........................................................................................................................................................228

Introduction 4 of 241
DESKLINE 3.0 STANDARD INTERFACE

INTRODUCTION
The Deskline 3.0 Standard Interface (DSI) is the Web Service to interact with Deskline 3.0 without a GUI. This
documentation should help developers to connect to Deskline 3.0 and provide examples on how to send and
receive data.

As the DSI progresses we will add new functionality with updates. Right now the following calls are possible:

 Get basic data for Service Providers


 Get basic data for Shop Items (brochures)
 Get basic data for Events
 Get basic data for Infrastructure
 Get basic data for Destination Packages
 Search for availabilities, events, destination packages
 Get the key values that are mandatory for a dynamic mapping of facilities, categories, …
 Guest Address Manipulation
 Booking
 Saving Requests

The following functions are planned:

 extending all functions and adding features as Deskline 3.0 development continues

This document will also be changed every time the DSI is changed or added.

Before you get started please refer to the chapter “Questionnaire” so we are able to support you better.

If you have any questions regarding the Deskline 3.0 Standard Interface please contact:

Interface Team
[email protected]

feratel media technologies AG


Businesscenter Altes Parkhotel Villach
Moritschstraße 2/IV
A-9500 Villach
FN 72841w, LG Innsbruck
Internet: www.feratel.com

For questions related to responses that you get from the interface please don’t forget to include the request-
XML in your mail!

Introduction 5 of 241
DESKLINE 3.0 STANDARD INTERFACE

GETTING STARTED / FUNCTION OVERVIEW


The DSI offers a variety of features to use and depending on the project that must be realized all or only parts
of the information are needed. In any case the following functions are available:

Function Description
Key Values Categories, Towns, … IDs and translations of certain items. In the Basic
Data only IDs of these items are returned so this can be used as a
mapping table.

Key Values are a global set of values, the same for all customers, but
there is also a way to read local values for some items if the project is
connected to only one local database.

KeyValues change rarely, synchronization once a week should be


enough. These data must be cached and are not supposed for use on
demand.
Basic Data Data of Service Providers (Accommodation, Additional services) like
details, addresses, descriptions, documents, rooms, products and so
on.
Basic Data Data of Shop Items (Brochures)
Basic Data Data of Events
Basic Data Data of Infrastructure Items (Restaurants, Rental services, …)
Search The search for availabilities returns a list of service providers and
product IDs.
Search Packages The search for package returns a list of destination packages and the
package detail search all available details to one package
Booking Creating a booking using the shopping cart functions.
Save Requests Saving an offer request or a request to the request pool.
Guest Address Management Adding and updating a guest address.

Each one of these functions must be activated by feratel before they can be used, so it is possible that one
project only allows requesting data but not searching for availabilities.

To start, the following information will be provided by feratel:

 Company code for authorization


 Point Of Sale code (Originator) for the project
 Sales Channel GUID(s) necessary for the prices/search
 Top location (Range Code and GUID)

With these values it is then already possible to create a request for Key Values to get the items that are
necessary for the project. These could be for example regions/towns/districts, categories, facilities and so on.

The top location is the highest geographical unit and can be used to get a list of towns and the IDs that can be
used in requests for basic data or for performing a search for one or more towns.

Before you get started, please provide us with the answers to the questions from the chapter “Questionnaire”
as every project is different. Therefore we need to know what you need and how you intend to use the data.

Getting Started / Function Overview 6 of 241


DESKLINE 3.0 STANDARD INTERFACE

Q UESTIONNAIRE
Before you get started with actual calls to our interface, please provide us with the answers to the questions
below. Every project is different and we need to know this information in order to support and advice you
when it comes to using the interface.

 Where are you going to use/display the data gathered?


o Is it one website? More than one website? Is it not displayed online?
 Are you requesting data only for one town or for multiple towns? For a region? For a whole country?
What is the scope of the project?
 What is the data that you need to get from us?
o Service Providers?
 To which level? Only details? Descriptions? Documents? Also the services and
products? The whole price details? Availabilities?
o Additional Service Providers?
 Again: to which level?
o Events?
 Again: to which level?
o Infrastructure?
 Again: to which level?
o Destination Packages?
 Again: to which level?
 Which functions do you intend to use?
o Gathering the basic data?
o Performing a search…
 ... against the interface directly?
 Search only for a previously selected hotel?
 General search for towns/regions?
 … with data cached in your system?
o Making a booking…
 … by using the interface?
 … by using the web link?
o Saving requests
 How often do you intend to request data and recently changed data for every item that you request?
o Different schedules for different items? (E.g. addresses less often than prices?)

Questionnaire 7 of 241
DESKLINE 3.0 STANDARD INTERFACE

TECHNICAL DESCRIPTION
XML files are the base for DSI data exchange – all mandatory and optional values for requests are passed inside
XML files and also the response will be a valid XML file.

The target address to pass the xmlString to is different for each Web Service, see chapter XSD & WSDL.
HttpSoap and HttpPost are allowed.

Please note that the examples provided in this documentation are not always guaranteed to be complete as
the documentation and XML Schema keep on growing, but the binding XML Schema is always the latest
version. Elements inside the XML Tree need to be used in the correct order. Element-Names and Attribute-
Names are case-sensitive.

Important: as the interface progresses with new functions and values, we will add new elements and attributes
in the XML structure along the way. We assume that this will not break existing solutions from external
providers when we ship updates on the interface to the live system.

AUTHENTICATION
Technically, the authentication is done based on a company authorization code assigned by feratel and IP-
checks, so the IP-address(es) of the server(s) that want(s) to access the Web Services must be known
beforehand. After that, the request is validated against the XSD schema.

Key Values, Basic Data, Searching, Booking: On the software level, the same checks are used that come into
action when a Point of Sale (POS) is requesting data inside the application. The Deskline 3.0 supervisors can
create a POS and the data owners can then define the access rights and sales rules to their data for every POS.

The POS is a string that must be provided in every request.

To receive price information or to perform a search or create a booking, also the SalesChannel (GUID provided
by feratel) must be known.

TEST ENVIRONMENT
A complete test environment is available and can be set up on demand. The target-URLs will then change from
interface.deskline.net/… to interfacetest.deskline.net/…

Technical Description 8 of 241


DESKLINE 3.0 STANDARD INTERFACE

KEY VALUES
The call for key values sends a list of all the values that are used for a successful mapping of Deskline 3.0 data:

 Countries
 Regions
 Towns
 Districts
 HotSpotTypes
 Categories
 Service Provider Classification information
 Service Classification information
 Chains
 Marketing groups
 Facility groups
 Facilities
 Languages
 Rating Questions
 Rating Visitors
 Salutations for guest addresses
 Guest Countries
 Shop Item Groups
 Infrastructure Types
 Infrastructure Topics
 Serial Events
 BankCodes
 CustomAttributes
 HotSpots
 Fallback Languages
 Link Types
 HandicapGroups
 HandicapTypes
 HandicapFacilityGroups
 HandicapFacilities
 HandicapClassifications
 VisitorTax

Translations are provided along with the key values, therefore the list of required languages must be provided
inside the request.

Not all projects will need to have all types of Key Values, therefore you have to define all the elements that
should be part of the response in the request with Show=True. If you only request hotels then you don’t need
the key values for events or infrastructure items. If you don’t do the booking you don’t need the Guest
Countries or Salutations and so on.

These Key Values are usually not changed very often as they are mostly global values so we recommend
synchronizing them only on demand.

Key Values 9 of 241


DESKLINE 3.0 STANDARD INTERFACE

REQUEST
More than one
Request field Description Can be empty?*
possible?

Originator The code of the point of sale requesting the data.


Provided by feratel.
Company The code of the company requesting the data. Provided
by feratel.
Range and GUIDs First, a range code to select the data must be defined.
IDs This is an enumeration if it is a region (RG) or a town (TO)
or a district (DI) for example. It is also possible to select a
data owner instead of a geographical selection. The ID of
regions/towns/districts are part of the KeyValues
function. If there is a need to call data owners (DO)
directly, the IDs are provided by feratel. The top location
(i.e. highest/widest range possible) will be provided by
feratel to get started (see range example in
KeyValues.xml)
Important: use only one ID in KeyValue function, if you
use more only the first one will influence the response.
KeyValues Important information: by default the Key Values will be
a global master and all additional entries that customers
can create on their local database will not be available.

However, in some projects – and only when there is only


one local database connected – the Attribute
GetLocalValues can be set to true if needed. In this case,
the values will be taken from the local database instead
of the global master. For projects that gather the data
from more than one customer/database, this flag should
not be used.

This is for example necessary for data that is only


available on the local database, like Rating Questions or
Rating Visitor Types.

It is also possible to request only those KeyValues


changed within a specific time range by providing a
DateFrom.

Summary: Possible Attributes

 GetLocalValue: true or false (default)


 DateFrom: Date Format YYYY-MM-DD

Translations It’s possible to receive all the required translations within


the same request by providing the language codes
necessary.

Example:

<Translations>
<Language Value="de" />
<Language Value="en" />
</Translations>

Key Values 10 of 241


DESKLINE 3.0 STANDARD INTERFACE

Countries, Regions, These elements can be activated in the response by


Towns, Districts, setting the value Show=true.
HotSpotTypes, It is also possible to request only one specific Item with
Categories, Stars, providing the Id. (not possible for call of KeyValues
Classifications, “Languages” and “InfrastructureTypes” because they do
HotelChains, not have an Id)
MarketingGroups,
ServiceClassifications,
HolidayThemes,
Languages,
ServiceCodes,
Salutations,
GuestCountries,
InfrastructureTypes,
HotSpotTypes,
FallbackLanguages,
LinkTypes,
HandicapGroups,
HandicapTypes,
HandicapFacilityGroups,
HandicapFacilities
HandicapClassifications

Countries, Regions, In generall location names are provided in their native


Towns, Districts, language. If needed in other languages available, add
optional attribute IncludeTranslations="true" to request,
then response includes also translations in this structure:

<Location Id="3dd67e34-1724-48fd-81dc-4c79f682ae6d"
ParentID="00000000-0000-0000-0000-000000000000"
Name="Österreich" ChangeDate="2009-06-24T17:29:00">
<Names>
<Translation Language="de">Österreich</Translation>
<Translation Language="en">Austria</Translation>
<Translation Language="fr">Autriche</Translation>
<Translation Language="uk">Австрія</Translation>
</Names>
</Location>

FacilityGroups, Facilities These elements can be activated in the response by


setting the value Show=true. With the attribute Types
(enumeration) the types of facility groups or facilities that
should be returned can be defined. If Types is not
provided, then all possible groups/facilities are returned.
Types has the following possible values:
ServicesAccommodation,
ServiceProviderAccommodation,
ServicesAdditionalService, Event

Example: <FacilityGroups Show="true"


Types="ServicesAccommodation
ServiceProviderAccommodation
ServicesAdditionalService Event" />
RatingQuestions, This will only be part of the response if the KeyValues
RatingVisitors, Attribute GetLocalValues is set to true.
ShopItemGroups,

Key Values 11 of 241


DESKLINE 3.0 STANDARD INTERFACE

InfrastructureTopics,
SerialEvents,
CustomAttributes,
HotSpots,
LinkTypes,
BankCodes, VisitorTax
Categories, For these it is possible to call the local values only. E.g.
Stars, when you have access to several customers you can call
Classifications, global values once and then only the local ones for each
HotelChains, customer separately.
MarketingGroups,
ServiceClassifications, <Categories Show="true" LocalOnly="true"/>
HolidayThemes,
FacilityGroups,
Facilities

Get a list of all key values in English and German. Note: not all elements have to be provided.
<?xml version="1.0" encoding="utf-8"?>
<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://interface.deskline.net/DSI/XSD">
<Request Originator="FERATEL" Company="FERATEL">
<Range Code="RG">
<Item Id="F180FFD5-4FBF-4F2C-AC00-7E8B94462F2C" />
</Range>
<KeyValues GetLocalValues="true" DateFrom="2000-01-01">
<Translations>
<Language Value="de" />
<Language Value="en" />
</Translations>
<Countries Show="true" IncludeTranslations="true"/>
<Regions Show="true" IncludeTranslations="true"/>
<Towns Show="true" IncludeTranslations="true"/>
<Districts Show="true" IncludeTranslations="true"/>
<HotSpotTypes Show="true" />
<HotSpots Show="true" />
<Categories Show="true" LocalOnly="true" />
<Stars Show="true" />
<Classifications Show="true" Id="b5b6abcf-fc38-4512-8732-e2210ba7bf88"/>
<!--If only one specific KeyValue is needed provide Id-->
<HotelChains Show="true" />
<MarketingGroups Show="true" />
<ServiceClassifications Show="true" />
<HolidayThemes Show="true" />
<FacilityGroups Show="true" />
<Facilities Show="true" />
<Languages Show="true" />
<RatingQuestions Show="true" />
<RatingVisitors Show="true" />
<Salutations Show="true" />
<GuestCountries Show="true" />
<ShopItemGroups Show="true" />
<InfrastructureTypes Show="true" />
<InfrastructureTopics Show="true" />
<SerialEvents Show="true" />
<BankCodes Show="false" />
<!--because of the huge amount requesting bank codes slows down the response time a lot, set true
only if needed-->
<CustomAttributes Show="true" />

Key Values 12 of 241


DESKLINE 3.0 STANDARD INTERFACE

<FallbackLanguages Show="true" />


<LinkTypes Show="true" />
<HandicapGroups Show="true" />
<HandicapTypes Show="true" />
<HandicapFacilityGroups Show="true"/>
<HandicapFacilities Show="true"/>
<HandicapClassifications Show="true"/>
<VisitorTax Show="true"/>
</KeyValues>
</Request>
</FeratelDsiRQ>

RESPONSE
More than one
Response field Description Can be empty?*
possible?

Countries A list of countries in the range available to the Point Of


Sale. Countries will only be of use for companies that
request data for more than one country, otherwise it will
be an empty result.
Regions A list of regions in the range available to the Point Of Sale.
Regions can have parents (e.g. a sub region is part of a
region), therefore the element “Parent” is used. Region-
names are not translated. Regions can be used in the
requests with the range code RG and the ID(s) of the
region.
Towns A list of towns in the range available to the Point Of Sale.
Towns are part of a region, therefore the element
“Parent” is used. Town-names are not translated. Towns
can be used in the requests with the range code TO and
the ID(s) of the town(s).
Districts A list of Districts in the range available to the Point Of
Sale. Districts are part of a town, therefore the element
“Parent” is used. District-names are not translated.
Districts can be used in the requests with the range code
DI and the ID(s) of the district(s).
HotSpotTypes HotSpotTypes are for example “Airport”, “Ski lift”, “Spa”
and so on. The actual hotspots, for example “Salzburg
Airport” are created per database and returned with the
element HotSpots documented further below.
HotSpots A hotspot can be for example “Salzburg Airport” and is
created on a local database. Therefore the request has to
include GetLocalValues=true. Inside the basic data the
HotSpots can be requested as well – if data is present
there will be an entry for each HotSpot and the distance
from the service provider to the HotSpot.

The attribute TypeId shows the relation to the HotSpot


Type it is related to.

Hotspots also have the element Position with the


Attributes Latitude and Longitude.
Categories A service provider can have one or more than one
categories, like hotel, inn, and so on. Categories have
translations and a sort order.

Key Values 13 of 241


DESKLINE 3.0 STANDARD INTERFACE

ServiceClassifications In some cases, services can have their own classification.


These items have a translation and a sort order as well.
Classifications Classification information except stars, like flowers, suns,
and so on. Classifications have translations, sort order and
a URL.
HotelChains Hotel Chains, like Best Western. Chains can have
translations, but are usually not translated. Sort order and
URL are also provided, but order can be dismissed for
chains.
Stars Stars can be applied to any service provider along with the
category and consist of translations, sort order and URL.
MarketingGroups Marketing Groups can have translations, but are usually
not translated. Sort order and URL are also provided, but
order can be dismissed for them as well.
FacilityGroups Facilities are generally assigned to one facility group.
There are facilities for service providers of type
accommodation, SP additional service, services and
additional services. These groups have translations.
Facilities Facilities can be assigned to service providers of type
accommodation, SP additional service, services, additional
services and events. They have translations and
information if it is possible for customers to assign values
as well. E.g. “Meeting Rooms” can have a value of “3”
while “Golf lessons” is only yes/no.
Languages Languages have a language code and the names are
translated as well.
RatingQuestions Questions for the rating module can be different by type
(Hotel/Apartment/Camping) and also have an order and
translations. Only part of the response if created on the
customer database and only if GetLocalValues is set to
true, otherwise the result will be empty.
RatingVisitors Visitor types for ratings have translations and an order.
Only part of the response if created on the customer
database and only if GetLocalValues is set to true,
otherwise the result will be empty.
ServiceCodes Service Codes define the basic structure of a service - e.g.
single room, double room, suite - and sanitary or
additional information. There are 2 types: ServiceType
(Accommodation, Additional Services) and CodeType
(Room type/Service type, Sanitary, AdditionalInfo)
Salutations Providing a salutation is mandatory information to be
passed when creating a guest address. Salutations consist
of translations, gender-information, order and default
values.
GuestCountries List of country codes with translations and dial code.
Providing a country code is mandatory when creating a
guest address.
ShopItemGroups Groups for shop items (brochures, articles) can be defined
on the local database. Only part of the response if
GetLocalValues is set to true, otherwise the result will be
empty.
InfrastructureTypes Infrastructure Types are the main types infrastructure
items are divided into. At the moment these are “Food &
Beverage”, “Routes & Tours”, “Sport & Leisure”,
“Wellness & Health” and so on. Could be expanded later
on.
Key Values 14 of 241
DESKLINE 3.0 STANDARD INTERFACE

InfrastructureTopics Topics are more specific filters for infrastructure items and
are divided in two columns. For example for “Food &
Beverage” there are items like “Bar”, “Restaurant”, “Fast
Food” in one column (SubType=”1”) and items like
“Italian”, “Mexican” in the other column (SubType=”2”).
Only part of the response if GetLocalValues is set to true,
otherwise the result will be empty.
Serial Events Events can be assigned to a series of events. The items for
serial events can have a translation but also descriptions
and documents inside, just like the descriptions and
documents for service providers for example. Only part of
the response if GetLocalValues is set to true, otherwise
the result will be empty.
BankCodes A list of banks that can be assigned to service providers.
Only necessary if the bank account information is required
when using the booking interface (usually these details
are already printed in the booking confirmation to the
guest).

Warning, this can be a long list of several thousand


BankCodes and therefore it can slow down the response
time a lot!

Attributes per bank: of Name, Code, BIC, CountryCode,


Street, ZipCode and City.
CustomAttributes A list of CustomAttributes created by the destination.
CustomAttributes must only be used if the
customer/destination specifies the demand!

Attributes:
 ID
 Name (right now it’s only the name, there are no
translations)
 ChangeDate (when it was last changed)
 Value (default value)
 Length (if there is a maximum length, it’s possible
that Length is missing when there is no maximum
length!)
 Type (Enumeration, right now only
ServiceProvider)
 DataType (Number, ComboBox, Date, String)

For DataType=ComboBox the available options will be part


of the value, separated by semicolon.
FallbackLanguages Additionally to the already provided languages, customers
have the possibility to choose which languages are active,
which order they have and if a translation is missing
(especially for description of any kind) they also define a
fallback language. E.g. a service provider has not entered
any Italian description and the fallback language of Italian
is set to English, you should show the English description
instead.
LinkTypes Links can have different types, like object link, video or
map. Requesting link types on KeyValues will show the list
of the link types in use by the customer.
HandicapGroups Handicaps are summarized in several groups e.g. wheel
Key Values 15 of 241
DESKLINE 3.0 STANDARD INTERFACE

chair or blindness.
HandicapTypes Handicap facilities can be of different types. Types are e.g.
service provider, services or events
HandicapFacilityGroups Handicap facilities are grouped. Handicap facility groups
are for example parking, lift/elevator…
HandicapFacilities List of all handicap facilities plus the information to which
groups and types they belong and also to which handicap
facility group.
HandicapClassifications Handicap classification information having translations,
sort order and a URL.
VisitorTax To get costs for visitor tax for each tax region including
code and code is then assigned to each service provider.

Example:

<?xml version="1.0" encoding="UTF-8"?>


<FeratelDsiRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
Status="0" Message="OK" xmlns="http://interface.deskline.net/DSI/XSD">
<Result Index="1">
<KeyValues>
<Countries />
<Regions>
<Location Id="f180ffd5-4fbf-4f2c-ac00-7e8b94462f2c" ParentID="00000000-0000-0000-0000-000000000000"
Name="Tirol" ChangeDate="2009-06-24T17:29:00" />
<Location Id="d5eeed9c-1cde-4294-a081-0f3432961e0b" ParentID="f180ffd5-4fbf-4f2c-ac00-7e8b94462f2c"
Name="Kaiserwinkl" ChangeDate="2009-06-24T17:29:00" />
<Location Id="188c3ce1-f120-4f75-bfbb-16feff8a4e78" ParentID="f180ffd5-4fbf-4f2c-ac00-7e8b94462f2c"
Name="Kitzbüheler Alpen - Brixental" ChangeDate="2009-06-24T17:29:00" />
</Regions>
<Towns>
<Location Id="68632227-8732-4735-a4ec-73de8724753c" ParentID="d5eeed9c-1cde-4294-a081-0f3432961e0b"
Name="Kössen" ChangeDate="2009-06-24T17:29:00" />
<Location Id="200ebaab-b356-4c9e-a8f7-ca602fdfb925" ParentID="d5eeed9c-1cde-4294-a081-0f3432961e0b"
Name="Schwendt" ChangeDate="2009-06-24T17:29:00" />
<Location Id="6063a46a-ced8-42fc-9638-f0a1dc41cf6f" ParentID="d5eeed9c-1cde-4294-a081-0f3432961e0b"
Name="Rettenschöss" ChangeDate="2009-06-24T17:29:00" />
<Location Id="ac28ea78-f836-4974-a19d-fd7cc78e2c4f" ParentID="d5eeed9c-1cde-4294-a081-0f3432961e0b"
Name="Walchsee" ChangeDate="2009-06-24T17:29:00" />
</Towns>
<Districts>
<Location Id="b369dda0-1742-4b19-ae79-12bff2b8c8a1" ParentID="68632227-8732-4735-a4ec-73de8724753c"
Name="Kalkau" ChangeDate="2009-06-24T17:29:00" />
<Location Id="31152c8b-f414-439f-8583-22d895ba6a81" ParentID="68632227-8732-4735-a4ec-73de8724753c"
Name="Thurnbichl" ChangeDate="2009-06-24T17:29:00" />
<Location Id="a80a639d-61ea-485a-9fd5-2faec68b768f" ParentID="68632227-8732-4735-a4ec-73de8724753c"
Name="Ried" ChangeDate="2009-06-24T17:29:00" />
<Location Id="ed313e2f-991c-406a-bf36-5f77e2bf60cd" ParentID="68632227-8732-4735-a4ec-73de8724753c"
Name="Mühlberg" ChangeDate="2009-06-24T17:29:00" />
</Districts>
<HotSpotTypes>
<HotSpotType Id="3714d443-6674-4342-8cb3-0c56a5bf6d56" Order="1" ChangeDate="2008-07-15T10:31:00">
<Name>
<Translation Language="de">Flughafen</Translation>
<Translation Language="en">Airport</Translation>
</Name>
</HotSpotType>
<HotSpotType Id="a69badda-c4b5-4a61-9861-4411ee893bbd" Order="2" ChangeDate="2008-07-15T10:32:00">
<Name>
<Translation Language="de">Bahnhof</Translation>
<Translation Language="en">Railway station</Translation>
</Name>
</HotSpotType>
</HotSpotTypes>
<HotSpots>

Key Values 16 of 241


DESKLINE 3.0 STANDARD INTERFACE

<HotSpot Id="dbc63576-8ab8-4d1b-bf48-2ac0eadf1ee1" Order="4" ChangeDate="2009-02-11T14:19:00"


TypeId="6bf64d9b-7edc-4b22-9219-9cc5d852d134">
<Name>
<Translation Language="de">Salzburger Congress</Translation>
<Translation Language="en">Salzburger Congress</Translation>
</Name>
<Position Latitude="47.8075343484343" Longitude="13.0423593521118" />
</HotSpot>
<HotSpot Id="6f54bba7-3b6b-43dd-b309-3ff6b40ff9e2" Order="6" ChangeDate="2009-02-11T14:28:00"
TypeId="edf9c842-cb10-4a2b-85ca-96e85f82b083">
<Name>
<Translation Language="de">Großes Festspielhaus</Translation>
<Translation Language="en">Großes Festspielhaus</Translation>
</Name>
<Position Latitude="47.798735400968" Longitude="13.0411684513092" />
</HotSpot>
</HotSpots>
<Categories>
<Category Id="ab4f2086-f06d-4dac-8b99-09eda5577c67" Order="1" ChangeDate="2008-06-27T15:53:00" Active="true"
URL="http://www.hotel.com" Global="true">
<Name>
<Translation Language="de">Hotel</Translation>
<Translation Language="en">hotel</Translation>
</Name>
</Category>
<Category Id="361bf303-3009-4bc6-8b7e-06c7de10edfc" Order="2" ChangeDate="2008-09-10T11:22:00" Active="true"
URL="" Global="true">
<Name>
<Translation Language="de">Gasthof</Translation>
<Translation Language="en">inn</Translation>
</Name>
</Category>
<Category Id="9e802064-0a21-4cbe-b5cc-2e442e32cc7c" Order="3" ChangeDate="2008-06-27T16:54:00" Active="true"
URL="" Global="true">
<Name>
<Translation Language="de">Campingplatz</Translation>
<Translation Language="en">camping</Translation>
</Name>
</Category>
</Categories>
<Stars>
<Star Id="ebf4ee39-f7e0-45fe-a410-46d75c3b769c" Order="2" ChangeDate="2009-08-06T19:03:00" Active="true" URL=""
Global="true">
<Name>
<Translation Language="de">5 Sterne</Translation>
<Translation Language="en">5 star</Translation>
</Name>
</Star>
<Star Id="effaf367-fa5f-4048-bb06-70b402f805e8" Order="3" ChangeDate="2008-06-27T16:43:00" Active="false" URL=""
Global="true">
<Name>
<Translation Language="de">4 Sterne Superior</Translation>
<Translation Language="en">4 star superior</Translation>
</Name>
</Star>
</Stars>
<Classifications>
<Classification Id="dcba917e-e17a-49c5-b2f8-bcc4422f87e7" Order="1" ChangeDate="2008-06-27T16:25:00"
Active="true" URL="" Global="true">
<Name>
<Translation Language="de">5 Edelweiß (Privatvermieter)</Translation>
<Translation Language="en">5 edelweiss (private landlords)</Translation>
</Name>
</Classification>
<Classification Id="3bac3e97-3432-4b89-88bd-685d5827ecec" Order="2" ChangeDate="2008-06-27T16:25:00"
Active="true" URL="" Global="true">
<Name>
<Translation Language="de">4 Edelweiß (Privatvermieter)</Translation>
<Translation Language="en">4 edelweiss (priv. landlords)</Translation>

Key Values 17 of 241


DESKLINE 3.0 STANDARD INTERFACE

</Name>
</Classification>
</Classifications>
<HotelChains>
<HotelChain Id="75b494a1-059f-4f7d-a9c1-8dd2b5c35bc3" Order="1" ChangeDate="2008-06-27T16:13:00" Active="true"
URL="http://www.holiday-inn.com" Global="true">
<Name>
<Translation Language="de">Holiday Inn</Translation>
<Translation Language="en">Holiday Inn</Translation>
</Name>
</HotelChain>
<HotelChain Id="c5572a2a-4c87-4ffa-b314-ba2a850ad771" Order="2" ChangeDate="2008-06-27T16:52:00" Active="true"
URL="http://www.bestwestern.com" Global="true">
<Name>
<Translation Language="de">Best Western</Translation>
<Translation Language="en">Best Western</Translation>
</Name>
</HotelChain>
</HotelChains>
<MarketingGroups>
<MarketingGroup Id="62ff0285-7f12-45c6-91df-ffa3a204429c" Order="2" ChangeDate="2010-07-01T10:18:00"
Active="true" URL="" Global="false">
<Name>
<Translation Language="de">Bett &amp; Bike</Translation>
<Translation Language="en">Bett &amp; Bike</Translation>
</Name>
</MarketingGroup>
<MarketingGroup Id="78cbf6ce-5be7-4b86-b65f-4d578f83b7e8" Order="3" ChangeDate="2008-07-15T12:58:00"
Active="true" URL="http://www.kinderhotels.com" Global="true">
<Name>
<Translation Language="de">KinderHotels</Translation>
<Translation Language="en">KinderHotels</Translation>
</Name>
</MarketingGroup>
</MarketingGroups>
<ServiceClassifications>
<Classification Id="20d52365-9611-454b-b1e6-ede6c3bc23e2" Order="1" ChangeDate="2011-05-30T17:06:00"
Active="true" URL="" Global="true">
<Name>
<Translation Language="de">1 Stern DTV</Translation>
<Translation Language="en">1 Stern DTV</Translation>
</Name>
</Classification>
<Classification Id="522b9638-4f19-44a2-a08e-76c9d661f8e9" Order="2" ChangeDate="2011-05-30T17:14:00"
Active="true" URL="" Global="true">
<Name>
<Translation Language="de">2 Sterne DTV</Translation>
<Translation Language="en">2 Sterne DTV</Translation>
</Name>
</Classification>
</ServiceClassifications>
<HolidayThemes>
<HolidayTheme Id="25f0588a-a040-48c4-a555-fa18d17a134e" Order="1" ChangeDate="2008-07-24T13:02:00"
Active="true" URL="" Global="true">
<Name>
<Translation Language="de">Weekend</Translation>
<Translation Language="en">Weekend</Translation>
</Name>
</HolidayTheme>
<HolidayTheme Id="dc26d00a-1b99-4c7c-a09a-afc16578c144" Order="2" ChangeDate="2008-07-24T13:02:00"
Active="true" URL="" Global="true">
<Name>
<Translation Language="de">Hochzeit</Translation>
<Translation Language="en">Wedding</Translation>
</Name>
</HolidayTheme>
</HolidayThemes>
<FacilityGroups>
<FacilityGroup Id="ccb7a9ba-e7f0-475e-bdda-076dc695b008" Type="ServiceProviderAccommodation" Active="true"

Key Values 18 of 241


DESKLINE 3.0 STANDARD INTERFACE

ChangeDate="2009-08-20T11:58:00" Global="true">
<Name>
<Translation Language="de">Einrichtungen Bauernhof</Translation>
<Translation Language="en">Farm facilities</Translation>
</Name>
</FacilityGroup>
<FacilityGroup Id="abe5607f-67f1-4739-bacd-19f48030ca12" Type="ServiceProviderAccommodation" Active="true"
ChangeDate="2009-08-31T12:24:00" Global="true">
<Name>
<Translation Language="de">Betten &amp; Zimmer</Translation>
<Translation Language="en">Beds &amp; rooms</Translation>
</Name>
</FacilityGroup>
</FacilityGroups>
<Facilities>
<Facility Id="f0e0d15f-7262-46f7-a7b3-eaecac514a49" Type="ServiceProviderAccommodation" Active="true"
ChangeDate="2009-08-20T12:12:00" Global="true" GroupID="ccb7a9ba-e7f0-475e-bdda-076dc695b008" ValueType="YesNo">
<Name>
<Translation Language="de">Wein &amp; Spirituosen</Translation>
<Translation Language="en">wine &amp; spirits</Translation>
</Name>
</Facility>
<Facility Id="9c71102e-7194-457a-9155-0b157c588e5b" Type="Event" Active="true" ChangeDate="2010-10-29T14:22:00"
Global="true" GroupID="2e5ea2d9-8d13-47d3-9fb8-16be04c4cb3d" ValueType="YesNo">
<Name>
<Translation Language="de">Silvester / Neujahr</Translation>
<Translation Language="en">Silvester / Neujahr</Translation>
</Name>
</Facility>
<Facility Id="9982bf66-1a36-4cc2-9d12-6d98ed7cc74c" Type="ServicesAccommodation" Active="true"
ChangeDate="2008-09-09T00:00:00" Global="true" GroupID="f91557d6-9d4d-476e-9f82-1bf29ded73ea" ValueType="YesNo">
<Name>
<Translation Language="de">Sonniger Stellplatz</Translation>
<Translation Language="en">sunny camping site</Translation>
</Name>
</Facility>
<Facility Id="26141395-01a4-4810-ba65-252b0cdab10b" Type="ServicesAdditionalService" Active="true"
ChangeDate="2010-03-26T11:22:00" Global="true" GroupID="153a6b6f-edbc-457d-a2f6-1db04086afd0" ValueType="YesNo">
<Name>
<Translation Language="de">Familienangebot</Translation>
<Translation Language="en">Familienangebot</Translation>
</Name>
</Facility>
</Facilities>
<Languages>
<Language Code="bg" ChangeDate="2008-09-09T15:10:00" Active="true">
<Name>
<Translation Language="de">Bulgarisch</Translation>
<Translation Language="en">Bulgarian</Translation>
</Name>
</Language>
<Language Code="hu" ChangeDate="2008-09-09T15:10:00" Active="true">
<Name>
<Translation Language="de">Ungarisch</Translation>
<Translation Language="en">Hungarian</Translation>
</Name>
</Language>
</Languages>
<RatingQuestions>
<RatingQuestion Id="8218f75b-4ed1-482f-aa44-0b6b37ef389c" Active="true" Type="Hotel" Order="2">
<Name>
<Translation Language="de">Wie zufrieden sind Sie mir der Sauberkeit des Zimmers?</Translation>
<Translation Language="en">How clean was the room?</Translation>
</Name>
</RatingQuestion>
<RatingQuestion Id="b289b48f-e56b-432a-93dc-3aab02a20a9b" Active="true" Type="Camping" Order="1">
<Name>
<Translation Language="de">War der Platz trocken?</Translation>
<Translation Language="en">How dry was the campsite?</Translation>

Key Values 19 of 241


DESKLINE 3.0 STANDARD INTERFACE

</Name>
</RatingQuestion>
</RatingQuestions>
<RatingVisitors>
<RatingVisitor Id="3a34e5bb-66cd-4cfd-b269-3965b8ff5b69" Active="true" Order="3">
<Name>
<Translation Language="de">Familie mit Kleinkindern</Translation>
<Translation Language="en">Family</Translation>
</Name>
</RatingVisitor>
<RatingVisitor Id="4678a819-71ca-4ea8-b1b5-3ff078396b58" Active="true" Order="1">
<Name>
<Translation Language="de">Single</Translation>
<Translation Language="en">Single</Translation>
</Name>
</RatingVisitor>
<RatingVisitor Id="dd38b518-94b7-44a6-a145-cc045e944736" Active="true" Order="2">
<Name>
<Translation Language="de">Geschäftsreisender</Translation>
<Translation Language="en">Corporate</Translation>
</Name>
</RatingVisitor>
</RatingVisitors>
<Salutations>
<Salutation Id="9d1acf1a-db25-4578-8c42-a0658677a599" Order="1" Language="de" Gender="m" Title="Herr"
Default="true" ChangeDate="2008-05-08T17:12:00" />
<Salutation Id="e87fa075-01b2-4bd5-9e77-5d0ba6e20a4b" Order="2" Language="de" Gender="f" Title="Frau"
Default="false" ChangeDate="2008-05-08T17:12:00" />
<Salutation Id="5b1528d2-fd4e-4a71-9955-d8dce8b890fd" Order="3" Language="de" Gender="u" Title="" Default="false"
ChangeDate="2008-05-08T17:13:00" />
<Salutation Id="bb8c2827-c101-4da5-aadf-ea4a82948ab0" Order="4" Language="de" Gender="u" Title="Familie"
Default="false" ChangeDate="2008-05-08T17:13:00" />
<Salutation Id="079bf6d5-ab63-46a7-825d-622d55734c62" Order="5" Language="de" Gender="u" Title="Herr und Frau"
Default="false" ChangeDate="2008-05-08T17:13:00" />
<Salutation Id="5640fbfd-8103-4b68-b04a-469a4b57863e" Order="1" Language="en" Gender="m" Title="Mr"
Default="true" ChangeDate="2008-04-30T15:10:00" />
<Salutation Id="e34c5bba-25c2-4910-bdbd-160d6b147d7c" Order="2" Language="en" Gender="f" Title="Mrs"
Default="false" ChangeDate="2008-04-30T15:10:00" />
<Salutation Id="3053794b-bd99-467f-8415-31870c56f7cb" Order="5" Language="en" Gender="u" Title="Mr and Mrs"
Default="false" ChangeDate="2008-04-30T15:09:00" />
<Salutation Id="5cc604d7-1e91-4059-be1c-b6b9aecc87a4" Order="6" Language="en" Gender="u" Title="Family"
Default="false" ChangeDate="2008-04-30T15:10:00" />
</Salutations>
<GuestCountries>
<Country Id="f8e30898-312e-404d-bc8e-71bded8a984a" Code="AD" ChangeDate="2007-10-29T14:50:00"
DialCode="+376" >
<Name>
<Translation Language="de">Andorra</Translation>
<Translation Language="en">Andorra</Translation>
</Name>
</Country>
<Country Id="af43cb0a-b8be-484b-959a-d4bada7f7fca" Code="AE" ChangeDate="2011-01-18T15:48:00"
DialCode="+971">
<Name>
<Translation Language="de">United Arabian Emirates</Translation>
<Translation Language="en">United Arabian Emirates</Translation>
</Name>
</Country>
<Country Id="24383212-0217-45fa-a157-eaa958c006fb" Code="AF" ChangeDate="2009-07-23T13:51:00" DialCode="+93">
<Name>
<Translation Language="de">Afghanistan</Translation>
<Translation Language="en">Afghanistan</Translation>
</Name>
</Country>
</GuestCountries>
<ShopItemGroups>
<ShopItemGroup Id="92e92cab-9139-49f9-b9dd-b187b4d58e8c" Type="Brochure" Order="1" ChangeDate="2011-11-
02T10:33:00">
<Name>

Key Values 20 of 241


DESKLINE 3.0 STANDARD INTERFACE

<Translation Language="de">Wein</Translation>
<Translation Language="en">Wein</Translation>
</Name>
</ShopItemGroup>
<ShopItemGroup Id="9ea286c0-2c5d-4745-80a3-c81a04b8aa32" Type="Brochure" Order="1" ChangeDate="2010-03-
30T13:23:00">
<Name>
<Translation Language="de">Allgemeine Prospekte</Translation>
<Translation Language="en">Allgemeine Prospekte</Translation>
</Name>
</ShopItemGroup>
<ShopItemGroup Id="8ff62c73-16ad-489c-aea3-d761585da2c7" Type="Brochure" Order="1" ChangeDate="2009-06-
06T23:39:00">
<Name>
<Translation Language="de">Prospekte</Translation>
<Translation Language="en">Prospekte</Translation>
</Name>
</ShopItemGroup>
</ShopItemGroups>
<InfrastructureTypes>
<InfrastructureType Type="4" Order="4" ChangeDate="2010-02-19T14:51:00" Active="true">
<Name>
<Translation Language="de">Wellness &amp; Gesundheit</Translation>
<Translation Language="en">Wellness &amp; Health</Translation>
</Name>
</InfrastructureType>
<InfrastructureType Type="1" Order="1" ChangeDate="2010-02-19T14:50:00" Active="true">
<Name>
<Translation Language="de">Essen &amp; Trinken</Translation>
<Translation Language="en">Food &amp; Beverage</Translation>
</Name>
</InfrastructureType>
<InfrastructureType Type="3" Order="3" ChangeDate="2010-02-19T14:51:00" Active="true">
<Name>
<Translation Language="de">Sport &amp; Freizeit</Translation>
<Translation Language="en">Sport &amp; Leisure</Translation>
</Name>
</InfrastructureType>
<InfrastructureType Type="8" Order="8" ChangeDate="2010-02-19T14:52:00" Active="true">
<Name>
<Translation Language="de">Infrastruktur</Translation>
<Translation Language="en">Infrastructure</Translation>
</Name>
</InfrastructureType>
<InfrastructureType Type="6" Order="6" ChangeDate="2010-02-19T14:52:00" Active="true">
<Name>
<Translation Language="de">Sehenswürdigkeiten</Translation>
<Translation Language="en">Places of interest</Translation>
</Name>
</InfrastructureType>
</InfrastructureTypes>
<InfrastructureTopics>
<InfrastructureTopic Id="b25cca1a-6633-4072-a58e-029762d44c55" Type="1" SubType="1" ChangeDate="2010-06-
01T17:49:00" Active="true" Global="true">
<Name>
<Translation Language="de">Restaurant</Translation>
<Translation Language="en">restaurant</Translation>
</Name>
</InfrastructureTopic>
<InfrastructureTopic Id="49add583-47c7-488b-9309-03fb052a5fa7" Type="1" SubType="2" ChangeDate="2010-06-
01T18:24:00" Active="true" Global="true">
<Name>
<Translation Language="de">Live-Musik/Konzerte</Translation>
<Translation Language="en">live music/concerts</Translation>
</Name>
</InfrastructureTopic>
</InfrastructureTopics>
<SerialEvents>
<SerialEvent Id="f6602355-4b08-49e6-b72e-3f835d15ab49" ChangeDate="2011-01-27T16:41:00" Active="true">

Key Values 21 of 241


DESKLINE 3.0 STANDARD INTERFACE

<Name>
<Translation Language="de">Seefestspiele</Translation>
<Translation Language="en">Seefestspiele</Translation>
</Name>
</SerialEvent>
<SerialEvent Id="467d9339-9870-4780-a9a2-5e9a481c7c29" ChangeDate="2011-07-07T09:27:00" Active="true">
<Name>
<Translation Language="de">HeimatHerbst</Translation>
<Translation Language="en">HeimatHerbst</Translation>
</Name>
<Descriptions>
<Description Id="f820c8e6-febe-41a4-8262-c2b4aad85712" Type="EventGroup" Language="de" Systems="L T I C"
ShowFrom="101" ShowTo="1231" ChangeDate="2011-07-07T09:28:00">Nur im Herbst</Description>
</Descriptions>
<Documents>
<Document Id="ff630f0d-539f-41eb-a95c-36075d1de836" Type="EventGroup" Class="Image" Systems="L T I C"
Order="1" ShowFrom="101" ShowTo="1231" Copyright="" Extension="jpg" Size="0" ChangeDate="2011-07-07T09:30:00">
<Names>
<Translation Language="de">Leuchtturm</Translation>
<Translation Language="en">Leuchtturm</Translation>
</Names>
<URL>http://interfacetest.deskline.net/Handlers/Document?code=FRT&amp;id=ff630f0d-539f-41eb-a95c-
36075d1de836</URL>
</Document>
</Documents>
</SerialEvent>
</SerialEvents>
<CustomAttributes>
<CustomAttribute Id="6bfa4856-7169-4df9-a90a-e458fcbfacff" Type="Event" DataType="String" Length="100" Value=""
Name="Event info" ChangeDate="2012-01-11T10:15:00" />
<CustomAttribute Id="c576ba02-df36-44c1-b264-f1d36dc97ebd" Type="Infrastructure" DataType="Number" Length="2"
Value="0" Name="Katalog XY Seite" ChangeDate="2012-01-11T10:15:00" />
<CustomAttribute Id="2c81ec5c-efda-468e-b6d3-3c3eb5a8aea4" Type="Infrastructure" DataType="Number" Length="3"
Value="0" Name="Säle" ChangeDate="2012-01-11T10:15:00" />
</CustomAttributes>
<FallbackLanguages>
<Language Active="true" Code="de" ChangeDate="2012-04-20T09:55:00" Default="false" Order="1" Fallback="en">
<Name>
<Translation Language="de">Deutsch</Translation>
<Translation Language="en">German</Translation>
</Name>
</Language>
<Language Active="true" Code="it" ChangeDate="2012-04-20T09:55:00" Default="false" Order="2" Fallback="en">
<Name>
<Translation Language="de">Italienisch</Translation>
<Translation Language="en">Italian</Translation>
</Name>
</Language>
<Language Active="true" Code="en" ChangeDate="2012-04-20T09:55:00" Default="true" Order="4" Fallback="de">
<Name>
<Translation Language="de">Englisch</Translation>
<Translation Language="en">English</Translation>
</Name>
</Language>
</FallbackLanguages>
<LinkTypes>
<LinkType Type="0" Order="999" ChangeDate="1980-01-01T00:00:00" Active="true" Global="true">
<Name>
<Translation Language="de">Unkategiorisiert</Translation>
<Translation Language="en">Uncategorised</Translation>
</Name>
</LinkType>
<LinkType Type="1" Order="1" ChangeDate="2012-04-18T15:09:00" Active="true" Global="true">
<Name>
<Translation Language="de">Objekt URL</Translation>
<Translation Language="en">Object URL</Translation>
</Name>
</LinkType>
</LinkTypes>

Key Values 22 of 241


DESKLINE 3.0 STANDARD INTERFACE

<HandicapGroups>
<HandicapGroup Active="false" Id="22cec13f-5d23-4d52-b519-0f316e4409ae" ChangeDate="2012-02-01T13:23:00"
Global="true">
<Name>
<Translation Language="de">Rollstuhlnutzer</Translation>
<Translation Language="en">Wheel chair</Translation>
</Name>
</HandicapGroup>
</HandicapGroups>
<HandicapTypes>
<HandicapType Active="true" Id="3509372F-0D89-4285-BF0A-5C80C14E11AB" ChangeDate="2012-08-
23T15:19:50.1537225+02:00">
<Name>
<Translation Language="de">Leistungsträger</Translation>
<Translation Language="en">Service provider</Translation>
</Name>
</HandicapType>
<HandicapType Active="true" Id="52F3354A-60C5-451D-A9A0-C4A695603A47" ChangeDate="2012-08-
23T15:19:50.1537225+02:00">
<Name>
<Translation Language="de">Veranstaltung</Translation>
<Translation Language="en">Event</Translation>
</Name>
</HandicapType>
</HandicapTypes>
<HandicapFacilityGroups>
<HandicapFacilityGroup Id="f2bf4a64-433d-4e77-ad95-2b3c02cbdd6c" ChangeDate="2012-02-01T13:25:00"
Global="true">
<Name>
<Translation Language="de">Parken</Translation>
<Translation Language="en">Parking</Translation>
</Name>
</HandicapFacilityGroup>
<HandicapFacilityGroup Id="0120ac85-ac47-4d26-9880-61640462915f" ChangeDate="2012-02-01T13:25:00"
Global="true">
<Name>
<Translation Language="de">Aufzug</Translation>
<Translation Language="en">Lift/Elevator</Translation>
</Name>
</HandicapFacilityGroup>
</HandicapFacilityGroups>
<HandicapFacilities>
<HandicapFacility Active="false" Id="ee6ce186-17b5-4ff2-8711-05a337a31dc0" ChangeDate="2012-02-01T13:39:00"
Global="true" GroupID="f2bf4a64-433d-4e77-ad95-2b3c02cbdd6c" ValueType="YesNo">
<Name>
<Translation Language="de">Anzahl der Behindertenparkplätze</Translation>
<Translation Language="en">Number of handicapped parking slots</Translation>
</Name>
<HandicapTypes>
<Item Id="6204d43a-1dc3-45a8-bbf0-03f5f50273d6" />
<Item Id="def6e413-ccd6-4dd9-9984-1c468b4f808d" />
<Item Id="a8d74657-7009-41e5-aaa8-35d767aed35a" />
<Item Id="3509372f-0d89-4285-bf0a-5c80c14e11ab" />
<Item Id="8b904488-998c-4c49-bfbf-6756dccd4f08" />
<Item Id="1866d591-8181-4d5e-a59a-88f9fee37d6c" />
<Item Id="ef216a78-3314-4ec1-a7fc-8d7451a891c8" />
<Item Id="6483da81-b263-40e7-a8b8-9bd4b59d5650" />
<Item Id="52f3354a-60c5-451d-a9a0-c4a695603a47" />
<Item Id="370375c7-cad3-4e90-891d-cfb84477bd38" />
</HandicapTypes>
<HandicapGroups>
<Item Id="22cec13f-5d23-4d52-b519-0f316e4409ae" />
<Item Id="d9892893-cfff-448f-b063-90e2bc74da25" />
<Item Id="d5bbacaa-b80a-4cfa-8789-cca97562b43a" />
</HandicapGroups>
</HandicapFacility>
</HandicapFacilities>
<VisitorTaxInfo>
<VisitorTax TownId="a21e6f3f-7ef2-4695-b759-4087c6b00ad8" Code="AA" Name="Anichka" ValidFrom="2009-06-

Key Values 23 of 241


DESKLINE 3.0 STANDARD INTERFACE

24T17:29:00" currency="EUR" ChildrenFromAge="2" AdultFromAge="18" TaxAdult="2" TaxChild="1" ChangeDate="2011-04-


21T15:00:00" />
<VisitorTax TownId="c11718bb-8412-42a4-b06f-4cf4aa9e5f46" Code="AA" Name="Anichka" ValidFrom="2009-06-
24T17:29:00" currency="EUR" ChildrenFromAge="2" AdultFromAge="18" TaxAdult="2" TaxChild="1" ChangeDate="2011-04-
21T15:00:00" />
<VisitorTax TownId="22eb0eac-617d-408b-a4a2-a0d4d742468d" Code="AA" Name="Anichka" ValidFrom="2009-06-
24T17:29:00" currency="EUR" ChildrenFromAge="2" AdultFromAge="18" TaxAdult="2" TaxChild="1" ChangeDate="2011-04-
21T15:00:00" />
</VisitorTaxInfo>
</KeyValues>
</Result>
</FeratelDsiRS>

24 of 241
DESKLINE 3.0 STANDARD INTERFACE

BASIC DATA FOR SERVICE PROVIDERS


The concept for getting basic data from the DSI allows for a maximum of flexibility to deal with exports and
changed data. If you have to get a list of hotels, then for every hotel request all descriptions and then request
all documents and so on. This logic would be supported. But we also support requests to get more data at once
with fewer connections necessary. DSI sends the live data from the customer’s database.

STRUCTURE OF A SERVICE PROVIDER WITH SERVICES AND PRODUCTS


A short overview how data regarding a service provider is entered and connected in Deskline 3.0: first, we have
the service provider which is for example a hotel:

A service provider will have one or more categories, classifications, marketing groups, facilities and so on. Also,
there are descriptions, documents, links, etc. - all information regarding the object itself, not about services or
products.

Then there can be services for this object:

A service can be seen as a summary of physical rooms with the same properties:

This room can also have descriptions, documents, facilities – and availabilities. For example there can be 10
available rooms of this category on a given day and only 8 on another day or 0 on another day if all rooms of
this type are occupied.

Based on one service there can be one or several products. Products are the units that can be booked by a
customer. So it is possible to sell a service either as a regular room (triple room with shower or bath in this
case) or as a special package or anything else the service provider can create. Restrictions about

Basic Data For Service Providers 25 of 241


DESKLINE 3.0 STANDARD INTERFACE

arrival/departure, min/max length of stay, min/max adults, min/max children and so on - including the prices -
are all defined on the product level:

Or:

Products can have their own descriptions or documents but if there aren’t any, then the service
description/document will be used as a fallback.

As soon as the service provider changes the availabilities for the service to 5, there are 5 units of the product
“Triple room” or 5 units of the product “Weekend package for two” available. As soon as for example one
weekend package is booked, the availability will be reduced and there are only 4 units of either product
available.

This way, a service provider can sell a room in multiple choices for the guest.

A DDITIONAL S ERVICE PROVIDERS AND ADDITIONAL SERVICES


The request logic for additional service providers is the same as for service providers with the type
accommodation. Additional services are basically all services that are not an accommodation, such as ski-

Basic Data For Service Providers 26 of 241


DESKLINE 3.0 STANDARD INTERFACE

passes, entry for the spa, guided hiking tours and whatsoever. The data structure for the service provider is
very much the same with some fields less. The additional services themselves have a different structure in the
details. A service provider of type accommodation can still have additional services whereas a service provider
of type additional service can only have additional services.

SCHEDULING THE SYNCHRONIZATION


Synchronizing your database with the complete Deskline data should best be scheduled during less frequent
hours (e.g. night hours).

REQUEST WORKFLOW
It is still highly recommended to request basic data in different steps and intervals, e.g. documents and
descriptions less often than prices since not all of the content is changed constantly! Bear in mind that a
request with all elements and all data can be quite a big file of several MB and will reflect in the response time.
Therefore splitting the Basic Data requests is strongly encouraged and the best way to do so is to get the details
per service provider. Also, you must not make a request for a whole region to get basic data, at max use this
per town or per district.

Synchronization based on Service Providers

This is a new way that also helps targeting the synchronization to whole objects at once.

1. Get list of Towns from Key Values according to the top-location provided by feratel
2. Get list of Service Providers per Town (Details)

For every Service Provider generate a request to get the full details. For example if you don’t need the
service/product level:
<Range Code="TO">
<Item Id="1DA11046-9505-4313-9D94-82903F2BCC04" />
</Range>
<BasicData>
<Filters>
<ServiceProvider Type="Accommodation" Id="21EC2020-3AEA-1069-A2DD-08002B30309D" />
<Languages>
<Language Value="en" />
<Language Value="de" />
</Languages>
</Filters>
<ServiceProviders>
<Details DateFrom="2009-01-01" />
<Documents DateFrom="2009-01-01" Systems="T" />
<Descriptions DateFrom="2009-01-01" Systems="T" />
<Facilities DateFrom="2009-01-01" />
<Addresses DateFrom="2009-01-01" />
</ServiceProviders>
</BasicData >

Depending on the needs it’s of course not always required to get certain elements. If you only need to realize a
hotel list without the detail then you won’t need the whole services and product part at all.

Basic Data For Service Providers 27 of 241


DESKLINE 3.0 STANDARD INTERFACE

REQUEST
A request consists of three different parts: first, the mandatory values, then the optional filter and then the
definition, which elements to provide in the response.

Request field Description Can be empty? Multiple?


Originator The code of the point of sale requesting the data.
Provided by feratel.
Company The code of the company requesting the data. Provided
by feratel.
Range and GUIDs First, a range code to select the data must be defined.
IDs This is an enumeration if it is a town (TO) or a district (DI)
for example. The IDs of towns/districts are part of the
KeyValues function. If there is a need to call data owners
(DO) directly, the IDs are provided by feratel. The top
location (i.e. highest/widest range possible) will be
provided by feratel to get started (see range example in
KeyValues.xml). Basic data requests should be done at
max per town or district, never per region unless
specifically defined by feratel.
Filters While the Sales Channel is mandatory in a few places (for
SalesChannelId example requesting prices) here it is optional in the
definition. Feratel will tell if it must be used for a project
depending on the requirements and the decision taken
by the customers. This filters the response to only return
service providers that have products assigned to the
specified Sales Channel.
Filters If you have access to more than one database with your
DBCode Originator and you want to get data only for one
database you can send us the DBCode with this attribute.
This has the advantage that we only look on this
database for the data. The Response will be much faster.
Filters <PreSelectedServiceProviderIDs> can be used to list
PreSelected- more than one service provider based on the SP-ID.
ServiceProviderIDs
Filters The type of service providers. Either Accommodation or
ServiceProvider Type AdditionalService.
Filters To search inside one service provider only, the Deskline
ServiceProvider ID 3.0 GUID can be provided in the request.
Filters To search inside one service provider only, the Deskline
ServiceProvider Code object code can be provided in the request.
Filters To search inside one service provider only, the full name
ServiceProvider Name of the service provider can be provided in the request.
Note: ID/Code/Name is either/or: if an ID is provided, Code/Name will not be checked and so on.
Filters Enumeration: All/Active/Inactive. The default setting is
ServiceProvider Status “Active”, so the interface only returns active service
providers. If it is necessary to know which service
providers were deactivated, the value All or Inactive
can be used. The Element <active> is returned on the
details level of the response.
Filters By default, all service provides are returned, but with
ServiceProvider setting OnlyBookable to true only those are returned
OnlyBookable that are used for bookings.
Filters To filter the response only to a specified service of a
Service Id service provider (must be used in combination with

Basic Data For Service Providers 28 of 241


DESKLINE 3.0 STANDARD INTERFACE

ServiceProvider Id)
Filters Enumeration: All/Active/Inactive. The default setting is
Service Status “Active”, so the interface only returns active services. If
it is necessary to know which services were
deactivated, the value All or Inactive can be used. The
Element <active> is returned on the details level of the
response.
Filters To filter the response only to a specified product of a
Product Id service provider (must be used in combination with
ServiceProvider Id)
Filters Enumeration: All/Active/Inactive. The default setting is
Product Status “Active”, so the interface only returns active products.
If it is necessary to know which productss were
deactivated, the value All or Inactive can be used. The
Element <active> is returned on the details level of the
response.
Filters To filter the response to only return products based on
Product a specified accommodation type: HotelRoom,
AccommodationType Apartment, Camping
Filters To filter the response to only return products based on
Product ProductType a specified product type: Accommodation,
AdditionalService or Package
Filters The language filter must be used to provide which
Language(s) translations should be transferred inside the DSI
response. It’s possible to request more than one
language at the time to save the amounts of requests
necessary.
Filters Basic data requests can be limited to provide only
Marketing Group(s) service providers that are part of special marketing
groups. E.g. “Mountain bike hotels”, “Urlaub am
Bauernhof”. The list of these IDs is provided in the Key
Values Function.
Filters Basic data requests can be limited to provide only
Category service providers that are part of the requested
categories. E.g. Hotels, Inns, Pensions, … the list of
these IDs is provided in the Key Values Function.
DateFrom (per Element) DateFrom attributes occur within the service provider
elements of the request and are not inherited. For
example, it is possible to request all service provider
basic data that was changed in the last week without
sending all the documents, descriptions, products and
so on. Or it is possible to only request User Ratings from
the last month.
Following filter element works only if you are requestion HousePackageMasters in Request
Filters Enumeration: All/Active/Inactive. The default setting is
HousePackageMasters  “Active”, so the interface only returns active
Status HousePackageMasters. If it is necessary to know which
HousePackageMasters were deactivated, the value All
or Inactive can be used. The Element <active> is
returned on the details level of the response.
<ServiceProvider> <ServiceProvider ShowDataOwner="" IncludeVTInfo="" IncludeTranslations="" >
Type = Accommodation <Details />
<Documents IncludeResolution="" />
Content Elements: <Links IncludeTranslations="" />
<Descriptions Markup=”” />
<Facilities />
<Addresses GetSettlementAddresses="" DetailedInformation="true" />

Basic Data For Service Providers 29 of 241


DESKLINE 3.0 STANDARD INTERFACE

<RatingsAverage Status="" />


<CustomAttributes />
<HotSpots />
<MetaRating CheckMinAmount="true" />
<ClosedPeriods />
<HandicapFacilities />
<HandicapClassifications />
<GTC />
<QualityDetails />
<HousePackageMasters />
<Services>
<Details IncludeTranslations="" />
<Documents Systems="" IncludeResolution="" />
<Descriptions Systems="" Markup=”” />
<Links IncludeTranslations="" />
<Facilities />
<Availabilities Start="" End="" />
<HandicapFacilities />
<HandicapClassifications />
<Products>
<Details />
<Documents Systems="" IncludeResolution="" />
<Links IncludeTranslations="" />
<Descriptions Systems="" Markup=”” />
<Prices SalesChannel=""/>
<PriceDetails SalesChannel="" Start="" End="" />
<ArrivalDepartureTemplates SalesChannel="" Start="" End="" />
<SalesRuleTemplates SalesChannel="" Start="" End="" />
<Availabilities SalesChannel="" Start="" End="" />
<Gaps Start="" End="" />
<CancellationPaymentTemplates SalesChannel="" Start="" End="" />
</Products>
</Services>
<CancellationPaymentInfo />
</ServiceProvider>
<ServiceProvider> <ServiceProvider ShowDataOwner="" >
Type = AdditionalService <Details />
<Documents Systems="" IncludeResolution="" />
Content Elements: <Links Systems="" IncludeTranslations="" />
<Descriptions Systems="" Markup=”” />
<Facilities />
<Addresses GetSettlementAddresses="" />
<RatingsAverage />
<CustomAttributes />
<HotSpots />
<AdditionalServices>
<Details />
<Documents Systems="" IncludeResolution="" />
<Descriptions Systems="" Markup=”” />
<Links IncludeTranslations="" />
<Facilities />
<Availabilities Start="" End="" />
<AdditionalProducts>
<Details />
<PriceDetails SalesChannel="" Start="" End="" />
<SalesRuleTemplates SalesChannel="" Start="" End="" />
</AdditionalProducts>
</AdditionalServices>
</ServiceProvider >
ServiceProvider Attribute True/False value, false by default. When set to true, the
ShowDataOwner DSI will also return one more element in service
provider details. It is the organization code of the
tourism organization this service provider belongs to.
<ServiceProvider Id=" " ChangeDate="">
<Details>
...
<DataOwner>FERATEL</DataOwner>
</Details>
</ServiceProvider>

Basic Data For Service Providers 30 of 241


DESKLINE 3.0 STANDARD INTERFACE

ServiceProvider Attribute True/False value, false by default. When set to true, the
IncludeVTInfo DSI will also return one more attribute in Town elment
inside provider details. It is the visitor tax code of the
tourism organisation this service provider belongs to.

<Details>
<Name>Simotel</Name>
<Town VTCode="AD">5c7e1d37-0060-4811-a996-
a8b36094d01e</Town>

</Details>
Details True/False value, false by default. When set to true,
IncludeTranslations response will include also the Name fo the Service
Provider in requested languages with an additional
attribute names:

<Details>
<Name>Simotel</Name>
<Names>
<Translation Language="de">German Simotel</Translation>
<Translation Language="en">Simotel</Translation>
</Names>

Descriptions Enum: true/false default: false


Markup when you set the optional attribute Markup=”true” you
get back html format tags which might be selected from
the customers.
Links IncludeTranslations True/False value, false by default. When set to true,
response will include also the Name fo the Link in
requested languages.
Addresses Attribute True/False value, false by default. When set to true, the
GetSettlementAddresses DSI will also return two more addresses: type
“Reservations” and “VisitorRegistration” which are used
for contacting the service providers when doing the
settlement of bookings.
Addresses Attribute true/false value, false by default. When set to true, DSI
DetailedInformation returns also Addresse Pictures and Descritpions. So you
can show on your homepage a picture and description
of the landlord.
Price, PriceDetails The same GUID of the SalesChannel that will be used
Attribute SalesChannel for the search has to be provided in order to get prices
per product.
Price vs. PriceDetails Since 1.0.20 there are two options to get prices in the
basic data interface. Price as before returns just a basic
from-to value, PriceDetails really return all the details
including meals, surcharges, discounts, price-splitting,
child-reductions, extras, ... getting the PriceDetails is
only possible when at least the Service Provider ID is
provided.

In a basic data request, Price and PriceDetails are a


choice in XML, meaning that only one of those options
can be selected at one time, so when starting a project
the need has to be defined.

With Update 1.0.21 we introduced two optional


Attributes for the Prices-Element: Start and End.
Basic Data For Service Providers 31 of 241
DESKLINE 3.0 STANDARD INTERFACE

Without Start/End the minimum/maximum value are


returned from all available prices for a product without
checking the date. When Start/End is provided, the
min/max values are only checked for values inside this
period. In the PriceDetails Element Start and End are
required.

The PriceDetails for AdditionalProducts have a different


structure than the PriceDetails for Accommodation
Products.
Arrival Departure See below, the information about minimum length of
Templates stay and valid weekdays for arrivals/departures as
defined by the service provider.
Sales Rule Templates See below, the information when and where a product
is bookable and when it is not as defined by the service
provider.
Availabilities Attributes Note: Getting availabilities per service and per day
should be avoided, please refer to the search to get
available objects (availabilities are not the only setting
that define if a hotel is available or not and only a
search will check for all required conditions).

If they must be used, then the DateFrom Attribute and


the Start/End date must be provided so it is possible to
get availabilities for a whole year or only for a month
for example.

Important: Availabilities are only returned per Service


Provider when the Service Provider ID is passed in the
<ServiceProvider> Filter!

Important: Availabilities can also be stored on a


product level if the service provider uses different
availabilities for different sales channels. Usage of
product availabilities has to be checked with each
customer.
Gaps What is a gap?
If a product has very strict arrival and departure
conditions e.g. minimal length of stay 7 days, these
settings are valid for all availabilities. If a service
provider now has a gap because a guest shortens his
stay for 2 days then he can enter a gap to be bookable
for these 2 days with different conditions. Gaps are
included into search for availabilities.

Gaps have their own availabilities and conditions and


can have their own prices or use the product prices.
CancellationPaymentInfo Information about cancellation and payment setting of
the service provider. Only available if set and
functionality provided by tourist office.
Different that the system logic for other kind of
templates there can be one STANDARD Template
defined on service provider level, which is valid for all
products unless there is a different template assigned.
For special offers with special prices like EarlyBooker,
LastMinute or any UserDefined special procies there

Basic Data For Service Providers 32 of 241


DESKLINE 3.0 STANDARD INTERFACE

can be special cancellation and payment rules valid.


These settings are defined on service provider level. So
CancellationPaymentInfo provides a list of templates
for these special reasons. Enumeration: STANDARD,
EarlyBooker, LastMinute or UserDefined
For further details to the response structure please see
CancellationPaymentTemplates on product level.

EXAMPLES

Get details for one service provider:


<?xml version="1.0" encoding="utf-8"?>
<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://interface.deskline.net/DSI/XSD">
<Request Originator="FERATEL" Company="FERATEL">
<Range Code="TO">
<!--Testdestination-->
<Item Id="50AE0318-5ABE-4339-88E3-09B704D7FA77" />
</Range>
<BasicData>
<Filters>
<ServiceProvider Type="Accommodation" Id="5BFDBFA8-8A0B-470E-998B-00242D0877C3" />
<Languages>
<Language Value="de" />
<Language Value="en" />
</Languages>
</Filters>
<ServiceProviders ShowDataOwner="True">
<Details DateFrom="1980-01-01" />
<Documents DateFrom="1980-01-01" Systems="T" IncludeResolution="true" />
<Descriptions DateFrom="1980-01-01" Systems="T" Markup=”true” />
<Links DateFrom="1980-01-01" IncludeTranslations="true" />
<Facilities DateFrom="1980-01-01" />
<Addresses DateFrom="1980-01-01" DetailedInformation="true" />
<RatingsAverage DateFrom="1980-01-01" Status="Active" />
<CustomAttributes DateFrom="1980-01-01" />
<HotSpots DateFrom="1980-01-01" />
<MetaRating DateFrom="1980-01-01" CheckMinAmount="true" />
<ClosedPeriods DateFrom="1980-01-01" />
<HandicapFacilities DateFrom="1980-01-01" />
<HandicapClassifications DateFrom="1980-01-01" />
<GTC DateFrom="1980-01-01" />
<QualityDetails DateFrom="1980-01-01" />
<HousePackageMasters DateFrom="1980-01-01" />
<HousePackageMastersSelfAssign DateFrom="1980-01-01" />
<Services>
<Details DateFrom="1980-01-01" />
<Documents DateFrom="1980-01-01" Systems="T" />
<Descriptions DateFrom="1980-01-01" Systems="T" Markup=”true” />
<Links DateFrom="1980-01-01" IncludeTranslations="true" />
<Facilities DateFrom="1980-01-01" />
<HandicapFacilities DateFrom="1980-01-01" />
<Products>
<Details DateFrom="1980-01-01" />
<Documents DateFrom="1980-01-01" Systems="T" />
<Descriptions DateFrom="1980-01-01" Systems="T" />
<Links DateFrom="1980-01-01" IncludeTranslations="true" />
</Products>
</Services>
<CancellationPaymentInfo DateFrom="1980-01-01" />
</ServiceProviders>
</BasicData>
</Request>
</FeratelDsiRQ>

Basic Data For Service Providers 33 of 241


DESKLINE 3.0 STANDARD INTERFACE

RESPONSE
Below is an example of a full response with all elements and attributes possible at the moment. Mind that
based on the request it’s possible that not all of these elements are part of the response. For details on the
data types and XML enumerations refer to the XSD documents.

Service Provider:

Response field Description Can be empty? Multiple?


ID GUID of the service provider
ChangeDate Date/time indicator when the item was last changed.
Name Name of the service provider
Code An internal code defined by the customer.
Type Type of service provider (accommodation, additional
service, …)
Town GUID of the town of the service provider
District District inside the town.
Priority Number to define the priority in lists, to allow
customers their own sort order
Rooms Amount of rooms in a hotel. Only for Accommodation
Service Providers and not used for Service Providers
with the type AdditionalService.
Beds Amount of beds in a hotel. Only for Accommodation
Service Providers and not used for Service Providers
with the type AdditionalService.
Position Latitude, GPS Coordinates
Longitude
Categories e.g. hotel, inn, pension, etc.
If there are any IDs present that are not provided in the
Key Values function it is because of items that were
created by the customers themselves and therefore are
not global and not available in the Key Values. Only for
Accommodation Service Providers and not used for
Service Providers with the type AdditionalService.
Stars *, **, ***
If there are any IDs present that are not provided in the
Key Values function it is because of items that were
created by the customers themselves and therefore are
not global and not available in the Key Values. Only for
Accommodation Service Providers and not used for
Service Providers with the type AdditionalService.
Classifications e.g. flowers
If there are any IDs present that are not provided in the
Key Values function it is because of items that were
created by the customers themselves and therefore are
not global and not available in the Key Values. Only for
Accommodation Service Providers and not used for
Service Providers with the type AdditionalService.
MarketingGroups Different marketing groups a service provider can be
part of.
If there are any IDs present that are not provided in the

Basic Data For Service Providers 34 of 241


DESKLINE 3.0 STANDARD INTERFACE

Key Values function it is because of items that were


created by the customers themselves and therefore are
not global and not available in the Key Values. Only for
Accommodation Service Providers and not used for
Service Providers with the type AdditionalService.
HotelChain e.g. Best Western
If there are any IDs present that are not provided in the
Key Values function it is because of items that were
created by the customers themselves and therefore are
not global and not available in the Key Values. Only for
Accommodation Service Providers and not used for
Service Providers with the type AdditionalService.
Active Indicates if the service provider is active or not.
CreditCards The names of accepted credit cards of this service
provider.
GridSquare e.g. A1, B4
PlanNumber Number given by the customer for a grid-reference
DBCode 3 letter code of the database. This is also part of the
search response and is used for adding items to the
shopping cart and for generating a direct link.
Bookable True/false if the service provider would generally be
bookable. Actual information if a product is bookable
for a certain period/occupancy is to be determined by
using the search function.
BankAccounts Container element for different bank accounts.
BankAccount Id ID of the bank code, see Key Values for the full list.
BankAccount If empty, this is the default bank account for this bank.
CountryCode Any other bank accounts that contain a country code
are for guests from this country. For example: a service
provider in Austria can have an extra bank account for
people from Germany, but everyone else has to use the
Austrian account.
BankAccount IBAN IBAN number
BankAccount Account Account number
CurrencyCode 3 letter currency code for the service provider.
Note: All prices shown for this service provider are in
this currency. If you provide any different currency
code in the request this will be ignored. No currency
changes in basic data response.
Documents Documents can be images, videos, PDF-files, etc. For
each document, the URL will be provided the image can
then be downloaded into an external database. The
URL will return the original uploaded file by the user,
not a resized or otherwise manipulated version. It is
also possible that documents have different names in
different languages, hence the translations. In addition
there is also a copyright note for each document if
necessary. Each document can either have a From-To
timeframe (only day/month, not year) or can be set to
be shown as “always” in which case From-To is send as
“101”-“1231” in the element. Documents can also be
set to only be available for different output systems
such as: local (Deskline 3.0 backend), internet
presentation, Informator or catalog productions. When

Basic Data For Service Providers 35 of 241


DESKLINE 3.0 STANDARD INTERFACE

requesting basic data the Systems-Attribute must


already be provided to filter only internet-documents
for example. For Service Providers there is also a
special type “logo” to identify if the service provider
uploaded a special logo. The extension is part of the
response.
Links There is a URL, name, type and order for each link
address connected to the parent. Type categorizes the
link in different groups. E.g. Object URL for homepage
Descriptions Descriptions in various languages. Each description can
either have a From-To timeframe (only day/month, not
year) or can be set to be shown as “always” in which
case From-To is send as “101”-“1231” in the element.
Line-breaks are not converted to HTML-line-breaks, the
description will be returned as entered in the system.
Descriptions can also be set to only be available for
different output systems such as: local (Deskline 3.0
backend), internet presentation, Informator or catalog
productions. When requesting basic data the Systems-
Attribute must already be provided to filter only
internet-descriptions for example.
Facilities Each service provider can have a lot of different
facilities. In the response, only the ID and value are
sent. The translations are available through the Key
Values function. The value is optional as well and is
used e.g. for the facility information “meeting rooms” –
i.e. “meeting rooms: 3”.
If there are any IDs present that are not provided in the
Key Values function it is because of items that were
created by the customers themselves and therefore are
not global and not available in the Key Values.
Addresses A service provider can consist of more than one
address: Object, Landlord, Owner, Keyholder.
ID ID of the address.
ChangeDate Date/time indicator when the item was last changed.
Address Company Company name
Address FirstName Contact person first name
Address LastName Contact person last name
Address AddressLine1 Street name / house number, line 1
Address AddressLine2 Street name / house number, line 2, additional line if
necessary
Address Country Country code
Address ZipCode Zip code
Address Town Town name
Address Email Primary e-mail address
Address Fax Fax
Address URL Main homepage of the service provider
Address Phone Landline
Address Mobile Mobile phone number
Address Documents Only included when BasicData Request includes
DetailedInformation=”true” attribute.
Documents can be images, videos, PDF-files, etc. For

Basic Data For Service Providers 36 of 241


DESKLINE 3.0 STANDARD INTERFACE

each document, the URL will be provided the image can


then be downloaded into an external database. The
URL will return the original uploaded file by the user,
not a resized or otherwise manipulated version. It is
also possible that documents have different names in
different languages, hence the translations. In addition
there is also a copyright note for each document if
necessary. Each document can either have a From-To
timeframe (only day/month, not year) or can be set to
be shown as “always” in which case From-To is send as
“101”-“1231” in the element. Documents can also be
set to only be available for different output systems
such as: local (Deskline 3.0 backend), internet
presentation, Informator or catalog productions. When
requesting basic data the Systems-Attribute must
already be provided to filter only internet-documents
for example. The extension is part of the response.
Address Description Only included when BasicData Request includes
DetailedInformation=”true” attribute.
Descriptions in various languages. Each description can
either have a From-To timeframe (only day/month, not
year) or can be set to be shown as “always” in which
case From-To is send as “101”-“1231” in the element.
Line-breaks are not converted to HTML-line-breaks, the
description will be returned as entered in the system.
Descriptions can also be set to only be available for
different output systems such as: local (Deskline 3.0
backend), internet presentation, Informator or catalog
productions. When requesting basic data the Systems-
Attribute must already be provided to filter only
internet-descriptions for example.
CustomAttributes CustomAttributes must only be used if the
customer/destination specifies the demand!
CustomAttributes are a list of fields that can be defined
per destination.

When requesting CustomAttributes it is possible that


the element will be empty.
RatingsAverage Ratings are a module that can be activated for a
customer. Therefore the presence of ratings differs
from customer to customer.
RatingAverage The ratings are split by main groups of
<RatingAverage> by hotel, apartment, … and will have
an average value per group for the values and
satisfaction. A total count of ratings and times the
service provider was recommended is also part of the
average per group.
Rating Inside the RatingAverage group you can find the
detailed ratings. Each rating consists of an average of
points based on the given answers (value), a
satisfaction level (1 bad to 5 very good), a nickname
chosen by the user, a recommendation rate if the user
decides to recommend the service provider and a
visitor type (e.g. single, family, corporate, ..).
Rating ChangeDate Date/time indicator when the item was last changed.
Rating UserComment The user can leave a comment during the rating. It is

Basic Data For Service Providers 37 of 241


DESKLINE 3.0 STANDARD INTERFACE

not translated.
Rating ParentComment The item that is rated (i.e. the service provider) can
leave a remark about a rating
Rating Answer QuestionID and Value given by the user. The list of
questions and their ID can be provided upon request as
a list as it is not part of the KeyValues function.
Rating CreateDate Date/time indicator when the item was created.
HotSpots ID with HotSpots from KeyValues and Distance (in km!).
MetaRatings If a customer has cooperation with TrustYou or
HotelNavigator service providers gets a mapping
(RatingCode) for this system and in Deskline we also
store their average rating value and the total number
of ratings existing for the service provider. With the
provided RatingCode you can call additional meta
rating information to be displayed on your website.

When you send Request with optional Attribute


CheckMinAmount="true" then you will get back
MetaRatings only if the ServiceProvider has already
reached the min Amount of Ratings defined from the
Organisation

Trustyou offers widgets and json object, Hotelnavigator


offery json object to provice further information.

For further information please send mail to


[email protected]
We will provide you the according documentation.
ClosedPeriods Get periods when the service provider has closed
HandicapFacilities List of Ids of connected handicap facilities to the service
provider, including the value and comments in
requested languages.
HandicapClassifications List of Ids of connected handicap classifications to the
service provider.
QualityDetails -> ContentScore Value for ServiceProvider
ContentScore
QualityDetails -> BestPrice active for ServiceProvider. When Yes then 1
BestPrice else 0
QualityDetaily -> Check for active availabilitys for Serviceprovider are
AvailUpdCheck active. When active then 1 else 0

Basic Data For Service Providers 38 of 241


DESKLINE 3.0 STANDARD INTERFACE

HousePackageMasters/HousePackageMastersSelfAssignment

With HousePackageMasters it is possible to bundle the house packages (product level) of a ServiceProvider
under one Header. This Header can have HolidayThemes, Periodes, Descriptions and Documents.

HousePackageMastersSelfAssignment are HousePackage Masters which are definied from the organization and
the serviceproviders can assign their products to them.

Response field Description Can be empty? Multiple?


HousePackageMasters - The ID of the HousePackageMaster
> HousePackageMaster
@ID
@ChangeDate Date/time indicator when the item was last changed.
Details -> Name Name of the HousePackageMaster
Details -> Priority Priority of the HousePackageMaster
Details -> Guid of the assigned Holiday Themes
HolidayThemes -> Item
@ID
Details -> Active Indicates if the HousePackageMaster is active or not.
Details -> DBCode DB Code of the HousePackageMaster
Details -> ValiDates Type=Always or Type=Period. With the valid dates a
service provider can define when a PackageMaster will
be available. When the Type=Period usually there will
be one or more ValidDate child elements with From/To
values, but it’s also possible that the child elements are
missing when the service provider did not enter any
periods.
Details -> Owner DataOwner of the HousePackageMaster
Descriptions Descriptions in various languages. Each description can
either have a From-To timeframe (only day/month, not
year) or can be set to be shown as “always” in which
case From-To is send as “101”-“1231” in the element.
Line-breaks are not converted to HTML-line-breaks, the
description will be returned as entered in the system.
Descriptions can also be set to only be available for
different output systems such as: local (Deskline 3.0
backend), internet presentation, Informator or catalog
productions. When requesting basic data the Systems-
Attribute must already be provided to filter only
internet-descriptions for example.
Documents Documents can be images, videos, PDF-files, etc. For
each document, the URL will be provided the image can
then be downloaded into an external database. The
URL will return the original uploaded file by the user,
not a resized or otherwise manipulated version. It is
also possible that documents have different names in
different languages, hence the translations. In addition
there is also a copyright note for each document if
necessary. Each document can either have a From-To
timeframe (only day/month, not year) or can be set to
be shown as “always” in which case From-To is send as
“101”-“1231” in the element. Documents can also be
set to only be available for different output systems

Basic Data For Service Providers 39 of 241


DESKLINE 3.0 STANDARD INTERFACE

such as: local (Deskline 3.0 backend), internet


presentation, Informator or catalog productions. When
requesting basic data the Systems-Attribute must
already be provided to filter only internet-documents
for example. The extension is part of the response.
AssignedProducts List of the assigned house packages (accommodation
products of type package) to this container, including Id
of the assigned product.

Basic Data For Service Providers 40 of 241


DESKLINE 3.0 STANDARD INTERFACE

Service:

Deskline 3.0 introduces a product level so every service provider will have services and products. Availability
data or facility information is always on the service level. Descriptions and documents are usually, too, but
there can always be additional descriptions and documents for products (accommodation only, not additional
services/products). A search result in Deskline 3.0 always returns a list of available products.

The response for services and products will follow on the next pages. For accommodation, there are the
elements <Services> and <Products> and for additional services there are the elements <AdditionalServices>
and <AdditionalProducts>.

Response field Description Can be empty? Multiple?


Service ID The ID of the service
ChangeDate Date/time indicator when the item was last changed.
NeedAcco Only in case of additional services this attribute is
included in the response. If it is true this means, that
this additional service can only be booked when also an
accommodation is booked
Type Type of the service, Enumeration of Accommodation or
Additional Service
Name Translations of service name
ServiceClassification Classification of the service .
If there are any IDs present that are not provided in the
Key Values function it is because of items that were
created by the customers themselves and therefore are
not global and not available in the Key Values.
Order Order of the services of a service provider
Rooms Amount of rooms in this service
BedRooms Amount of sleeping rooms in this service
Size Size of the service in m²
UseAvailability Does this service use availabilities or not (1..true,
0…false)
LastAvailabilityChange Date and Time when the availabilities where changed
the last time for this service (either through Deskline or
the WebClient).
MaxAvailability Is there a top limit to the availabilities? E.g. max. 3 units
available?
Code Service Code, refer to KeyValues function
“ServiceCodes”.

Important:
The first 2 characters always reflect the ServiceCodes
ServiceType.
The next two 2 characters always reflect the
ServiceCodes CodeType “Sanitary”.
The rest of the characters always reflect the
ServiceCodes CodeType “AdditionalInfo”.

Example: SUYTNOSMO
SU = Suite
YT = shower and both, toilet

Basic Data For Service Providers 41 of 241


DESKLINE 3.0 STANDARD INTERFACE

NOSMO = no smoker
Active True/false value if the service is set to active or not. By
default, only active services are returned.
Documents Documents can be images, videos, PDF-files, etc. For
each document, the URL will be provided the image can
then be downloaded into an external database. The
URL will return the original uploaded file by the user,
not a resized or otherwise manipulated version. It is
also possible that documents have different names in
different languages, hence the translations. In addition
there is also a copyright note for each document if
necessary. Each document can either have a From-To
timeframe (only day/month, not year) or can be set to
be shown as “always” in which case From-To is send as
“101”-“1231” in the element. Documents can also be
set to only be available for different output systems
such as: local (Deskline 3.0 backend), internet
presentation, Informator or catalog productions. When
requesting basic data the Systems-Attribute must
already be provided to filter only internet-documents
for example. The extension is part of the response.
Links There is a URL, name, type and order for each link
address connected to the parent. Type categorizes the
link in different groups. E.g. Object URL for homepage
Facilities Each service can have a lot of different facilities. In the
response, only the ID and value are sent. The
translations are available through the Key Values
function. The value is optional as well and is used e.g.
for the service facility information “amount
bathrooms” – i.e. “amount bathrooms: 2”.
If there are any IDs present that are not provided in the
Key Values function it is because of items that were
created by the customers themselves and therefore are
not global and not available in the Key Values.
Descriptions Descriptions in various languages. Each description can
either have a From-To timeframe (only day/month, not
year) or can be set to be shown as “always” in which
case From-To is send as “101”-“1231” in the element.
Line-breaks are not converted to HTML-line-breaks, the
description will be returned as entered in the system.
Descriptions can also be set to only be available for
different output systems such as: local (Deskline 3.0
backend), internet presentation, Informator or catalog
productions. When requesting basic data the Systems-
Attribute must already be provided to filter only
internet-descriptions for example.
Availabilities ChangeDate provides the information when there were
the last changes in availabilities.
A collection of <Availability> Elements that consist of
the day and the count of available rooms for this day.

Special cases:
 Count -1002: Closed
 Count -1001: Own use by service provider
The special cases can be interpreted as 0 (not available)
if no distinction is made between not
Basic Data For Service Providers 42 of 241
DESKLINE 3.0 STANDARD INTERFACE

available/closed/own use.
Missing days in between the requested start/end dates
are not available (availability 0).

If availabilities of an additional service are called they


also include the attribute Time, because additional
services can have different availabilities for different
start times.

Additionally we provide a on demand request for


showing availability calendars, so you don’t have to
synchronize huge amount of very dynamic data and just
call and show availabilities on demand on your sites.
HandicapFacilities List of Ids of connected handicap facilities to the
service, including the value and comments in requested
languages.
HandicapClassifications List of Ids of connected handicap classifications to the
service.
<Products>-collection Products are based on services and there can be more
than one product for a service.
Products:

Response field Description Can be empty? Multiple?


Product ID ID of the product
ChangeDate Date/time indicator when the item was last
changed.
Product Name Translations of the product name
Product Type Accommodation, AdditionalService or Package
AccommodationType HotelRoom, Apartment, Camping
HolidayThemes e.g. Weekend, Wedding, Family, etc..
SearchCode Code for a search, can be defined by the customer.
SortOrder Products inside a service can be ordered
Beds Min Minimum amount of beds.
Beds Max Maximum amount of beds.
Adults Min Minimum amount of adults for a product.
Adults Max Maximum amount of adults for a product.
Adults Standard Standard amount of adults for a product.
Children Min Minimum amount of children for a product.
Children Max Maximum amount of children for a product.
MinFullPayer Minimum Fullpayers for a product.
CalcMealAge Calculate Meal price from this age up.
Price Ranges Returns the min/max values of the assigned price
templates for this service provider per adult
occupancy setting. Not limited to any date, this will
reflect the full price range the service provider
entered. The occupancy element repeats for
minimum to maximum adult occupancy.
Calculation Rule Enumeration: PerPerson, PerUnit, Total
Price Nights Number of nights the price is applied to, the default
is 1 but based on Calculation Rule this can be
different. E.g. a total price for 7 nights for a

Basic Data For Service Providers 43 of 241


DESKLINE 3.0 STANDARD INTERFACE

package.
PriceInclVT Information if the price already includes Visitor’s tax
or not.
FromToPrice Is the price a “from-to” price instead of a fixed
price? For the time being, Deskline 3.0 only allows
fixed prices so this will always be 0.
StandardMealCode The code of the meal that is the first meal code
found in all the templates for the requested period.
Enumeration like in search form
(NO/BB/HB/FB/AI/34).
ValidDates For Packages. Type=Always or Type=Period. With
the valid dates a service provider can define when a
package will be available. When the Type=Period
usually there will be one or more ValidDate child
elements with From/To values, but it’s also possible
that the child elements are missing when the
service provider did not enter any periods.
Active True/false value if the product is set to active or not.
By default, only active products are returned.
Documents Documents can be images, videos, PDF-files, etc. For
each document, the URL will be provided the image
can then be downloaded into an external database.
The URL will return the original uploaded file by the
user, not a resized or otherwise manipulated
version. It is also possible that documents have
different names in different languages, hence the
translations. In addition there is also a copyright
note for each document if necessary. Each
document can either have a From-To timeframe
(only day/month, not year) or can be set to be
shown as “always” in which case From-To is send as
“101”-“1231” in the element. Documents can also
be set to only be available for different output
systems such as: local (Deskline 3.0 backend),
internet presentation, Informator or catalog
productions. When requesting basic data the
Systems-Attribute must already be provided to filter
only internet-documents for example. The
extension is part of the response.
Links There is a URL, name, type and order for each link
address connected to the parent. Type categorizes
the link in different groups. E.g. Object URL for
homepage
Descriptions Descriptions in various languages. Each description
can either have a From-To timeframe (only
day/month, not year) or can be set to be shown as
“always” in which case From-To is send as “101”-
“1231” in the element. Line-breaks are not
converted to HTML-line-breaks, the description will
be returned as entered in the system. Descriptions
can also be set to only be available for different
output systems such as: local (Deskline 3.0
backend), internet presentation, Informator or
catalog productions. When requesting basic data
the Systems-Attribute must already be provided to
filter only internet-descriptions for example.
Basic Data For Service Providers 44 of 241
DESKLINE 3.0 STANDARD INTERFACE

Availabilities The Attribute OwnAvailability (true/false) will


indicate if a product is defined to have separate
availabilities or if the underlying service availabilities
should be used. If the value is false, then there will
be no availabilities on the product level. If the value
is true and the response is empty, then there are no
availabilities stored yet (zero/no availabilities).
Gaps A gap has its own Availabilities and arrival and
departure templates. It can have own prices
(UseProductPrice = “false”), then also price
templates are in the response, else the prices of the
product are used.
Products Price Details:

If the basic from-to price is not enough it is possible to get the price details with all fields from child reductions,
surcharges, discounts, price-splitting, extras. These can only be obtained when at least the service provider ID is
present in the request.

Template-Logic:

Prices in Deskline 3.0 are arranged in price templates. Each template contains the full set of information and
can be assigned on a calendar to one or more periods. There is one default-template per product that is always
valid unless overruled by another custom template.

The currency code is returned with the service provider details, currencies usually don’t change within one
destination/customer.

The ranges for occupancy-settings are also checked in combination with the product details – meaning, a user
can’t enter a price for 8 people if the product only allows a maximum of 5 adults.

Please note: values from templates must only be used to display information to the guest while the total price
calculation must only be done with the search function for a specific product. The calculation rules in full detail
would be too complex to recreate from the Deskline 3.0 core functions. When an item is added to the shopping
cart the total price is calculated by this core function.

Response for PriceDetails:

Response field Description Can be empty? Multiple?


PriceDetail Enumeration: PerPerson, PerUnit, Total
Calculation Rule
PriceDetail Number of nights the price is applied to, the default is 1
Price Nights but based on Calculation Rule this can be different. E.g.
Basic Data For Service Providers 45 of 241
DESKLINE 3.0 STANDARD INTERFACE

a total price for 7 nights for a package.


PriceDetail Information if the price already includes Visitor’s tax or
PriceInclVT not.
PriceDetail Is the price a “from-to” price instead of a fixed price?
FromToPrice Right now, Deskline 3.0 only allows fixed prices so this
will always be 0 for now.
PriceDetail Defines if the product requires OrganisationPayment as
OrgPaymentRequired PaymentType in case of a booking (1…yes, 0…no)
PriceTemplates There can be multiple price templates for a product but
it’s also possible that one product does not have any
prices at the moment of the request.
PriceTemplate ID of the price template created by the user.
Id
PriceTemplate Date/Time when the price template was last changed.
ChangeDate
PriceTemplate Internal Name of the price template as defined by the
Name user, do not display to a guest, useful for debugging.
PriceTemplate Only for the standard template if it should not be
ValidFrom available from today on but rather from a different day
on.
PriceTemplate A user can define if this price template reflects the
IsBestPrice “best price” possible for this product. True/false.
PriceTemplate For each template there can be only one default meal
DefaultMealCode code which says if the price in question already
includes the specified meal or not. See enumeration
MealCodes (NO, AI, 34, BB, HB, FB)
Periods Start/End The periods that the price template is assigned to. The
periods for the default (“Standard”) template will
always be empty but for other templates there will be
one or more periods listed. The End date is included in
this case, meaning, the template is still valid on the day
that is returned in the attribute “End”.
Prices Information about the basic price and surcharges and
discounts.
BasePrices\BasePrice The price for adults in one or more different occupancy
levels.
OccupancyFrom Adults from
OccupancyTo Adults to
Price Price
BasePrice This is the price for the additional bed. The additional
AdditionalBed bed can be entered for any occupancy bigger than the
standard occupancy.
Example: min. adults = 1; max. adults = 4; standard = 2
If the price range is from 1 to 4, then the standard price
is calculated for 1 and 2 persons. The additional price
then is calculated for the 3rd and 4th person.
Surcharges\Surcharge Depending of the length of stay there can be a
surcharge (e.g. 10 EUR per night surcharge if the guest
only stays in a place for two night)
OccupancyFrom Adults from
OccupancyTo Adults to
StayTo e.g. “5” – meaning the guest will pay the surcharge
when only staying up to 5-nights.
Value The amount of the surcharge (absolute value).

Basic Data For Service Providers 46 of 241


DESKLINE 3.0 STANDARD INTERFACE

Discounts\Discount Depending of the length of stay there can be a discount


(e.g. 10 EUR per night discount if the guest stays in a
place longer than five nights).
OccupancyFrom Adults from
OccupancyTo Adults to
StayFrom e.g. “5” – meaning the guest will receive a discount
when staying at least 5-nights.
Value The amount of the discount (absolute value).
ChildReductions Child reductions – other than in Deskline 2.0 – can be
created based on the ages of the children by the user
themselves.
ChildReductions It is possible for a price template that x-children can
FreeChildren stay in the room/product free of charge.
ChildReductions The maximum age of children that qualifiy for the free
FreeChildMaxAge stay.
ChildReduction Age from
AgeFrom
ChildReduction Age to
AgeTo
CalcRule Percentage/Fixed
Value Amount (either fixed amount to be paid or amount of
reduction from adult base price)
WithMeals When true, the reduction – when defined in
percentage - is also used for meals.
Example: The discount for children is 20% and the meal
surcharge for full board is € 10. If checked, then the full
board for this age-group is € 8, otherwise € 10.
UseBasePrice Defines, from which base the reduction is calculated.
If checked, the system takes the basic price, otherwise
calculates the child-reduction from the final price
where surcharges and discounts are already calculated.
PriceSplittings Used for “Stay 7, pay 6” offers.
PriceSplittings True/false if the PriceSplitting also affects calculated
FromDiscounts discounts.
PriceSplittings True/false if the PriceSplitting also affects calculated
FromMeals meals.
PriceSplittings True/false if the PriceSplitting also affects calculated
FromExtras extras.
PriceSplittings True/false if the PriceSplitting also affects calculated
FromChildPrice child reductions.
PriceSplitting Stay Nights the guest can stay in this offer.
PriceSplitting Pay Nights the guest has to pay for this offer.
SpecialPrices\ Special destination-created discounts such as Early
Booker or Last Minute or user-created discounts.
SpecialPrice From Days before arrival
SpecialPrice To Days until arrival
CalcRule Fixed/Percentage
Value Amount for the special price discount.
Type Type of SpecialPrice. Can be EarlyBooker, LastMinute
or Userdefined
SpecialPrice Names A SpecialPrice can also have translations
Meals\Meal While in Deskline 2.0 meals were defined on a service

Basic Data For Service Providers 47 of 241


DESKLINE 3.0 STANDARD INTERFACE

provider level, they are now defined on a product level


per price template.
MealCode Enumeration (NO, BB, HB, FB, 34, AI)
Value Amount (positive or negative, based on the default
meal).
Nights It is possible that a meal, such as all inclusive, is only
possible if the guest stays at least x-nights.
BedLinen The calculation for bed linen is usually done for
CalcRule/Value/Nights apartments, the rule can be Total/PerPerson/PerUnit
and it’s possible that bed linen is only offered if the
guests stay a certain amount of nights. When “0”, bed
linen is included in the price of the stay.
FinalCleaning The calculation for final cleaning is usually done for
apartments, the rule can be Total/PerPerson/PerUnit
and it’s possible that final cleaning is only offered if the
guests stay a certain amount of nights. When “0”, final
cleaning is included in the price of the stay.
Extras\Extra Extras can be defined by the user per template and can
also have translations.
CalcRule/Value/Nights The code is just an internal code defined by the user,
the name can have translations. The rule can be
Total/PerPerson/PerUnit and it’s possible that a user
defined extra is only offered if the guests stay a certain
amount of nights. It would also be possible to add
something for free (value = 0).
Extras Names A user-defined surcharge can also have translations

Products Arrival/Departure Details:

Many service providers use settings like “minimum length of stay” or only allow arrivals or departures on
certain weekdays. If this information is a must-have for your project, then you can use these arrival/departure
templates. The template logic is the same logic as for the price details: there is always a standard-template that
is valid if not overruled by other templates.

This is how settings look like in Deskline 3.0:

This translates to the following: if a search is done with an arrival date within 14 days the minimum length of
stay is 3 nights. If a search is done with an arrival date longer than 14 days the minimum length of stay is 7
nights. There are no arrival/departures possible on Mondays so this product would not show up in a search
with arrival and/or departure on a Monday.

These templates can be present but it’s also possible that a service provider did not enter them. In this case the
products can’t be found in a search.

Basic Data For Service Providers 48 of 241


DESKLINE 3.0 STANDARD INTERFACE

Response for ArrivalDepartureTemplates:

Response field Description Can be empty? Multiple?


ArrivalDepartureTemplates There can be multiple templates for a product but
it’s also possible that one product does not have
any templates at the moment of the request.
ArrivalDepartureTemplate ID of the template created by the user.
Id
ArrivalDepartureTemplate Date/Time when the template was last changed.
ChangeDate
ArrivalDepartureTemplate Internal Name of the template as defined by the
Name user, do not display to a guest, useful for
debugging.
ArrivalDepartureTemplate Only for the standard template if it should not be
ValidFrom available from today on but rather from a different
day on.
Periods Start/End The periods that the arrival and departure template
is assigned to. The periods for the default
(“Standard”) template will always be empty but for
other templates there will be one or more periods
listed. The End date is included in this case,
meaning, the template is still valid on the day that
is returned in the attribute “End”.
Conditions Can be empty, but usually one or more.
DaysUntilArrival The values that follow apply only to a specific
timeframe – days until arrival of the guest.
MinStay The minimum length of stay dependent on the
DaysUntilArrival value.
MaxStay Maximum length of stay can also be defined by a
service provider inside a template.
Interval Standard value is 1. This defines the possible
booking/search interval. Example: Apartment is
only bookable for 7 nights, not 5 or 8…
ArrivalDays True/false setting per weekday if arrivals are
possible on this day.
DepartureDays True/false setting per weekday if departures are
possible on this day.

Sales Rule Templates:

With the sales rules a service provider can define templates for different periods for settings about when a
product is bookable and when it can only be offered. In addition, there can be several exceptions (“Product A is
bookable for POS X but not for POS Y”). Based on the request that already includes the POS and the sales
channel the result will already be the correct setting for this sales channel.

This is how settings look like in Deskline 3.0:

Basic Data For Service Providers 49 of 241


DESKLINE 3.0 STANDARD INTERFACE

This translates to the following: if a search is done with the POS “Region XY” and the template is assigned to
the period from the search request, this product will not be bookable. With another POS except for “Region
XY” the product would be bookable.

These templates can be present but it’s also possible that a service provider did not enter them. In this case the
products can’t be found in a search. Its also possible that the service provider has entered an exception that
the product is not bookable or offerable for a certain salespoint or saleschannel, in this case the product or
atleast the serviceprovider (if all products are not min. offerable) should not be shown in the accommodation
list.

Response for Sales Rule Templates:

Response field Description Can be empty? Multiple?


SalesRuleTemplates There can be multiple templates for a product but it’s also
possible that one product does not have any templates at
the moment of the request.
SalesRuleTemplate Unique ID of the template.
Id
SalesRuleTemplate Date/Time when the template was last changed.
ChangeDate
SalesRuleTemplate Internal Name of the template as defined by the user, do not
Name display to a guest, useful for debugging.
SalesRuleTemplate Only for the standard template if it should not be available
ValidFrom from today on but rather from a different day on.
Periods Start/End The periods that the template is assigned to. The periods for
the default (“Standard”) template will always be empty but
for other templates there will be one or more periods listed.
The End date is included in this case, meaning, the template
is still valid on the day that is returned in the attribute “End”.
Offerable The minimum requirement for a product to be found in the
search is “offerable”.
Bookable True/False if a product is bookable for this POS/Sales
Channel.
BookOnRequest If a product is not directly bookable but only bookable on
request (overrules the “bookable only” setting)
UseTATO If a product can be booked by travel agencies / tour
operators.
DaysOfferStops When greater than 0, defines how many days before arrival
a product can’t be offered any longer.
DaysBookingStops When greater than 0, defines how many days before arrival
a product can’t be booked any longer.
DirectPayment When greater than 0, amount in percent how much pre-
PrePayment payment a service provider needs for a booking.
DirectPayment When greater than 0, amount of days after the booking until
PrePaymentUntil the pre-payment must be paid in order to guarantee the
booking.
DirectPayment When greater than 0, amount in percent how much final-
FinalPayment payment a service provider needs for a booking.
DirectPayment When greater than 0, amount of days before arrival until the
FinalPaymentUntil final-payment must be paid in order to guarantee the
booking.

Basic Data For Service Providers 50 of 241


DESKLINE 3.0 STANDARD INTERFACE

Gaps:

If a product has very strict arrival and departure conditions e.g. minimal length of stay 7 days, these settings are
valid for all availabilities. If a service provider now has a gap because a guest shortens his stay for 2 days then
he can enter a gap to be bookable for these 2 days with different conditions. Gaps are included into search for
availabilities.

Gaps have their own availabilities and conditions and can have their own prices or use the product prices.

This is how a gap looks like in Deskline 3.0:

Response for Gaps:

Response field Description Can be Multiple


empty? ?
Gaps There can be multiple gaps for a product but it’s also
possible that one product does not have any gaps at the
moment of the request.
Gap DateFrom/ DateTo Period in which gap is valid.
Gap Date/Time when the gap was last changed.
ChangeDate
Availabilities Includes all availability for the gap.
Availability Day/Count List of availabilities on specific day and count.
ArrivalDepartureTemplate See “Products Arrival/Departure Details”
s
PriceDetail If false PriceTemplates for this gap are included in the
UseProductPrice response, if true the price templates of the products
have to be used.
PriceTemplate Only if UseProductPrice is false. For details see
“Products Price Details”

Basic Data For Service Providers 51 of 241


DESKLINE 3.0 STANDARD INTERFACE

Cancellation and Payment Details:

The possibility if cancellation and payment policies can be defined by the service provider depends on the
settings of the data owner organization (tourist office). If these settings are missing, the organitsation settings
are valid.

Cancellation settings: A service provider can define for each product and date separately which cancellation
conditions he offers. He can choose between default (organization settings), free cancellation, no cancellation
and free cancellation until x days before arrival and afterwards cancellation fee depending on the days
between cancellation and arrival. So it is e.g. possible to offer free cancellation until 18:00 on arrival date. The
service provider also has to define the cancellation fee after the free cancellation deadline. It can be a
percentage of the whole stay or a percentage of the price for the first x nights.

Payment rules: A service provider can define for each product and date separately which payment rules he
offers. He can choose whether he wants prepayment or not and with invoice or credit card, if he wants credit
card guarantee or not, as well as optional guarantee or a prepayment to tourist office. Default and standard
setting is organization settings.

Important: Please be aware that in case of special prices (last minute, early booker, price splitting) there can be
different templates valid. Information included in CancellationPaymentInfo on service provider level.

This is how settings look like in Deskline 3.0:

This translates to the following: The cancellation is free until 7 days before arrival date, afterwards cancellation
fee is 50% of the price for the first 2 nights. If the guest does not appear until 18:00 on arrival date the
cancellation fee is 100 persent of the first 2 nights.

To guarantee the booking the service provider wants prepayment of 20% per credit card or per invoice within
the next 7 days. Invoice as a pre payment method is only possible until 10 days before arrival.

These templates can be present but it’s also possible that a service provider did not enter them or the tourist
board does not provide this possibility to its service providers.

Basic Data For Service Providers 52 of 241


DESKLINE 3.0 STANDARD INTERFACE

Response for CancellationPaymentTemplates:

Response field Description Can be empty? Multiple?


CancellationPaymentTemplate There can be multiple templates for a product but
s it’s also possible that one product does not have
any templates at the moment of the request.
CancellationPaymentTemplate Date/Time when the template was last changed.
ChangeDate
CancellationPaymentTemplate Only for the standard template if it should not be
ValidFrom available from today on but rather from a
different day on.
Periods Start/End The periods that the cancellation and payment
template is assigned to. The periods for the
default (“Standard”) template will always be
empty but for other templates there will be one
or more periods listed. The End date is included in
this case, meaning, the template is still valid on
the day that is returned in the attribute “End”.
CancellationInformation Enumeration true or false. False indicates that
UseOwnCancellationSettings organsiation settings are valid. True means the
service provider has his own individual settings.
CancellationInformation Enumeration true or false. False indicates that
FreeCancellation there is no free cancellation at all, true that there
is free cancellation until a specific date and time.
CancellationFee Element with cancellation fee information
depending on the days between canceellation and
arrival date which can be multiple.
CancellationFee In case of 0 the base for cancellation fees is the
CalculationBase whole stay. If >0 the amount of first days as base
for cancellation fee. E.g. cancellation fee is 10% of
whole stay or 50% of the first 2 days.
CancellationFee Percentage Percentage value for cancellation fee.
CancellationFee DaysUntil Days before arrival until the cancellation is for
free.
CancellationFee TimeUntil Time until the cancellation is free.
PaymentInformation Enumeration true or false. False indicates that
UseOwnPaymentSettings organsiation settings are valid. True means the
service provider has his own individual settings.
PaymentInformation Enumeration:
PaymentType  Default: Organisation settings
 NoPayment: No prepayment required at all
 Guarantee: Product requires guarantee
 OptionalGuarantee: Guest choice if guarantee
is given or not, to guarantee the room also in
case of arrival after 18:00
 PrePayment: pre payment to service provider
is required
 OrganisationPrePayment: pre payment to
tourist office is required
PaymentInformation Percantage value to calculate the pre payment
PrePaymentPercentage amount
PaymentMethods Day before arrival the payment method incoice is
InvoicePossibleDays possible (afterwards organization default)
PaymentMethods Days before arrival in case of final payment via
FinalPayment invoice.
Basic Data For Service Providers 53 of 241
DESKLINE 3.0 STANDARD INTERFACE

PaymentMethods In case of pre payment via invoice to calculate the


PrePaymentUntil due date of prepayment after day of booking.
PaymentMethods Invoice, Defines which payment methods are valid. In case
CreditCard, ELV, of prepayment to service provider via CreditCard
Sofortueberweisung, iDeal, only a credit card guarantee has to be given, the
PayPal service provider then has the possibility to get the
amount to prepay from the guest’s credit card.

Basic Data For Service Providers 54 of 241


DESKLINE 3.0 STANDARD INTERFACE

Additional Services:
Response field Description Can be empty? Multiple?
Service ID The ID of the service
ChangeDate Date/time indicator when the item was last changed.
Name Translations of service name
Order Order of the services of a service provider
UseAvailability Does this service use availabilities or not (1…true,
0…false)
LastAvailabilityChange Date and Time when the availabilities where changed
the last time for this service (either through Deskline or
the WebClient).
MaxAvailability Is there a top limit to the availabilities? E.g. max. 3 units
available?
Code Service Code, refer to KeyValues function
“ServiceCodes”.

Important:
The first 2 characters always reflect the ServiceCodes
ServiceType.
The next two 2 characters always reflect the
ServiceCodes CodeType “Sanitary”.
The rest of the characters always reflect the
ServiceCodes CodeType “AdditionalInfo”.

Example: SUYTNOSMO
SU = Suite
YT = shower and both, toilet
NOSMO = no smoker
Dates Container for a collection of Date-Elements that this
service is valid on. If empty it is always valid.
StartTimes Container for a collection of StartTime-Elements that
this service is valid on. Including Time and a true/false
flag for every day of the week (Mon, Tue, Wed, Thu, Fri,
Sat, Sun)
Durations Container for a collection of Duration-Elements that
define the intervals that a service is available for.
Duration Type can be Minute/Hour/Day/None.
Active True/false value if the service is set to active or not. By
default, only active services are returned.
Documents Documents can be images, videos, PDF-files, etc. For
each document, the URL will be provided the image can
then be downloaded into an external database. It is
also possible that documents have different names in
different languages. In addition there is also a copyright
note for each document if necessary. Each document
can either have a From-To timeframe (only day/month,
not year) or can be set to be shown as “always” in
which case From-To is send as “101”-“1231” in the
element. Documents can also be set to only be
available for different output systems such as: local
(Deskline 3.0 backend), internet presentation,
Informator or catalog productions. When requesting
basic data the Systems-Attribute must already be
provided to filter only internet-documents for example.
The extension is part of the response.
Basic Data For Service Providers 55 of 241
DESKLINE 3.0 STANDARD INTERFACE

Links There is a URL for each address (typically the


homepage) but the service providers have the option to
add more links to external sites or external documents.
Facilities Each service can have a lot of different facilities. In the
response, only the ID and value are sent. The
translations are available through the Key Values
function. The value is optional as well and is used e.g.
for the service facility information “amount
bathrooms” – i.e. “amount bathrooms: 2”.
If there are any IDs present that are not provided in the
Key Values function it is because of items that were
created by the customers themselves and therefore are
not global and not available in the Key Values.
Descriptions Descriptions in various languages. Each description can
either have a From-To timeframe (only day/month, not
year) or can be set to be shown as “always” in which
case From-To is send as “101”-“1231” in the element.
Line-breaks are not converted to HTML-line-breaks, the
description will be returned as entered in the system.
Descriptions can also be set to only be available for
different output systems such as: local (Deskline 3.0
backend), internet presentation, Informator or catalog
productions. When requesting basic data the Systems-
Attribute must already be provided to filter only
internet-descriptions for example.
Availabilities A collection of <Availability> Elements that consist of
the day and the count of available rooms for this day.

Special cases:
 Count -1002: Closed
 Count -1001: Own use by service provider
The special cases can be interpreted as 0 (not available)
if no distinction is made between not
available/closed/own use.
Missing days in between the requested start/end dates
are not available (availability 0).
<AdditionalProducts>- Products are based on services and there can be more
collection than one product for a service.

Basic Data For Service Providers 56 of 241


DESKLINE 3.0 STANDARD INTERFACE

Additional Products:

Response for Details:

Response field Description Can be empty? Multiple?


Product ID ID of the product
Product PackageOnly Indicates if this assitional product can only be booked
inside a destination package or not (Enumeration:
true/false)
Product ChangeDate Date/time indicator when the item was last changed.
Details  This attribute shows if the additional service product is
@FreeBookable bookable as free. Enumeration: true/false
SearchCode Code for a search, can be defined by the customer.
SortOrder Products inside a service can be ordered
Active True/false value if the product is set to active or not. By
default, only active products are returned.
Product Name Translations of the product name
HolidayThemes e.g. Weekend, Wedding, Family, etc..
Documents Documents can be images, videos, PDF-files, etc. For
each document, the URL will be provided the image can
then be downloaded into an external database. It is
also possible that documents have different names in
different languages. In addition there is also a copyright
note for each document if necessary. Each document
can either have a From-To timeframe (only day/month,
not year) or can be set to be shown as “always” in
which case From-To is send as “101”-“1231” in the
element. Documents can also be set to only be
available for different output systems such as: local
(Deskline 3.0 backend), internet presentation,
Informator or catalog productions (LTIC). When
requesting basic data the Systems-Attribute must
already be provided to filter only internet-documents
for example. The extension is part of the response.
Links There is a URL for each address (typically the
homepage) but there is the option to add more links to
external sites or external documents.
Descriptions Descriptions in various languages. Each description can
either have a From-To timeframe (only day/month, not
year) or can be set to be shown as “always” in which
case From-To is send as “101”-“1231” in the element.
Line-breaks are not converted to HTML-line-breaks, the
description will be returned as entered in the system.
Descriptions can also be set to only be available for
different output systems such as: local (Deskline 3.0
backend), internet presentation, Informator or catalog
productions. When requesting basic data the Systems-
Attribute must already be provided to filter only
internet-descriptions for example.

Basic Data For Service Providers 57 of 241


DESKLINE 3.0 STANDARD INTERFACE

Response for PriceDetails:

Response field Description Can be empty? Multiple?


PriceDetails Container element for detailed price information.
Attribut OrgPaymentRequired marks the product if it
can only be booked with PaymentType
OrganisationPayment (1 means organization payment
reuired, 0 means other payment types possible,
depending on payment settings)
PriceTemplates There can be multiple price templates for a product but
it’s also possible that one product does not have any
prices at the moment of the request.
PriceTemplate ID of the price template created by the user.
Id
PriceTemplate Date/Time when the price template was last changed.
ChangeDate
PriceTemplate Internal Name of the price template as defined by the
Name user, do not display to a guest, useful for debugging.
PriceTemplate Only for the standard template if it should not be
ValidFrom available from today on but rather from a different day
on.
PriceTemplate A user can define if this price template reflects the
IsBestPrice “best price” possible for this product. True/false.
Periods Start/End The periods that the price template is assigned to. The
periods for the default (“Standard”) template will
always be empty but for other templates there will be
one or more periods listed. The End date is included in
this case, meaning, the template is still valid on the day
that is returned in the attribute “End”.
Prices Additional services can be set up to be sold in different
PriceValue units: a ticket for a day or an entrance for one or two
DurationUnits hours. This is defined in the product details. So if the
duration unit is “hour” then the price can be different
for 1 hour or two hours.
Prices The price for the defined duration or units.
PriceValue Price
Response for SalesRulesTemplates:

Response field Description Can be empty? Multiple?


SalesRuleTemplates There can be multiple templates for a product but it’s also
possible that one product does not have any templates at
the moment of the request.
SalesRuleTemplate ID of the template created by the user.
Id
SalesRuleTemplate Date/Time when the template was last changed.
ChangeDate
SalesRuleTemplate Internal Name of the template as defined by the user, do not
Name display to a guest, useful for debugging.
SalesRuleTemplate Only for the standard template if it should not be available
ValidFrom from today on but rather from a different day on.
Periods Start/End The periods that the template is assigned to. The periods for
the default (“Standard”) template will always be empty but
for other templates there will be one or more periods listed.
The End date is included in this case, meaning, the template
is still valid on the day that is returned in the attribute “End”.

Basic Data For Service Providers 58 of 241


DESKLINE 3.0 STANDARD INTERFACE

Offerable The minimum requirement for a product to be found in the


search is “offerable”.
Bookable True/False if a product is bookable for this POS/Sales
Channel.
BookOnRequest If a product is not directly bookable but only bookable on
request (overrules the “bookable only” setting)
UseTATO If a product can be booked by travel agencies / tour
operators.
DaysOfferStops When greater than 0, defines how many days before arrival
a product can’t be offered any longer.
DaysBookingStops When greater than 0, defines how many days before arrival
a product can’t be booked any longer.
DirectPayment When greater than 0, amount in percent how much pre-
PrePayment payment a service provider needs for a booking.
DirectPayment When greater than 0, amount of days after the booking until
PrePaymentUntil the pre-payment must be paid in order to guarantee the
booking.
DirectPayment When greater than 0, amount in percent how much final-
FinalPayment payment a service provider needs for a booking.
DirectPayment When greater than 0, amount of days before arrival until the
FinalPaymentUntil final-payment must be paid in order to guarantee the
booking.

Full example for one service provider, type accommodation:

<?xml version="1.0" encoding="UTF-8"?>


<FeratelDsiRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
Status="0" Message="OK" xmlns="http://interface.deskline.net/DSI/XSD">
<Result Index="1">
<ServiceProviders>
<ServiceProvider Id="dc1defe3-999a-4097-a5bf-7bd86a14e28a" ChangeDate="2012-02-01T10:17:00">
<Details>
<Name>Simotel</Name>
<Town>5c7e1d37-0060-4811-a996-a8b36094d01e</Town>
<District>65f056cd-4bc9-4272-a1d6-3fadf7aac9d9</District>
<Code>SIM22</Code>
<Type>Accommodation</Type>
<Priority>99</Priority>
<Rooms>6</Rooms>
<Beds>1</Beds>
<Position Latitude="46.6188492" Longitude="13.82479" />
<Stars Id="EBF4EE39-F7E0-45FE-A410-46D75C3B769C" />
<Categories>
<Item Id="AB4F2086-F06D-4DAC-8B99-09EDA5577C67" />
</Categories>
<Classifications>
<Item Id="50A3AF54-33DB-4612-8848-B9CF0A65C558" />
<Item Id="89C1A7D7-0222-4DEE-AA35-D6A01496B0BC" />
</Classifications>
<MarketingGroups>
<Item Id="9B3F881D-D73F-4772-AD7B-99DCAE16BB59" />
</MarketingGroups>
<Active>true</Active>
<CreditCards>
<CreditCard Name="VISA" />
<CreditCard Name="American Express" />
<CreditCard Name="MasterCard" />
</CreditCards>
<GridSquare />
<PlanNumber />

Basic Data For Service Providers 59 of 241


DESKLINE 3.0 STANDARD INTERFACE

<DBCode>FRT</DBCode>
<Bookable>true</Bookable>
<BankAccounts>
<Bank Id="6828b606-9324-4426-94ff-05470675a351" CountryCode="" IBAN="at1234567890" Account="123456789" />
</BankAccounts>
<CurrencyCode>EUR</CurrencyCode>
</Details>
<Documents>
<Document Id="a5f93456-418b-49d3-b35b-4b3f4f0b3fbf" Type="ServiceProvider" Class="Image" Systems="L T I C"
Order="1" ShowFrom="101" ShowTo="1231" Copyright="" Extension="jpg" Size="548" ChangeDate="2011-06-07T18:18:00">
<Names>
<Translation Language="de">Hotelansicht1</Translation>
<Translation Language="en">Hotelansicht1</Translation>
</Names>
<URL>http://interfacetest.deskline.net/Handlers/Document?code=FRT&amp;id=a5f93456-418b-49d3-b35b-
4b3f4f0b3fbf</URL>
</Document>
<Document Id="ac86a9a8-9055-41a4-941d-c05369daba06" Type="ServiceProviderLogo" Class="Image" Systems="L T I C"
Order="1" ShowFrom="101" ShowTo="1231" Copyright="" Extension="jpg" Size="581" ChangeDate="2010-11-03T15:27:00">
<Names>
<Translation Language="de">Logo</Translation>
<Translation Language="en">Logo</Translation>
</Names>
<URL>http://interfacetest.deskline.net/Handlers/Document?code=FRT&amp;id=ac86a9a8-9055-41a4-941d-
c05369daba06</URL>
</Document>
<Descriptions>
<Description Id="9039deb1-2082-4758-bb8b-4f00ffb8c9b2" Type="ServiceProviderArrivalVoucher" Language="de"
Systems="L T I C" ShowFrom="101" ShowTo="1231" ChangeDate="2011-09-01T15:21:00">ankunft</Description>
<Description Id="3b44d9ab-53ec-448f-a473-5bbbef80d633" Type="ServiceProviderDescription" Language="en"
Systems="L T I C" ShowFrom="101" ShowTo="1231" ChangeDate="2012-01-16T10:22:00">
Very nice hotel....
- nice rooms
- nice restaurant
- nice buffet
- nice garden
- nice bar
- nice pool
</Description>
</Descriptions>
<Links>
<Link Id="dd40cbc1-50fd-4add-a2e3-405d6fc96121" Name="Homepage" URL="http://" ChangeDate="2011-02-
08T11:23:00" Type="0" Order="1" />
</Links>
<Facilities>
<Facility Id="8f94d1ef-bfae-485a-9df6-837da241728f" Value="1" />
<Facility Id="962d8aa4-7501-4e2f-9ee5-455ab1eb579d" Value="3" />
</Facilities>
<Addresses>
<Address Type="Object" ChangeDate="2012-02-01T10:24:00" Id="b75a83ca-de68-453a-acb3-c5567a4468dd">
<Company>Feratel</Company>
<Title>Frau</Title>
<FirstName>Simone</FirstName>
<LastName>Schanitz</LastName>
<AddressLine1>Moritschstraße 2/IV</AddressLine1>
<AddressLine2 />
<Country>AT</Country>
<ZipCode>9500</ZipCode>
<Town>Villach</Town>
<Email>[email protected]</Email>
<Fax />
<URL>http://feratel.com</URL>
<Phone>(0043) 4242 424242</Phone>
<Mobile />
</Address>
<Address Type="Owner" ChangeDate="2012-02-01T10:24:00" Id="b75a83ca-de68-453a-acb3-c5567a4468dd">
<Company>Feratel</Company>
<Title>Frau</Title>
<FirstName>Simone</FirstName>

Basic Data For Service Providers 60 of 241


DESKLINE 3.0 STANDARD INTERFACE

<LastName>Schanitz</LastName>
<AddressLine1>Moritschstraße 2/IV</AddressLine1>
<AddressLine2 />
<Country>AT</Country>
<ZipCode>9500</ZipCode>
<Town>Villach</Town>
<Email>[email protected]</Email>
<Fax />
<URL>http://feratel.com</URL>
<Phone>(0043) 4242 424242</Phone>
<Mobile />
</Address>
<Address Type="LandLord" ChangeDate="2012-02-01T10:24:00" Id="b75a83ca-de68-453a-acb3-c5567a4468dd">
<Company>Feratel</Company>
<Title>Frau</Title>
<FirstName>Simone</FirstName>
<LastName>Schanitz</LastName>
<AddressLine1>Moritschstraße 2/IV</AddressLine1>
<AddressLine2 />
<Country>AT</Country>
<ZipCode>9500</ZipCode>
<Town>Villach</Town>
<Email>[email protected]</Email>
<Fax />
<URL>http://feratel.com</URL>
<Phone>(0043) 4242 424242</Phone>
<Mobile />
</Address>
<Address Type="Keyholder" ChangeDate="2012-02-01T10:24:00" Id="b75a83ca-de68-453a-acb3-c5567a4468dd">
<Company>Feratel</Company>
<Title>Frau</Title>
<FirstName>Simone</FirstName>
<LastName>Schanitz</LastName>
<AddressLine1>Moritschstraße 2/IV</AddressLine1>
<AddressLine2 />
<Country>AT</Country>
<ZipCode>9500</ZipCode>
<Town>Villach</Town>
<Email>[email protected]</Email>
<Fax />
<URL>http://feratel.com</URL>
<Phone>(0043) 4242 424242</Phone>
<Mobile />
</Address>
</Addresses>
<CustomAttributes ChangeDate="2011-06-07T18:18:00">
<CustomAttribute Value="43" Id="ed7a6734-f08f-4df7-9bec-ab5f7c94ad9c" />
<CustomAttribute Value="12345" Id="b3a21b45-3139-4978-aed7-a023aa69cdb5" />
</CustomAttributes>
<HotSpots ChangeDate="2011-06-07T18:18:00">
<HotSpot Id="216e575f-99e2-4340-937f-4728259afc33" Distance="4.0" />
<HotSpot Id="6953b575-88d9-469f-a80b-d6cec6fb51df" Distance="3.0" />
</HotSpots>
<QualityDetails>
<ContentScore>33.4</ContentScore>
<BestPrice>1</BestPrice>
<AvailUpdCheck>0</AvailUpdCheck>
</QualityDetails>
<HousePackageMasters>
<HousePackageMaster Id="eadebcd7-d5bd-4b62-a450-1498883cc99e" ChangeDate="2015-09-28T09:35:00">
<Details>
<Name>
<Translation Language="de">Test Sommer Bike Pauschale</Translation>
<Translation Language="en">Test Sommer Bike Pauschale</Translation>
</Name>
<Priority>1</Priority>
<HolidayThemes>
<Item Id="E60B1D44-8704-47C1-8CE3-4CE641D673B9" />
<Item Id="6F5D7410-2888-4B17-B497-F881321ADA74" />

Basic Data For Service Providers 61 of 241


DESKLINE 3.0 STANDARD INTERFACE

<Item Id="BBBEBC26-8375-4E04-A9C1-C1F477489156" />


<Item Id="6A78542A-B24B-44B0-A9DF-0203CBB8F0E2" />
<Item Id="EFDF7EDF-B161-4D5F-B2C9-C21DF98397E5" />
<Item Id="E94074C0-184E-41C2-A74A-F9BBB9366747" />
</HolidayThemes>
<Active>true</Active>
<DBCode>FRT</DBCode>
<ValidDates Type="Period">
<ValidDate From="2016-04-28" To="2016-10-01" />
</ValidDates>
<Owner>FERATEL</Owner>
</Details>
<Descriptions>
<Description Id="e069c674-c71f-4397-83d6-208885b11a4b" Type="Package" Language="de" Systems="L T I C"
ShowFrom="101" ShowTo="1231" ChangeDate="2015-09-28T09:37:00">Mit mehr als 500 km hat die Region in und um Flachau
ein variantenreiches und gut ausgeschildertes Angebot an Mountainbikerouten. Bewaldete Bergrücken, felsige Gipfel und
weite Täler sowie die Enns, die im Talschluss von Flachau entspringt, prägen das Landschaftsbild. Freut euch also auf jede
Menge abwechslungsreiche Touren mit vielen unterschiedlichen Runden.</Description>
</Descriptions>
<Documents>
<Document Id="f46bc80d-774a-4426-8aae-9efb7a0379e1" Type="Package" Class="Image" Systems="L T I C" Order="1"
ShowFrom="101" ShowTo="1231" Copyright="" Extension="jpg" Size="127" ChangeDate="2015-09-28T09:35:00"
Width="1200" Height="798">
<Names>
<Translation Language="de">Sommer</Translation>
<Translation Language="en">Sommer</Translation>
</Names>
<URL>http://restest.deskline.net/images/FRT/1/f46bc80d-774a-4426-8aae-9efb7a0379e1/99/image.jpg</URL>
</Document>
</Documents>
<Links>
<Link Id="a5673d9a-37d0-4d81-98a9-89f426e1b573" Name="Test" URL="http://feratel.com" ChangeDate="2015-09-
28T09:37:00" Type="0" Order="1">
<Names>
<Translation Language="de">Test</Translation>
<Translation Language="en">Test</Translation>
</Names>
</Link>
</Links>
<AssignedProducts>
<AssignedProduct ProductId="71aa2253-bed7-4cba-a0f3-3b879d676d3d" />
<AssignedProduct ProductId="f5b298c7-8d2f-4a29-94c3-56c6a3d2606a" />
<AssignedProduct ProductId="df0d9e42-4035-4fc1-b477-77d076f2e8df" />
<AssignedProduct ProductId="eb06579a-0c88-427f-ba37-953a89c0f0fc" />
</AssignedProducts>
</HousePackageMaster>
</HousePackageMasters>
<Services>
<Service Id="6c6a8447-4877-45be-93b5-e2fcfd9f1f68" ChangeDate="2011-06-09T13:52:00">
<Details>
<Type>Accommodation</Type>
<Rooms>1.0</Rooms>
<Bedrooms>1</Bedrooms>
<Size>25</Size>
<UseAvailability>1</UseAvailability>
<LastAvailabilityChange>2012-01-31T13:26:00</LastAvailabilityChange>
<MaxAvailability>33</MaxAvailability>
<Order>1</Order>
<Name>
<Translation Language="de">Doppelzimmer, Bad, WC, Balkon</Translation>
<Translation Language="en">Double room, bath, toilet, balcony</Translation>
</Name>
<Code>DRBTBAL</Code>
<Active>true</Active>
</Details>
<Descriptions>
<Description Id="f2e5d8a3-f71c-4167-b3f4-030282d50368" Type="ServiceDescription" Language="de" Systems="L T I
C" ShowFrom="101" ShowTo="1231" ChangeDate="2011-02-24T15:55:00">deutsch leistung dz</Description>
<Description Id="273943f4-da82-416c-8b8e-cdbbeaaaf9b3" Type="ServiceDescription" Language="en" Systems="L T I

Basic Data For Service Providers 62 of 241


DESKLINE 3.0 STANDARD INTERFACE

C" ShowFrom="101" ShowTo="1231" ChangeDate="2011-02-24T15:55:00">englisch leistung dz</Description>


</Descriptions>
<Availabilities ChangeDate="2012-01-31T13:26:00">
<Availability Day="2012-02-03" Count="99" />
<Availability Day="2012-02-04" Count="99" />
<Availability Day="2012-02-05" Count="99" />
<Availability Day="2012-02-06" Count="99" />
<Availability Day="2012-02-07" Count="99" />
<Availability Day="2012-02-08" Count="99" />
<Availability Day="2012-02-09" Count="2" />
<Availability Day="2012-02-10" Count="2" />
<Availability Day="2012-02-11" Count="3" />
<Availability Day="2012-02-12" Count="3" />
<Availability Day="2012-02-13" Count="3" />
<Availability Day="2012-02-14" Count="3" />
<Availability Day="2012-02-15" Count="3" />
<Availability Day="2012-02-16" Count="3" />
</Availabilities>
<Products>
<Product Id="90ea4361-af82-466e-b759-9b448ed95826" ChangeDate="2012-01-04T17:12:00">
<Details>
<ProductType>Accommodation</ProductType>
<AccommodationType>HotelRoom</AccommodationType>
<SearchCode>TEST</SearchCode>
<Order>1</Order>
<Occupancy>
<Beds Min="1" Max="3" />
<Adults Standard="2" Min="1" Max="3" />
<Children Min="0" Max="3" />
<MinFullPayer>0</MinFullPayer>
</Occupancy>
<Name>
<Translation Language="de">Doppelzimmer, Nichtraucher</Translation>
<Translation Language="en">Doppelzimmer, Nichtraucher</Translation>
</Name>
<ValidDates Type="Always" />
<Active>true</Active>
</Details>
<PriceDetail InclVT="0" FromTo="0" Rule="PerPerson" Nights="0" OrgPaymentRequired="0">
<PriceTemplates>
<PriceTemplate Id="19f09daf-73cd-4a59-a8c8-0c664381dbaa" Name="1:100-2:90-3:80" ValidFrom="2012-01-12"
IsBestPrice="false" DefaultMealCode="BB" ChangeDate="2012-01-12T15:35:00">
<Periods>
<Period Start="2012-02-03" End="2012-02-11" />
</Periods>
<Prices>
<BasePrices>
<BasePrice OccupancyFrom="1" OccupancyTo="1" Price="100" AdditionalBed="0" />
<BasePrice OccupancyFrom="2" OccupancyTo="2" Price="90" AdditionalBed="0" />
<BasePrice OccupancyFrom="3" OccupancyTo="3" Price="80" AdditionalBed="0" />
</BasePrices>
<Surcharges>
<Surcharge OccupancyFrom="1" OccupancyTo="1" StayTo="3" Value="10" />
<Surcharge OccupancyFrom="1" OccupancyTo="1" StayTo="3" Value="10" />
<Surcharge OccupancyFrom="2" OccupancyTo="2" StayTo="3" Value="9" />
<Surcharge OccupancyFrom="2" OccupancyTo="2" StayTo="3" Value="9" />
<Surcharge OccupancyFrom="3" OccupancyTo="3" StayTo="3" Value="8" />
<Surcharge OccupancyFrom="3" OccupancyTo="3" StayTo="3" Value="8" />
</Surcharges>
<Discounts>
<Discount OccupancyFrom="1" OccupancyTo="1" StayFrom="10" Value="-10" />
<Discount OccupancyFrom="1" OccupancyTo="1" StayFrom="10" Value="-10" />
<Discount OccupancyFrom="2" OccupancyTo="2" StayFrom="10" Value="-9" />
<Discount OccupancyFrom="2" OccupancyTo="2" StayFrom="10" Value="-9" />
<Discount OccupancyFrom="3" OccupancyTo="3" StayFrom="10" Value="-8" />
<Discount OccupancyFrom="3" OccupancyTo="3" StayFrom="10" Value="-8" />
</Discounts>
</Prices>
<ChildReductions FreeChildren="0" FreeChildMaxAge="7">

Basic Data For Service Providers 63 of 241


DESKLINE 3.0 STANDARD INTERFACE

<ChildReduction AgeFrom="0" AgeTo="3" CalcRule="Fixed" Value="100" WithMeals="false" UseBasePrice="true"


/>
<ChildReduction AgeFrom="4" AgeTo="7" CalcRule="Fixed" Value="50" WithMeals="false" UseBasePrice="true"
/>
<ChildReduction AgeFrom="8" AgeTo="12" CalcRule="Fixed" Value="20" WithMeals="false" UseBasePrice="true"
/>
</ChildReductions>
<PriceSplittings FromDiscounts="true" FromMeals="true" FromExtras="true" FromChildPrice="true" />
<SpecialPrices FromDiscounts="true" FromMeals="true" FromExtras="true" FromChildPrice="true">
<SpecialPrice From="30" To="999" CalcRule="Percentage" Value="10" Type="EarlyBooker">
<Names>
<Translation Language="de">Frühbucher </Translation>
<Translation Language="en">Frühbucher </Translation>
</Names>
</SpecialPrice>
</SpecialPrices>
<Meals>
<Meal MealCode="HB" Value="10" Nights="1" />
<Meal MealCode="BB" Value="0" Nights="1" />
</Meals>
<BedLinen CalcRule="Total" Value="12" Nights="1" />
<FinalCleaning CalcRule="Total" Value="13" Nights="1" />
<Extras>
<Extra CalcRule="Total" Code="TE" Value="14" Nights="1">
<Names>
<Translation Language="de" />
<Translation Language="en">TEST</Translation>
</Names>
</Extra>
<Extra CalcRule="Total" Code="BU" Value="24" Nights="1">
<Names>
<Translation Language="de" />
<Translation Language="en">BUBU</Translation>
</Names>
</Extra>
</Extras>
</PriceTemplate>
<PriceTemplate Id="7444a17a-5151-4f68-b4ab-47a827d04cbf" Name="STANDARD" ValidFrom="2010-11-08"
IsBestPrice="true" DefaultMealCode="BB" ChangeDate="2011-12-20T11:49:00">
<Periods />
<Prices>
<BasePrices>
<BasePrice OccupancyFrom="1" OccupancyTo="1" Price="10" AdditionalBed="0" />
<BasePrice OccupancyFrom="2" OccupancyTo="2" Price="10" AdditionalBed="0" />
<BasePrice OccupancyFrom="3" OccupancyTo="3" Price="10" AdditionalBed="0" />
</BasePrices>
<Surcharges />
<Discounts />
</Prices>
<ChildReductions FreeChildren="0" FreeChildMaxAge="7">
<ChildReduction AgeFrom="0" AgeTo="3" CalcRule="Fixed" Value="100" WithMeals="false" UseBasePrice="true"
/>
<ChildReduction AgeFrom="4" AgeTo="7" CalcRule="Fixed" Value="50" WithMeals="false" UseBasePrice="true"
/>
<ChildReduction AgeFrom="8" AgeTo="12" CalcRule="Fixed" Value="20" WithMeals="false" UseBasePrice="true"
/>
</ChildReductions>
<PriceSplittings FromDiscounts="true" FromMeals="true" FromExtras="true" FromChildPrice="true" />
<SpecialPrices FromDiscounts="true" FromMeals="true" FromExtras="true" FromChildPrice="true">
<SpecialPrice From="30" To="999" CalcRule="Percentage" Value="10">
<Names>
<Translation Language="de">Frühbucher </Translation>
<Translation Language="en">Frühbucher </Translation>
</Names>
</SpecialPrice>
</SpecialPrices>
<Meals>
<Meal MealCode="HB" Value="10" Nights="1" />
<Meal MealCode="BB" Value="0" Nights="1" />

Basic Data For Service Providers 64 of 241


DESKLINE 3.0 STANDARD INTERFACE

</Meals>
<BedLinen CalcRule="Total" Value="12" Nights="1" />
<FinalCleaning CalcRule="Total" Value="13" Nights="1" />
<Extras>
<Extra CalcRule="Total" Code="BU" Value="24" Nights="1">
<Names>
<Translation Language="de" />
<Translation Language="en">BUBU</Translation>
</Names>
</Extra>
<Extra CalcRule="Total" Code="TE" Value="14" Nights="1">
<Names>
<Translation Language="de" />
<Translation Language="en">TEST</Translation>
</Names>
</Extra>
</Extras>
</PriceTemplate>
</PriceTemplates>
</PriceDetail>
<ArrivalDepartureTemplates>
<ArrivalDepartureTemplate Id="f821900d-f1a6-4527-ae69-e43af4491453" Name="STANDARD" ValidFrom="2010-11-
08" ChangeDate="2011-07-28T18:06:00">
<Conditions>
<Condition>
<DaysUntilArrival>9999</DaysUntilArrival>
<MinStay>1</MinStay>
<MaxStay>999</MaxStay>
<Interval>1</Interval>
<ArrivalDays Mon="true" Tue="true" Wed="true" Thu="true" Fri="true" Sat="true" Sun="true" />
<DepartureDays Mon="true" Tue="true" Wed="true" Thu="true" Fri="true" Sat="true" Sun="true" />
</Condition>
</Conditions>
<Periods />
</ArrivalDepartureTemplate>
</ArrivalDepartureTemplates>
<SalesRuleTemplates>
<SalesRuleTemplate Name="STANDARD" ValidFrom="2010-11-08" ChangeDate="2011-06-07T18:18:00">
<Periods />
<Offerable>true</Offerable>
<Bookable>true</Bookable>
<BookOnRequest>false</BookOnRequest>
<UseTATO>false</UseTATO>
<DaysOfferStops>0</DaysOfferStops>
<DaysBookingStops>0</DaysBookingStops>
<DirectPayment>
<PrePayment>0</PrePayment>
<PrePaymentUntil>0</PrePaymentUntil>
<FinalPayment>0</FinalPayment>
<UsePayment>0</UsePayment>
</DirectPayment>
</SalesRuleTemplate>
</SalesRuleTemplates>
<Availabilities OwnAvailabilities="false" />
<CancellationPaymentTemplates>
<CancellationPaymentTemplate ValidFrom="1980-01-01" ChangeDate="2013-09-03T15:34:00">
<Periods>
<Period Start="2013-10-07" End="2013-11-06" />
</Periods>
<CancellationInformation UseOwnCancellationSettings="true" FreeCancellation="true" />
<CancellationFee CalculationBase="3" Percentage="5.00" DaysUntil="5" TimeUntil="18:00" />
<CancellationFee CalculationBase="3" Percentage="10.00" DaysUntil="2" TimeUntil="18:00" />

<PaymentInformation UseOwnPaymentSettings="true" PaymentType="PrePayment"


PrePaymentPercentage="10.00" />
<PaymentMethods InvoicePossibleDays="14" PrePaymentUntil="7" Invoice="false" CreditCard="false" ELV="false"
PayPal="false" />
</CancellationPaymentTemplate>
</CancellationPaymentTemplates>

Basic Data For Service Providers 65 of 241


DESKLINE 3.0 STANDARD INTERFACE

</Product>
</Products>
</Service>
</Services>
<RatingsAverage>
<RatingAverage Type="Hotel" Value="3.0" Count="4" Satisfaction="2,0" Recommended="3">
<Ratings>
<Rating Points="3.4" Satisfaction="4" Recommended="1" Nickname="Testnick" VisitorTypeID="4678a819-71ca-4ea8-
b1b5-3ff078396b58" Id="2d9bc603-1fd3-4a80-ba80-1613735f3fce" ChangeDate="2011-12-01T11:08:00" Active="true"
CreateDate="2011-12-01T11:08:00" >
<UserComment>es war schön</UserComment>
<ParentComment />
<Answer QuestionID="8218f75b-4ed1-482f-aa44-0b6b37ef389c" Value="4" />
<Answer QuestionID="127b3703-e51e-4252-a62c-64a67491a238" Value="5" />
<Answer QuestionID="8450d77d-c15e-4ec0-962c-c50e054beff3" Value="3" />
<Answer QuestionID="212d35e2-1e1c-4725-bfa3-e07f21988708" Value="1" />
<Answer QuestionID="dc7f1005-a743-4581-a9f6-2be05a5f923f" Value="4" />
</Rating>
<Rating Points="5.0" Satisfaction="5" Recommended="1" Nickname="monamunki" VisitorTypeID="4678a819-71ca-
4ea8-b1b5-3ff078396b58" Id="a7d963e5-d391-4497-88bf-69c145e666ef" ChangeDate="2011-12-22T07:06:00" Active="true"
CreateDate="2011-12-01T11:08:00" >
<UserComment>Supertoll!</UserComment>
<ParentComment />
<Answer QuestionID="880addb5-3881-476f-988b-6487f399fb6b" Value="5" />
<Answer QuestionID="212d35e2-1e1c-4725-bfa3-e07f21988708" Value="5" />
<Answer QuestionID="91a4b6ad-311e-4410-91e8-19077089eb55" Value="5" />
<Answer QuestionID="4236876b-a058-4390-8621-630fe960c397" Value="5" />
<Answer QuestionID="127b3703-e51e-4252-a62c-64a67491a238" Value="5" />
<Answer QuestionID="b5884357-629b-4d1e-a31d-9ad30230a691" Value="5" />
<Answer QuestionID="da3fca5a-5323-43e8-96a0-0d36b72369fd" Value="5" />
<Answer QuestionID="a8746bcb-7ed2-48cf-aadb-ab9ea49adc10" Value="5" />
<Answer QuestionID="e3753956-165a-466f-91c5-9251ef79c959" Value="5" />
<Answer QuestionID="73a8dbd8-4a88-4419-9092-e6262d09ee97" Value="5" />
<Answer QuestionID="155f3d8c-336c-49fe-951f-86a7d851e852" Value="5" />
<Answer QuestionID="3945fd30-e2fb-4033-9f52-96ef6e4f1626" Value="5" />
</Rating>
<Rating Points="1.2" Satisfaction="2" Recommended="1" Nickname="dadada" VisitorTypeID="4678a819-71ca-4ea8-
b1b5-3ff078396b58" Id="1b71ae96-f03c-4259-a405-84918efded1f" ChangeDate="2011-12-01T11:09:00" Active="true"
CreateDate="2011-12-01T11:08:00" >
<UserComment />
<ParentComment />
<Answer QuestionID="8218f75b-4ed1-482f-aa44-0b6b37ef389c" Value="2" />
<Answer QuestionID="dc7f1005-a743-4581-a9f6-2be05a5f923f" Value="3" />
<Answer QuestionID="212d35e2-1e1c-4725-bfa3-e07f21988708" Value="0" />
<Answer QuestionID="8450d77d-c15e-4ec0-962c-c50e054beff3" Value="0" />
<Answer QuestionID="127b3703-e51e-4252-a62c-64a67491a238" Value="1" />
</Rating>
<Rating Points="2.4" Satisfaction="3" Recommended="0" Nickname="Hans" VisitorTypeID="4678a819-71ca-4ea8-
b1b5-3ff078396b58" Id="afb5a033-542a-48f0-995a-ca59a13d457c" ChangeDate="2011-12-01T11:09:00" Active="true"
CreateDate="2011-12-01T11:08:00" >
<UserComment>nicht gefallen</UserComment>
<ParentComment />
<Answer QuestionID="127b3703-e51e-4252-a62c-64a67491a238" Value="2" />
<Answer QuestionID="8450d77d-c15e-4ec0-962c-c50e054beff3" Value="2" />
<Answer QuestionID="8218f75b-4ed1-482f-aa44-0b6b37ef389c" Value="2" />
<Answer QuestionID="212d35e2-1e1c-4725-bfa3-e07f21988708" Value="3" />
<Answer QuestionID="dc7f1005-a743-4581-a9f6-2be05a5f923f" Value="3" />
</Rating>
</Ratings>
</RatingAverage>
</RatingsAverage>
</ServiceProvider>
</ServiceProviders>
</Result>
</FeratelDsiRS>

Basic Data For Service Providers 66 of 241


DESKLINE 3.0 STANDARD INTERFACE

Description Markup

When you set this optional attribute to true, you get back html format tags:

Full example of one Markup Description

<Descriptions>
<Description Id="8687160b-7881-4c01-b672-5a029ca8c2dc" Type="ServiceProviderDescription"
Language="de" Systems="L T I C" ShowFrom="101" ShowTo="1231" ChangeDate="2017-02-20T17:05:00">
&lt;b&gt;Bold&lt;/b&gt; &lt;i&gt;Italic&lt;/i&gt; &lt;u&gt;Underline&lt;/u&gt;
&lt;br&gt;
Testline &lt;p&gt;This is a paragraph!&lt;/p&gt;
&lt;h1&gt;Headline 1&lt;/h1&gt;
&lt;h2&gt;Headline 2&lt;/h2&gt;
&lt;h3&gt;Headline 3&lt;/h3&gt;
&lt;h4&gt;Headline 4&lt;/h4&gt;
&lt;h5&gt;Headline 5&lt;/h5&gt;
&lt;h6&gt;Headline 6&lt;/h6&gt;
Unordered List
&lt;ul&gt;
&lt;li&gt;List Item 1&lt;/li&gt;
&lt;li&gt;List Item 2&lt;/li&gt;
&lt;li&gt;List Item 3&lt;/li&gt;
&lt;/ul&gt;
Ordered List
&lt;ol&gt;
&lt;li&gt;List Item 1&lt;/li&gt;
&lt;li&gt;List Item 2&lt;/li&gt;
&lt;li&gt;List Item 3&lt;/li&gt;
&lt;/ol&gt;
Link &lt;a href="http://www.google.com"&gt;Linkname&lt;/a&gt;
</Description>

67 of 241
DESKLINE 3.0 STANDARD INTERFACE

ON DEMAND DATA FOR SHOWING AVAILABILITY CALENDAR


Very often customers want availability calendars to be shown for each product. Wether you synchronize
product and service availabilities plus arrival and departure templates (for more detailed information) very
regularly and store the data in your database. Or you can use this request (part of Basic Data) to show this
information on demand. So no more need for storing a huge amount of data plus the need to synchonise this
dynamicly changing data very often. We tried to provide a fast and slim solution for this matter, so that you are
able to call this data only in case a website user really has a look at the availability calendar.

REQUEST
Request field Description Can be empty? Multiple?
Originator The code of the point of sale requesting the data.
Provided by feratel.
Company The code of the company requesting the data. Provided
by feratel.
GetAvailabilities - DBCode 3 character data base code provides in response of
service provider details
GetAvailabilities - Start date from which on the availabilities should be in
StartDate, Month the response (best is to take the first of the current
month) plus the number of month, so enddate is
StartDate plus x Month.
GetAvailabilities - Sales Channel ID (provided by Feratel within accesss
SalesChannelId data) is mandatory, if a product has own availabilities
for a specific saleschannel you don’t have to add
service and product availabilities, this is done on
Deskline side
GetAvailabilities - Id of the service provider for which the availability
ServiceProviderId calendar should be shown. Avaialbilities of all products
are inside the response
GetAvailabilities - Optional parameters if only availability calendar of one
ProductId single product should be shown. If this attribute is not
provided reposne includes data for availabilities of all
products of the service provider.

EXAMPLE

Get availabilities for one service provider:


<?xml version="1.0" encoding="utf-8"?>
<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://interface.deskline.net/DSI/XSD">
<Request Originator="FERATEL" Company="FERATEL">
<GetAvailabilities DBCode="FRT" Months="4" StartDate="2013-05-01" SalesChannelId="BB556229-E7B1-4F21-9C6A-
2BEA7120BF5A" ServiceProviderId="DC1DEFE3-999A-4097-A5BF-7BD86A14E28A"/>
</Request>
</FeratelDsiRQ>

Get availabilities for one product:


<?xml version="1.0" encoding="utf-8"?>
<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://interface.deskline.net/DSI/XSD">
<Request Originator="FERATEL" Company="FERATEL">
<GetAvailabilities DBCode="FRT" Months="4" StartDate="2013-05-01" SalesChannelId="BB556229-E7B1-4F21-9C6A-
2BEA7120BF5A" ServiceProviderId="DC1DEFE3-999A-4097-A5BF-7BD86A14E28A"ProductId="ddf0d045-a03e-4585-ab12-

On Demand Data For Showing Availability Calendar 68 of 241


DESKLINE 3.0 STANDARD INTERFACE

fbb6f9d546fc"/>
</Request>
</FeratelDsiRQ>

RESPONSE
Response field Description Can be empty? Multiple?
AvailabilityCalendar List of data to create availability calendar for each
ProductId product
AV Each requested day has an AV element. This elements
includes all the data to build up an availability calendar
comma separated. Data inside:
 Date: YYYY-MM-DD
 Count of availability: 0 to x plus Special cases:
Count -1002 for Closed and -1001 for Own use
by service provider
 Minimum stay: in days
 Maximum stay: in days
 Intervall: in days
 Arrival possible: 0…No 1…Yes
 Departure possible: 0…No 1…Yes

EXAMPLE

<?xml version="1.0" encoding="UTF-8"?>


<FeratelDsiRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
Status="0" xmlns="http://interface.deskline.net/DSI/XSD">
<Result Index="1">
<AvailabilityCalendar ProductId="ddf0d045-a03e-4585-ab12-fbb6f9d546fc">
<AV>2013-05-01,15,1,999,1,1,1</AV>
<AV>2013-05-02,15,1,999,1,1,1</AV>
<AV>2013-05-03,15,1,999,1,1,1</AV>
<AV>2013-05-04,-1002,1,999,1,1,1</AV>
<AV>2013-05-05,-1002,1,999,1,1,1</AV>
<AV>2013-05-06,-1002,1,999,1,1,1</AV>
<AV>2013-05-07,-1002,1,999,1,1,1</AV>
<AV>2013-05-08,-1002,1,999,1,1,1</AV>
<AV>2013-05-09,-1002,1,999,1,1,1</AV>
<AV>2013-05-10,-1002,1,999,1,1,1</AV>
<AV>2013-05-11,15,1,999,1,1,1</AV>
<AV>2013-05-12,15,1,999,1,1,1</AV>
<AV>2013-05-13,15,1,999,1,1,1</AV>
<AV>2013-05-14,15,1,999,1,1,1</AV>
<AV>2013-05-15,15,1,999,1,1,1</AV>
<AV>2013-05-16,15,1,999,1,1,1</AV>
<AV>2013-05-17,-1001,1,999,1,1,1</AV>
<AV>2013-05-18,-1001,1,999,1,1,1</AV>
<AV>2013-05-19,-1001,1,999,1,1,1</AV>
<AV>2013-05-20,-1001,1,999,1,1,1</AV>
<AV>2013-05-21,15,1,999,1,1,1</AV>
<AV>2013-05-22,15,1,999,1,1,1</AV>
<AV>2013-05-23,6,1,999,1,1,1</AV>
<AV>2013-05-24,6,1,999,1,1,1</AV>
<AV>2013-05-25,6,1,999,1,1,1</AV>
<AV>2013-05-26,6,1,999,1,1,1</AV>
<AV>2013-05-27,6,1,999,1,1,1</AV>
<AV>2013-05-28,6,1,999,1,1,1</AV>
<AV>2013-05-29,6,1,999,1,1,1</AV>
<AV>2013-05-30,15,1,999,1,1,1</AV>
<AV>2013-05-31,15,1,999,1,1,1</AV>

On Demand Data For Showing Availability Calendar 69 of 241


DESKLINE 3.0 STANDARD INTERFACE

</AvailabilityCalendar>
</Result>
</FeratelDsiRS>

FRONT END EXAMPLES

CHECK FOR CHANGED SERVICE PROVIDERS


To make data synchronization more efficient a check for changed service provider is given. On service provider
level it is possible to request all data since a specific date (DateFrom). For request on service and product level
it is necessary to provide a service provider ID to get specific data. So if you synchronize availabilities, prices
and so on iteration through all service providers has to be done. For this case we provide this check for
changed data so you can reduce number of requests to a list of service provider which has changed data since a
specific date and time. This is part of basic data web service for service provider. Please note that deleted items
are not in response of this request. Deleted items always have to be called with special DeletedItems request.

REQUEST
Request field Description Can be empty? Multiple?
Originator The code of the point of sale requesting the data.
Provided by feratel.
Company The code of the company requesting the data. Provided
by feratel.
Range and GUIDs First, a range code to select the data must be defined.
IDs This is an enumeration if it is a town (TO) or a district
(DI) for example. The IDs of towns/districts are part of
the KeyValues function. If there is a need to call data
owners (DO) directly, the IDs are provided by feratel.
The top location (i.e. highest/widest range possible) will
be provided by feratel to get started (see range
example in KeyValues.xml). Basic data requests should
be done at max per town or district, never per region
unless specifically defined by feratel.
Filters While the Sales Channel is mandatory in a few places

Check For Changed Service Providers 70 of 241


DESKLINE 3.0 STANDARD INTERFACE

SalesChannelId (for example requesting prices) here it is optional in the


definition. If your are checking changes of a specific
sales channel you only have to use this filter once here
and it is taken for all requested changes depending on a
sales channel (availabilities, prices, sales rules
templates, arrival and departure templates, gaps).
This filters the response to only return service providers
that have products assigned to the specified Sales
Channel.
Filters DateFrom attribute occurs within the filter element of
DateFrom the request and is inherited to all elements requested.
In this kind of request DateFrom is a Date Time field
("2011-05-18T09:30:00").
For example, it is possible to request all service
providers that were changed in the last twelve hours.
Filters Filter on Start and End Date is mandatory if the request
Start and End contains one of these elements: availabilities, prices,
sales rules templates, arrival and departure templates,
gaps. If you are checking changes within a specific date
range you only have to use this filter once here and it is
taken for all requested changes.
Filters When requesting basic data the Systems-Attribute must
Systems already be provided to filter only internet-descriptions
for example. Example Systems=”T” for internet.
T…Internet
L…Local
I…Informator
C.. Catalogue
For multiple selection separate with a Space. Example
Systems = “L T”
Filters The type of service providers. Either Accommodation or
ServiceProvider Type AdditionalService.
Filters Enumeration: All/Active/Inactive. The default setting is
ServiceProvider Status “Active”, so the interface only returns active service
providers. If it is necessary to know which service
providers were deactivated, the value All or Inactive
can be used. The Element <Active> is returned on the
details level of the response.
Filters The language filter must be used to provide which
Language(s) translations should be transferred inside the DSI
response. It’s possible to request more than one
language at the time to save the amounts of requests
necessary.
ChangedServiceProvider <ChangedServiceProviders >
<Details />
<Documents />
<Descriptions />
<Links />
<Facilities />
<Addresses />
<RatingsAverage />
<CustomAttributes />
<HotSpots />
<Services>
<Details />
<Documents />
<Descriptions />
<Links />
<Facilities />

Check For Changed Service Providers 71 of 241


DESKLINE 3.0 STANDARD INTERFACE

<Availabilities />
<Products>
<Details />
<Documents />
<Descriptions />
<Links />
<PriceDetails />
<ArrivalDepartureTemplates />
<SalesRuleTemplates />
<Availabilities />
<Gaps />
</Products>
</Services>
<AdditionalServices>
<Details />
<Documents />
<Descriptions />
<Links />
<Facilities />
<AdditionalProducts>
<Details />
<PriceDetails />
</AdditionalProducts>
</AdditionalServices>
</ChangedServiceProviders>

EXAMPLE

Get list of changed service providers:


<?xml version="1.0" encoding="utf-8"?>
<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://interface.deskline.net/DSI/XSD">
<Request Originator="FERATEL" Company="FERATEL">
<Range Code="RG">
<Item Id="F180FFD5-4FBF-4F2C-AC00-7E8B94462F2C" />
</Range>
<BasicData>
<Filters SalesChannelId="BB556229-E7B1-4F21-9C6A-2BEA7120BF5A" DateFrom="2011-05-18T09:30:00" Start="2011-05-
16" End="2011-06-16" Systems="T" >
<ServiceProvider Type="Accommodation"/>
<Languages>
<Language Value="de" />
<Language Value="en" />
</Languages>
</Filters>
<ChangedServiceProviders >
<Services>
<Availabilities />
<Products>
<PriceDetails />
<ArrivalDepartureTemplates />
<SalesRuleTemplates />
<Availabilities />
<Gaps />
</Products>
</Services>
</ChangedServiceProviders>
</BasicData>
</Request>
</FeratelDsiRQ>

RESPONSE
Below is an example of a response with a list of Service Provider IDs, which has changed data of any of
elements in the request. This list should be base for basic data request.
Check For Changed Service Providers 72 of 241
DESKLINE 3.0 STANDARD INTERFACE

Response field Description Can be empty? Multiple?


ChangedServiceProvider List of Service Provider were there were changes in the
requested elements within the specific time range
ID GUID of the service provider

<?xml version="1.0" encoding="UTF-8"?>


<FeratelDsiRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
Status="0" Message="OK" xmlns="http://interface.deskline.net/DSI/XSD">
<Result Index="1">
<ChangedServiceProviders>
<ServiceProvider Id="c8bc5944-474b-41aa-88f4-054e8c4b9ed9" />
<ServiceProvider Id="ea06184c-a6a1-4e19-acec-125e273c623a" />
<ServiceProvider Id="77a7c00d-fc50-4e36-a7d8-4582116c0742" />
<ServiceProvider Id="e970f557-4e47-4597-8ab6-5ddbdf8ba505" />
<ServiceProvider Id="b38de37b-20f1-4631-8cac-60dabdf1a22a" />
<ServiceProvider Id="fc50ecb4-67e8-4d13-b5c1-687b336b2926" />
<ServiceProvider Id="f20acdb7-2df0-4d6d-8050-72523b4a84f5" />
<ServiceProvider Id="dc1defe3-999a-4097-a5bf-7bd86a14e28a" />
<ServiceProvider Id="d19969f8-9d94-4966-8f56-876b49eb2985" />
<ServiceProvider Id="732cd163-34b1-4de8-9dee-8fdd94ba5cdb" />
<ServiceProvider Id="8a438e5d-fbe6-4357-9413-9342ef5b5694" />
<ServiceProvider Id="2dda07b9-7194-4a88-aa6f-f159d8daabd6" />
<ServiceProvider Id="c4b47dd0-80d8-4c50-88c3-f7ec85409401" />
</ChangedServiceProviders>
</Result>
</FeratelDsiRS>

BASIC DATA FOR EVENTS


Events also have a new logic in Deskline 3.0 and can also be requested through this interface. Every event must
be assigned to a town so it is also possible to request events only for one town or for a whole region. Events
consist of the following parts: Details, Documents, Descriptions, Links, Facilities (more like categories for
events) and Addresses.

Note: While it is possible to filter the basic data for a specific timeframe the events should still be synchronized
to a local database in intervals and not be requested every time a user is looking for events.

Note: After an event does no longer take place in the future, do not synchronozice these events any longer.

REQUEST
A request consists of three different parts: first, the mandatory values, then the optional filter and then the
definition, which elements to provide in the response.

Request field Description Can be empty? Multiple?


Originator The code of the point of sale requesting the data.
Provided by feratel.
Company The code of the company requesting the data. Provided
by feratel.
Range and GUIDs First, a range code (TO) to select the data must be
IDs defined. The IDs of towns are part of the KeyValues
function. The top location (i.e. highest/widest range
possible) will be provided by feratel to get started (see
range example in KeyValues.xml)
Filters <PreSelectedEventIDs> can be used to list more than one
PreSelectedEventIDs event based on the Event-ID.

Basic Data For Events 73 of 241


DESKLINE 3.0 STANDARD INTERFACE

Filters – Events, Events can be filtered for a specific timeframe


Attributes Start/End (Start/End).
Filters – Events, Events can be set to only be available for different output
Attributes Systems systems such as: local (Deskline 3.0 backend), internet
presentation, Informator or catalog productions.
L…Local
T…Internet
I…Informator
C… Catalog
Filters – Events, It is also possible to use the optional attribute Status
Attribute Status (Values: All/Active/Inactive) – by default, only active
events are returned.
Filters – Events, Visibility can define how important an event is on a
Attribute Visibility geographical level. If it’s a small event that’s only
important for a link for the town it takes place in or if it’s
important enough to show up on a link for a whole region
or a whole country. Enumeration: Local, Town, Region,
Subregion, Country
Filters – Events, Events can be assigned to a series of events, the
Attribute SerialEvent SerialEvent information can be requested in the
KeyValues function. For example all events for one
festival can be assigned to the same SerialEvent. The
basic data allows to filter based on such a SerialEvent.
Filters – Events, Events can be top events or not. Set to true to get only
Attribute IsTopEvent top events, false for the opposite. If the filter is not set
both top events and not top events are in the response.
Filters - Events Basic data requests can be limited to provide only events
Marketing Group(s) that are part of special marketing groups. E.g. “Mountain
bike hotels”, “Urlaub am Bauernhof”. The list of these IDs
is provided in the Key Values Function.
Language(s) The language filter must be used to provide which
translations should be transferred inside the DSI
response. It’s possible to request more than one
language at the time to save the amounts of requests
necessary.
Events Id Id in this case is an attribute not subelement. When Id is
provided one single event can be called.
Events – Attribut True/False value, false by default. When set to true, the
ShowDataOwner DSI will also return one more element in events details. It
is the organization code of the tourism orgianisation this
event belongs to.
<Details>
...
<DataOwner>FERATEL</DataOwner>
</Details>
Events Details Define if event-details should be part of the response.
Use DateFrom to define the modification-date-filter.
Events Documents Define if event-documents (mostly images) should be
part of the response. Use DateFrom to define the
modification-date-filter.
Events Descriptions Define if event-descriptions should be part of the
response. Use DateFrom to define the modification-date-
filter.
Descriptions Enum: true/false default: false
Markup when you set the optional attribute Markup=”true” you
get back html format tags which might be selected from
the customers.
Basic Data For Events 74 of 241
DESKLINE 3.0 STANDARD INTERFACE

Events Links Define if event-links should be part of the response. Use


DateFrom to define the modification-date-filter.
Events Facilities Define if event-facilities should be part of the response.
Use DateFrom to define the modification-date-filter.
Events Addresses Define if event-addresses should be part of the response.
Use DateFrom to define the modification-date-filter.
There are three types of event-addresses: Organizer,
Booking, Info
Events Define if event-custom attributes should be part of the
CustomAttributes response. Use DateFrom to define the modification-date-
filter.
Events Define if event-handicap facilities should be part of the
HandicapFacilities response. Use DateFrom to define the modification-date-
filter.
Events Define if event-handicap classifications should be part of
HandicapClassifications the response. Use DateFrom to define the modification-
date-filter.

EXAMPLES
Get all information for events in June for one town:
<?xml version="1.0" encoding="utf-8"?>
<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://interface.deskline.net/DSI/XSD">
<Request Originator="" Company="">
<Range Code="TO">
<Item Id="F180FFD5-4FBF-4F2C-AC00-7E8B94462F2C" />
</Range>
<BasicData>
<Filters>
<Events Start="2010-06-01" End="2010-06-30" Systems="T " />
<Languages>
<Language Value="de" />
<Language Value="en" />
</Languages>
</Filters>
<Events>
<Details DateFrom="1980-01-01" />
<Documents DateFrom="1980-01-01" Systems="L T" />
<Descriptions DateFrom="1980-01-01" Systems="L T" Markup=”true”/>
<Links DateFrom="1980-01-01" />
<Facilities DateFrom="1980-01-01" />
<Addresses DateFrom="1980-01-01" />
<HandicapFacilities DateFrom="1980-01-01" />
<HandicapClassifications DateFrom="1980-01-01" />
</Events>
</BasicData>
</Request>
</FeratelDsiRQ>

Basic Data For Events 75 of 241


DESKLINE 3.0 STANDARD INTERFACE

RESPONSE
Below is an example of a full response with all elements and attributes possible at the moment. Mind that
based on the request it’s possible that not all of these elements are part of the response. For details on the
data types and XML enumerations refer to the XSD documents.

Response field Description Can be empty? Multiple?


ID GUID of the event
ChangeDate Date/time indicator when the item was last changed.
Name Name of the event
Location Free-text entry about the event location
Active Indicates if the event is active or not.
Towns GUID of the towns assigned to the event. As of June
2010 there can be only one town assigned but with
future updates it might be possible that more than one
town can be assigned to one item, so the structure is
already prepared for this.
Town GUID of the town assigned to the event
Position Latitude, GPS Coordinates
Longitude
IsTopEvent Flag if this is a “top-event” or not, special marker
(true/false)
HolidayThemes e.g. Weekend, Wedding, Family, etc..
ConnectedEntries An event can be connected to one or more service
providers and/or one or more infrastructure items.
If type is “EventInfrastructure” the connected entry is a
infrastructure. “EventServiceProvider” means
connected Entry is a ServiceProvider of type
Accommodation or Additional Service.
SerialEvents An event can be connected to a series of events like a
special festival (see KeyValues for these values)
Visibility Visibility can define how important an event is on a
geographical level. If it’s a small event that’s only
important for a link for the town it takes place in or if
it’s important enough to show up on a link for a whole
region or a whole country. Enumeration: Local, Town,
Region, Subregion, Country
Dates Not only can there be multiple dates for one event but
it’s also possible in Deskline 3.0 to flag an event to take
place always, then the dates can be empty.
StartTime Starting times per weekday – or the same starting time
for all weekday, different combinations possible.
Duration Duration of the event, Type is either one of these
values: None, Day, Hours, Minutes and a value.
Documents Documents can be images, videos, PDF-files, etc. For
each document, the URL will be provided the image can
then be downloaded into an external database. The
URL will return the original uploaded file by the user,
not a resized or otherwise manipulated version. It is
also possible that documents have different names in
different languages, hence the translations. In addition
there is also a copyright note for each document if
necessary. Each document can either have a From-To
timeframe (only day/month, not year) or can be set to
Basic Data For Events 76 of 241
DESKLINE 3.0 STANDARD INTERFACE

be shown as “always” in which case From-To is send as


“101”-“1231” in the element. Documents can also be
set to only be available for different output systems
such as: local (Deskline 3.0 backend), internet
presentation, Informator or catalog productions. When
requesting basic data the Systems-Attribute must
already be provided to filter only internet-documents
for example. The extension is part of the response.
Links There is a URL, name, type and order for each link
address connected to the parent. Type categorizes the
link in different groups. E.g. Object URL for homepage
Descriptions Descriptions in various languages. Each description can
either have a From-To timeframe (only day/month, not
year) or can be set to be shown as “always” in which
case From-To is send as “101”-“1231” in the element.
Line-breaks are not converted to HTML-line-breaks, the
description will be returned as entered in the system.
Descriptions can also be set to only be available for
different output systems such as: local (Deskline 3.0
backend), internet presentation, Informator or catalog
productions. When requesting basic data the Systems-
Attribute must already be provided to filter only
internet-descriptions for example. Descriptions will
have the type EventHeader (long description) or
EventHeaderShort (short description).
Facilities Facilities for an event. In the response, only the ID and
value are sent. The translations are available through
the Key Values function. The value is optional as well
and is used e.g. for the facility information “meeting
rooms” – i.e. “meeting rooms: 3”.
If there are any IDs present that are not provided in the
Key Values function it is because of items that were
created by the customers themselves and therefore are
not global and not available in the Key Values.
Addresses There can be multiple addresses connected to one
event, four types are possible: Organizer, Booking, Info
and Venue.
ID ID of the address.
ChangeDate Date/time indicator when the item was last changed
Address Company Company name
Address FirstName Contact person first name
Address LastName Contact person last name
Address AddressLine1 Street name / house number, line 1
Address AddressLine2 Street name / house number, line 2, additional line if
necessary
Address Country Country code
Address ZipCode Zip code
Address Town Town name
Address Email Primary e-mail address
Address Fax Fax
Address URL Website URL
Address Phone Landline

Basic Data For Events 77 of 241


DESKLINE 3.0 STANDARD INTERFACE

Address Mobile Mobile phone number


CustomAttributes CustomAttributes must only be used if the
customer/destination specifies the demand!
CustomAttributes are a list of fields that can be defined
per destination.
When requesting CustomAttributes it is possible that
the attribute Value will be empty.
HandicapFacilities Handicap facilities for an event. In the response, only
the ID, value and comments in requested languages are
sent. The translations of the name of the facility are
available through the Key Values function.
HandicapClassifications Handicap classifications for an event. In the response,
only the ID is sent. The translations of the name of the
classifications are available through the Key Values
function.

Full example for one event:


<?xml version="1.0"?>
<FeratelDsiRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" Status="0"
Message="OK" xmlns="http://interface.deskline.net/DSI/XSD">
<Result Index="1">
<Events>
<Event Id="eaff6469-2dc8-4369-9ac3-51f9baf9dddd" ChangeDate="2010-05-21T16:41:00">
<Details>
<Names>
<Translation Language="de">Beach-Party</Translation>
<Translation Language="en">Beach-Party</Translation>
</Names>
<Location>
<Translation Language="de">Grand Hotel Patricia</Translation>
<Translation Language="en">Grand Hotel Patricia</Translation>
</Location>
<Active>true</Active>
<Towns>
<Item Id="090a18ae-5d50-421e-a65a-c5a2b8227ae5" />
<Item Id="2f7c71f3-f375-434b-9a04-49f474df6b68" />
</Towns>
<Position Latitude="13.9056015014648" Longitude="46.6095920078523" />
<IsTopEvent>false</IsTopEvent>
<HolidayThemes>
<Item Id="090a18ae-5d50-421e-a65a-c5a2b8227ae5" />
<Item Id="2f7c71f3-f375-434b-9a04-49f474df6b68" />
</HolidayThemes>
<ConnectedEntries>
<ConnectedEntry Type="EventInfrastructure" Id="2f050ae2-85f5-4a99-8c92-075ff4b3f58b" />
<ConnectedEntry Type="EventInfrastructure" Id="034927b4-062e-499e-9bea-bb638814dae5" />
<ConnectedEntry Type="EventServiceProvider" Id="e59a3a87-8b76-423a-9a54-767ddc405d90" />
</ConnectedEntries>
<SerialEvents>
<SerialEvent Id="3a8b8857-500c-4693-8afe-7ec4c258b234" />
</SerialEvents>
<Visibility>Local</Visibility>
<Dates>
<Date From="2010-07-30" To="2010-08-01" />
</Dates>
<StartTimes>
<StartTime Time="00:23:00" Mon="false" Tue="false" Wed="false" Thu="false" Fri="true" Sat="true" Sun="true" />
</StartTimes>
<Duration Type="None">0</Duration>
</Details>
<Addresses>
<Address Type="Organizer" ChangeDate="2009-10-01T14:17:00">
<Company>Hotel Sonne, Abr. Res.</Company>
<FirstName />
<LastName>Huber</LastName>
<AddressLine1>Am Wald 1</AddressLine1>
<AddressLine2 />
<Country>DE</Country>
<ZipCode>88605</ZipCode>
<Town>Meßkirch</Town>
<Email />

Basic Data For Events 78 of 241


DESKLINE 3.0 STANDARD INTERFACE

<Fax />
<URL />
<Phone />
<Mobile />
</Address>
<Address Type="Booking" ChangeDate="2009-10-01T14:17:00">
<Company>Hotel Sonne, Abr. Res.</Company>
<FirstName />
<LastName>Huber</LastName>
<AddressLine1>Am Wald 1</AddressLine1>
<AddressLine2 />
<Country>DE</Country>
<ZipCode>88605</ZipCode>
<Town>Meßkirch</Town>
<Email />
<Fax />
<URL />
<Phone />
<Mobile />
</Address>
<Address Type="Info" ChangeDate="2009-10-01T14:17:00">
<Company>Hotel Sonne, Abr. Res.</Company>
<FirstName />
<LastName>Huber</LastName>
<AddressLine1>Am Wald 1</AddressLine1>
<AddressLine2 />
<Country>DE</Country>
<ZipCode>88605</ZipCode>
<Town>Meßkirch</Town>
<Email />
<Fax />
<URL />
<Phone />
<Mobile />
</Address>
</Addresses>
<Address Type="Venue" ChangeDate="2009-10-01T14:17:00">
<Company>Hotel Sonne, Abr. Res.</Company>
<FirstName />
<LastName>Huber</LastName>
<AddressLine1>Am Wald 1</AddressLine1>
<AddressLine2 />
<Country>DE</Country>
<ZipCode>88605</ZipCode>
<Town>Meßkirch</Town>
<Email />
<Fax />
<URL />
<Phone />
<Mobile />
</Address>
</Addresses>
<Descriptions>
<Description Id="e57d510f-8a90-4689-a4d5-0b5eb95641a6" Type="EventHeader" Language="de" Systems="L T I C" ShowFrom="101"
ShowTo="1231" ChangeDate="2010-05-03T16:15:00">Dieses Mega-Event findet direkt am Faaker-See statt.</Description>
</Descriptions>
<Links>
<Link Id="c857610e-2c5b-4317-bbbc-e5cb81654293" Name="fest" URL="http://www.test.com" ChangeDate="2010-05-20T16:40:00"
Type="0" Order="1" />
</Links>
<Facilities ChangeDate="2009-10-01T14:17:00">
<Facility Id="189c28da-b1e1-455b-8a02-1191931ab458" Value="1" />
<Facility Id="9dbe2baf-9c86-4e95-9dc3-55b14730b23b" Value="1" />
</Facilities>
</Event>
</Events>
</Result>
</FeratelDsiRS>

CHECK FOR CHANGED EVENTS


To make data synchronization more efficient a check for changed events is given. So you can reduce number of
requests to a list of events which has changed data since a specific date and time. This is part of basic data web
service for events. Please note that delted items are not in response of this request. Deleted items always have
to be called with special DeletedItems request.

Check For Changed Events 79 of 241


DESKLINE 3.0 STANDARD INTERFACE

REQUEST
Request field Description Can be empty? Multiple?
Originator The code of the point of sale requesting the data.
Provided by feratel.
Company The code of the company requesting the data. Provided
by feratel.
Range and GUIDs First, a range code to select the data must be defined.
IDs This is an enumeration if it is a town (TO) or a district
(DI) for example. The IDs of towns/districts are part of
the KeyValues function. If there is a need to call data
owners (DO) directly, the IDs are provided by feratel.
The top location (i.e. highest/widest range possible) will
be provided by feratel to get started (see range
example in KeyValues.xml). Basic data requests should
be done at max per town or district, never per region
unless specifically defined by feratel.
Filters DateTimeFrom attribute occurs within the filter
DateTimeFrom element of the request and is inherited to all elements
requested. In this kind of request DateTimeFrom is a
Date Time field ("2011-05-18T09:30:00").
For example, it is possible to request all events that
were changed in the last twelve hours.
Filters Filter on Start and End Date is mandatory to check
Start and End those events taking place within this specific time
range.
Filters When requesting basic data the Systems-Attribute must
Systems already be provided to filter only events which should
be shown online or internet-descriptions for example.
Example Systems=”T” for internet.
T…Internet
L…Local
I…Informator
C.. Catalogue
For multiple selection separate with a Space. Example
Systems = “L T”
Filters Enumeration: All/Active/Inactive. The default setting is
Events Status “Active”, so the interface only returns active events. If
it is necessary to know which events were deactivated,
the value All or Inactive can be used. The Element
<Active> is returned on the details level of the
response.
Filters ChangedEvents For event related filters. Attributes are Status
(Enumeration: All, Active, Inactive) with default value
Active; IsTopEvent (Enumeration: true, false) with
default value false, which means response includes Top
events and none top events.
Filters The language filter must be used to provide which
Language(s) translations should be transferred inside the DSI
response. It’s possible to request more than one
language at the time to save the amounts of requests
necessary.
ChangedEvents <ChangedEvents>
<Details />
<Documents />
<Descriptions />

Check For Changed Events 80 of 241


DESKLINE 3.0 STANDARD INTERFACE

<Links />
<Facilities />
<Addresses />
<CustomAttributes />
<HandicapFacilities />
</ChangedEvents>

EXAMPLE

Get list of changed events:


<?xml version="1.0" encoding="utf-8"?>
<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://interface.deskline.net/DSI/XSD">
<Request Originator="FERATEL" Company="FERATEL">
<Range Code="RG">
<Item Id="F180FFD5-4FBF-4F2C-AC00-7E8B94462F2C" />
</Range>
<BasicData>
<Filters DateTimeFrom="2013-02-26T12:00:00" Start="2013-02-27" End="2013-03-29" Systems="T" >
<ChangedEvents Status="All " IsTopEvent=" false"/>
<Languages>
<Language Value="de" />
<Language Value="en" />
</Languages>
</Filters>
<ChangedEvents>
<Details />
<Documents />
<Descriptions />
<Links />
<Facilities />
<Addresses />
<CustomAttributes />
<HandicapFacilities />
</ChangedEvents>
</BasicData>
</Request>
</FeratelDsiRQ>

RESPONSE
Below is an example of a response with a list of Event IDs, which has changed data of any of elements in the
request. This list should be base for basic data request.

Response field Description Can be empty? Multiple?


ChangedEvents List of Events were there were changes in the
requested elements within the specific time range
Id GUID of the event

<?xml version="1.0" encoding="UTF-8"?>


<FeratelDsiRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" Status="0" Message="OK"
xmlns="http://interface.deskline.net/DSI/XSD">
<Result Index="1">
<ChangedEvents>
<Event Id="c8bc5944-474b-41aa-88f4-054e8c4b9ed9" />

Check For Changed Events 81 of 241


DESKLINE 3.0 STANDARD INTERFACE

<Event Id="ea06184c-a6a1-4e19-acec-125e273c623a" />


<Event Id="77a7c00d-fc50-4e36-a7d8-4582116c0742" />
<Event Id="e970f557-4e47-4597-8ab6-5ddbdf8ba505" />
</ChangedEvents>
</Result>
</FeratelDsiRS>

BASIC DATA FOR INFRASTRUCTURE


Every infrastructure item must be assigned to a town so it is also possible to request events only for one town
or for a whole region.

Items consist of the following parts: Details, Documents, Descriptions, Links, and Addresses. In general, an item
has a fixed type (e.g. Food & Beverages, Routes & Tours, Sport & Leisure, Wellness & Health, …) and various
topics concerning this type (e.g. “Bar” for “Food & Beverages”).

REQUEST
A request consists of three different parts: first, the mandatory values, then the optional filter and then the
definition, which elements to provide in the response.

Can be
Request field Description empty?
Multiple?

Originator The code of the point of sale requesting the data.


Provided by feratel.
Company The code of the company requesting the data. Provided
by feratel.
Range and GUIDs First, a range code (TO) to select the data must be
IDs defined. The IDs of towns are part of the KeyValues
function. The top location (i.e. highest/widest range
possible) will be provided by feratel to get started (see
range example in KeyValues.xml)
Filters <PreSelectedInfrastructureIDs> can be used to list more
PreSelectedInfrastructureIDs than one infrastructure based on the Infrastructure-ID.
Filters – Infrastructure, Infrastructures can be set to only be available for
Attribute Systems different output systems such as: local (Deskline 3.0
backend), internet presentation, Informator or catalog
productions.
L…Local
T…Internet
I…Informator
C… Catalog
Filters – Infrastructure, It is also possible to use the optional attribute Status
Attribute Status (Values: All/Active/Inactive) – by default, only active
infrastructure items are returned.
Filters – Infrastructure, Infrastructure items can be either one of a specific type
Attribute Type defined in the system. The types can be gathered
through the KeyValues function InfrastructureTypes.
Filters – Infrastructure, Basic data requests can be limited to provide only
Marketing Group(s) infrastructures that are part of special marketing
groups. E.g. “Mountain bike hotels”, “Urlaub am
Bauernhof”. The list of these IDs is provided in the Key
Values Function.
Language(s) The language filter must be used to provide which

Basic Data For Infrastructure 82 of 241


DESKLINE 3.0 STANDARD INTERFACE

translations should be transferred inside the DSI


response. It’s possible to request more than one
language at the time to save the amounts of requests
necessary.
Infrastructure -Attribute Id Id in this case is an attribute not subelement. When Id is
provided one single infrastructure can be called.
Infrastructure –Attribut True/False value, false by default. When set to true, the
ShowDataOwner DSI will also return one more element in infrstructure
details. It is the organization code of the tourism
orgianisation this infrastructure belongs to.
<Details>
...
<DataOwner>FERATEL</DataOwner>
</Details>
Infrastructure Details Define if event-details should be part of the response.
Use DateFrom to define the modification-date-filter.
In some cases it is important to have only one main
topic. Customer can define one, but this is no must.
Send optional attribute IncludeMainTopicId=”true” to
get this information.
Infrastructure Documents Define if event-documents (mostly images) should be
part of the response. Use DateFrom to define the
modification-date-filter.
Infrastructure Descriptions Define if event-descriptions should be part of the
response. Use DateFrom to define the modification-
date-filter.
Descriptions Enum: true/false default: false
Markup when you set the optional attribute Markup=”true” you
get back html format tags which might be selected from
the customers.
Infrastructure Links Define if infrastructure-links should be part of the
response. Use DateFrom to define the modification-
date-filter.
Infrastructure Addresses Define if infrastructure -addresses should be part of the
response. Use DateFrom to define the modification-
date-filter. There are two types of infrastructure -
addresses: ExternalAddress and InternalAddress. Both
are returned in case they are really needed but in
general only the external address should be displayed to
guests.
Infrastructure Hotspots Define if infrastructure-hotspots should be part of the
response. Use DateFrom to define the modification-
date-filter.
Infrastructure Define if infrastructure -custom attributes should be
CustomAttributes part of the response. Use DateFrom to define the
modification-date-filter.
HandicapFacilities Define if infrastructure -handicap facilities should be
part of the response. Use DateFrom to define the
modification-date-filter.
HandicapClassififcations Define if infrastructure -handicap classifications should
be part of the response. Use DateFrom to define the
modification-date-filter.

Basic Data For Infrastructure 83 of 241


DESKLINE 3.0 STANDARD INTERFACE

EXAMPLE

Get all information for infrastructure items in one town:


<?xml version="1.0" encoding="utf-8"?>
<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://interface.deskline.net/DSI/XSD">
<Request Originator="FERATEL" Company="">
<Range Code="TO">
<Item Id="F180FFD5-4FBF-4F2C-AC00-7E8B94462F2C" />
</Range>
<BasicData>
<Filters>
<Infrastructure Systems="T " />
<Languages>
<Language Value="de" />
</Languages>
</Filters>
<Infrastructure ShowDataOwner="true" >
<Details DateFrom="1980-01-01" IncludeMainTopicId="true" />
<Documents DateFrom="1980-01-01" Systems="L T" />
<Descriptions DateFrom="1980-01-01" Systems="L T" Markup="true" />
<Links DateFrom="1980-01-01" />
<Addresses DateFrom="1980-01-01" />
<HotSpots DateFrom="1980-01-01" />
<HandicapFacilities DateFrom="1980-01-01" />
<HandicapClassifications DateFrom="1980-01-01" />
</Infrastructure>
</BasicData>
</Request>
</FeratelDsiRQ>

RESPONSE
Below is an example of a full response with all elements and attributes possible at the moment. Mind that
based on the request it’s possible that not all of these elements are part of the response. For details on the
data types and XML enumerations refer to the XSD documents.

Response field Description Can be empty? Multiple?


ID GUID of the infrastructure item
ChangeDate Date/time indicator when the item was last changed.
Names Name of the infrastructure item
Topics Type and Topics connected to this item (see KeyValues
for these values). If main topic id is included attribute
MainTopicId appears, if main topic not set by customer
it is zero GUID
Active Indicates if the infrastructure is active or not.
Towns GUID of the towns assigned to the event. As of June
2010 there can be only one town assigned but with
future updates it might be possible that more than one
town can be assigned to one item, so the structure is
already prepared for this.
Position Latitude, GPS Coordinates
Longitude
HolidayThemes e.g. Weekend, Wedding, Family, etc..
ConnectedEntries An infrastructure item can be connected to one or
more service providers and/or one or more events.
If type is “EventInfrastructure” the connected entry is
an event. “InfrastructureServiceProvider” means
connected Entry is a ServiceProvider of type
Accommodation or Additional Service. And if
Type="InfrastructureInfrastructure" connected entry is

Basic Data For Infrastructure 84 of 241


DESKLINE 3.0 STANDARD INTERFACE

an infrastructure.
OpeningHours An infrastructure item can have none, one or more
opening hours for different periods, times and week
day
FoodAndBeverage An infrastructure of type FoodAndBeverage has four
additional field: PriceFrom, PriceTo, SeatsInside and
SeatsOutside
These fields are only included in the response if the
requested infrastructure is of type FoodAndBeverage
Documents Documents can be images, videos, PDF-files, etc. For
each document, the URL will be provided the image can
then be downloaded into an external database. The
URL will return the original uploaded file by the user,
not a resized or otherwise manipulated version. It is
also possible that documents have different names in
different languages, hence the translations. In addition
there is also a copyright note for each document if
necessary. Each document can either have a From-To
timeframe (only day/month, not year) or can be set to
be shown as “always” in which case From-To is send as
“101”-“1231” in the element. Documents can also be
set to only be available for different output systems
such as: local (Deskline 3.0 backend), internet
presentation, Informator or catalog productions. When
requesting basic data the Systems-Attribute must
already be provided to filter only internet-documents
for example. The extension is part of the response.
Links There is a URL, name, type and order for each link
address connected to the parent. Type categorizes the
link in different groups. E.g. Object URL for homepage
Descriptions Descriptions in various languages. Each description can
either have a From-To timeframe (only day/month, not
year) or can be set to be shown as “always” in which
case From-To is send as “101”-“1231” in the element.
Line-breaks are not converted to HTML-line-breaks, the
description will be returned as entered in the system.
Descriptions can also be set to only be available for
different output systems such as: local (Deskline 3.0
backend), internet presentation, Informator or catalog
productions. When requesting basic data the Systems-
Attribute must already be provided to filter only
internet-descriptions for example. Descriptions will
have the type InfrastructureShort, InfrastructureLong,
InfrastructureOpeningTimes.
Addresses There can be multiple addresses connected to one
item, two types are possible at the moment:
ExternalAddress and InternalAddress. Both addresses
are returned from the web service but unless it’s
demanded by the customer, only the external address
must be displayed to the guest.
ID ID of the address.
ChangeDate Date/time indicator when the item was last changed
Address Company Company name
Address FirstName Contact person first name

Basic Data For Infrastructure 85 of 241


DESKLINE 3.0 STANDARD INTERFACE

Address LastName Contact person last name


Address AddressLine1 Street name / house number, line 1
Address AddressLine2 Street name / house number, line 2, additional line if
necessary
Address Country Country code
Address ZipCode Zip code
Address Town Town name
Address Email Primary e-mail address
Address Fax Fax
Address URL Website URL
Address Phone Landline
Address Mobile Mobile phone number
HotSpots Hotspots related to the infrastructure. Id and distance
in kilometer is shown. List of names according to the
Ids provided by Key Values
CustomAttributes CustomAttributes must only be used if the
customer/destination specifies the demand!
CustomAttributes are a list of fields that can be defined
per destination.

When requesting CustomAttributes it is possible that


the element will be empty.
HandicapFacilities Handicap facilities for an infrastructure. In the
response, only the ID and value are sent. The
translations are available through the Key Values
function.
HandicapClassifications Handicap facilities for an infrastructure. In the
response, only the ID and value are sent. The
translations are available through the Key Values
function.

Details example for one infrastructure item:


<InfrastructureItem Id="52c510a2-cf52-4883-8711-8cf8004ec607" ChangeDate="2011-02-15T08:05:00">
<Details>
<Names>
<Translation Language="de">Afro, Cafe</Translation>
<Translation Language="en">Afro, Cafe</Translation>
</Names>
<Topics Type="1">
<Topic Id="8c871e8d-0d52-45b9-aec8-705b514c4b5f" />
</Topics>
<Active>true</Active>
<Towns>
<Item Id="3310c506-a478-4be8-af74-df697c0738fb" />
</Towns>
<Position Latitude="46.6268063953552" Longitude="13.817024230957" />
<HolidayThemes>
<Item Id="78f5739b-d2e4-49ab-99f1-cca61994137e" />
<Item Id="6862a86a-1105-49f6-a9d1-7a3c34b7d82f" />
</HolidayThemes>
<ConnectedEntries>
<ConnectedEntry Type="InfrastructureServiceProvider" Id="ea06184c-a6a1-4e19-acec-125e273c623a" />
<ConnectedEntry Type="EventInfrastructure" Id="28eb6183-ff81-4d79-8545-cd91db210bde" />
</ConnectedEntries>
<OpeningHours>
<OpeningHour DateFrom="2010-08-01" DateTo="2011-07-30" TimeFrom="10:00" TimeTo="00:00" Mon="true" Tue="true" Wed="true"
Thu="true" Fri="true" Sat="false" Sun="false" />
<OpeningHour DateFrom="2010-08-01" DateTo="2012-07-30" TimeFrom="09:00" TimeTo="22:00" Mon="false" Tue="false" Wed="false"
Thu="false" Fri="false" Sat="true" Sun="true" />
</OpeningHours>
</Details>
<Addresses>
<Address Type="InfrastructureExternal" ChangeDate="2010-08-12T19:36:00" Id="8b8c7a00-8fd0-4c47-ac4a-f072f3149a6f">

Basic Data For Infrastructure 86 of 241


DESKLINE 3.0 STANDARD INTERFACE

<Company>Afro Cafe GmbH</Company>


<Title>Herr</Title>
<FirstName>Thomas</FirstName>
<LastName>Anger</LastName>
<AddressLine1>Weg 1</AddressLine1>
<AddressLine2 />
<Country>AT</Country>
<ZipCode>5020</ZipCode>
<Town>Salzburg</Town>
<Email>[email protected]</Email>
<Fax>(0043) 34567 6987676</Fax>
<URL>http://www.afrocoffee.com</URL>
<Phone>(0043) 3456 14332233</Phone>
<Mobile>(0043) 664 1232323</Mobile>
</Address>
<Address Type="InfrastructureInternal" ChangeDate="2010-08-12T19:36:00" Id="8b8c7a00-8fd0-4c47-ac4a-f072f3149a6f">
<Company>Afro Cafe GmbH</Company>
<Title>Herr</Title>
<FirstName>Thomas</FirstName>
<LastName>Anger</LastName>
<AddressLine1>Weg 1</AddressLine1>
<AddressLine2 />
<Country>AT</Country>
<ZipCode>5020</ZipCode>
<Town>Salzburg</Town>
<Email>[email protected]</Email>
<Fax>(0043) 34567 6987676</Fax>
<URL>http://www.afrocoffee.com</URL>
<Phone>(0043) 3456 14332233</Phone>
<Mobile>(0043) 664 1232323</Mobile>
</Address>
</Addresses>
<Descriptions>
<Description Id="565ce39b-dad0-45fb-bfbe-2f2b299fd54a" Type="InfrastructureLong" Language="de" Systems="L T I C" ShowFrom="101"
ShowTo="1231" ChangeDate="2011-10-28T07:52:00">langer Test-Weg</Description>
<Description Id="360fec1a-5e78-4c84-a10c-7bc0fdba6b18" Type="InfrastructureOpeningTimes" Language="de" Systems="L T I C"
ShowFrom="101" ShowTo="1231" ChangeDate="2011-10-28T07:52:00">geöffnet</Description>
<Description Id="7d0525f8-2318-45e8-84fa-ec5b102f94e0" Type="InfrastructurePriceInfo" Language="en" Systems="L T I C"
ShowFrom="101" ShowTo="1231" ChangeDate="2016-08-26T13:35:00">TEST PRICE INFO</Description>
</Descriptions>
<Documents>
<Document Id="045647a8-14fd-4f53-914c-fc27efefbdb4" Type="Infrastructure" Class="Image" Systems="L T I C" Order="2"
ShowFrom="101" ShowTo="1231" Copyright="" Extension="jpg" ChangeDate="2010-08-12T20:05:00">
<Names>
<Translation Language="de">Shop</Translation>
<Translation Language="en">Shop</Translation>
</Names>
<URL>http://interfacetest.deskline.net/Handlers/Document?code=FRT&amp;id=045647a8-14fd-4f53-914c-fc27efefbdb4</URL>
</Document>
</Documents>
<Links>
<Link Id="f405f32f-7112-4f7a-9ce8-bd11f86450e8" Name="Homepage" URL="http://www.afrocoffee.com" ChangeDate="2010-08-
12T20:06:00" Type="1" Order="1" />
<Link Id="674870e3-9744-41e5-9eec-9498f4c69aaf" Name="AfroShop" URL="http://www.afrocoffee.com/shop/" ChangeDate="2010-08-
12T19:54:00" Type="0" Order="2" />
</Links>
<HotSpots ChangeDate="2009-10-01T14:17:00">
<HotSpot Id="35083ac1-fc57-4c9b-929d-ed5fe9f978a1" Distance="4.0" />
</HotSpots>
</InfrastructureItem>

CHECK FOR CHANGED INFRASTRUCTURES


To make data synchronization more efficient a check for changed infrastructures is given. So you can reduce
number of requests to a list of infrastructures which has changed data since a specific date and time. This is
part of basic data web service for infrastructures. Please note that delted items are not in response of this
request. Deleted items always have to be called with special DeletedItems request.

Check For Changed Infrastructures 87 of 241


DESKLINE 3.0 STANDARD INTERFACE

REQUEST
Request field Description Can be empty? Multiple?
Originator The code of the point of sale requesting the data.
Provided by feratel.
Company The code of the company requesting the data. Provided
by feratel.
Range and GUIDs First, a range code to select the data must be defined.
IDs This is an enumeration if it is a town (TO) or a district
(DI) for example. The IDs of towns/districts are part of
the KeyValues function. If there is a need to call data
owners (DO) directly, the IDs are provided by feratel.
The top location (i.e. highest/widest range possible) will
be provided by feratel to get started (see range
example in KeyValues.xml). Basic data requests should
be done at max per town or district, never per region
unless specifically defined by feratel.
Filters DateTimeFrom attribute occurs within the filter
DateTimeFrom element of the request and is inherited to all elements
requested. In this kind of request DateTimeFrom is a
Date Time field ("2011-05-18T09:30:00").
For example, it is possible to request all events that
were changed in the last twelve hours.
Filters When requesting basic data the Systems-Attribute must
Systems already be provided to filter only events which should
be shown online or internet-descriptions for example.
Example Systems=”T” for internet.
T…Internet
L…Local
I…Informator
C.. Catalogue
For multiple selection separate with a Space. Example
Systems = “L T”
Filters Enumeration: All/Active/Inactive. The default setting is
Infrastructure Status “Active”, so the interface only returns active
infrastructures. If it is necessary to know which
infrastructures were deactivated, the value All or
Inactive can be used. The Element <Active> is returned
on the details level of the response.
Filters For infrastructure related filters. Attribute is Status
ChangedInfrastructure (Enumeration: All, Active, Inactive) with default value
Active.
Filters The language filter must be used to provide which
Language(s) translations should be transferred inside the DSI
response. It’s possible to request more than one
language at the time to save the amounts of requests
necessary.
ChangedEvents <ChangedInfrastructures>
<Details />
<Documents />
<Descriptions />
<Links />
<Addresses />
<HotSpots />
<CustomAttributes />
<HandicapFacilities />

Check For Changed Infrastructures 88 of 241


DESKLINE 3.0 STANDARD INTERFACE

</ChangedInfrastructures>

EXAMPLE

Get list of changed infrastructures:


<?xml version="1.0" encoding="utf-8"?>
<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://interface.deskline.net/DSI/XSD">
<Request Originator="FERATEL" Company="FERATEL">
<Range Code="RG">
<Item Id="F180FFD5-4FBF-4F2C-AC00-7E8B94462F2C" />
</Range>
<BasicData>
<Filters DateTimeFrom="2013-01-01T08:00:00" Systems="T" >
<ChangedInfrastructure Status="All " />
<Languages>
<Language Value="de" />
<Language Value="en" />
</Languages>
</Filters>
<ChangedInfrastructures>
<Details />
<Documents />
<Descriptions />
<Links />
<Addresses />
<HotSpots />
<CustomAttributes />
<HandicapFacilities />
</ChangedInfrastructures>
</BasicData>
</Request>
</FeratelDsiRQ>

RESPONSE
Below is an example of a response with a list of Infrastructure IDs, which has changed data of any of elements
in the request. This list should be base for basic data request.

Response field Description Can be empty? Multiple?


ChangedInfrastructures List of Infrastructures were there were changes in the
requested elements within the specific time range
Id GUID of the infrastructure

Example

<?xml version="1.0" encoding="UTF-8"?>


<FeratelDsiRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" Status="0" Message="OK"
xmlns="http://interface.deskline.net/DSI/XSD">
<Result Index="1">
<ChangedInfrastructures >
<Infrastructure Id="c8bc5944-474b-41aa-88f4-054e8c4b9ed9" />
<Infrastructure Id="ea06184c-a6a1-4e19-acec-125e273c623a" />
<Infrastructure Id="77a7c00d-fc50-4e36-a7d8-4582116c0742" />
<Infrastructure Id="e970f557-4e47-4597-8ab6-5ddbdf8ba505" />
</ChangedInfrastructures >
</Result>
</FeratelDsiRS>

Check For Changed Infrastructures 89 of 241


DESKLINE 3.0 STANDARD INTERFACE

BASIC DATA FOR SHOP ITEMS (BROCHURES AND ARTICLES )


Shop Items like Brochures or Articles can be entered by customers and it’s possible to add brochures to a
shopping cart. In order to display the possible brochures there is an extra function to receive them in the basic
data. Articles are generally only available in the tourist office and not bookable online. They are however
transmitted in the interface if they need to be displayed as well.

Shop Items have a name and translations, a group, holiday themes, documents, descriptions – and variations.
This is new in Deskline 3.0: for example a customer can create the hiking guide brochure in two language
variations: one in German, one in English. Each variation can also have its own documents (e.g. cover) and
descriptions.

REQUEST
A request consists of three different parts: first, the mandatory values, then the optional filter and then the
definition, which elements to provide in the response.

Request field Description Can be empty? Multiple?


Originator The code of the point of sale requesting the data.
Provided by feratel.
Company The code of the company requesting the data. Provided
by feratel.
Range and GUIDs First, a range code to select the data must be defined.
IDs This is an enumeration if it is a region (RG) or a town (TO)
or a district (DI) for example. It is also possible to select
one or more data owners instead of a geographical
selection. The IDs of regions/towns/districts are part of
the KeyValues function. If there is a need to call data
owners (DO) directly, the IDs are provided by feratel. The
top location (i.e. highest/widest range possible) will be
provided by feratel to get started (see range example in
KeyValues.xml)
Filter: Languages The request must already include the languages that
should be returned upon one request for Shop Items.
Filter: ShopItem Type Enumeration: All (default), Brochure or Article
Filter: ShopItem Status Enumeration: Active (default), Inactive, All
ShopItems Details To receive details about the Shop Item. Parameter
DateFrom must be provided.
ShopItems Documents Parameter DateFrom must be provided. Also, the
Systems Enumeration must be filled. E.g. Systems=”T” to
get all documents that should be displayed online.
ShopItems Descriptions Parameter DateFrom must be provided. Also, the
Systems Enumeration must be filled. E.g. Systems=”T” to
get all descriptions that should be displayed online.
Descriptions Enum: true/false default: false
Markup when you set the optional attribute Markup=”true” you
get back html format tags which might be selected from
the customers.
ShopItems Links Parameter DateFrom must be provided.
ShopItems Variations Variations are a new form of brochures. E.g. a brochure
like “hiking guide” can exist in two variations: one in
German as “Wanderführer” with its own cover and one in
English as “Hiking guide” with its own cover. To receive
the details about variations, the parameter DateFrom

Basic Data For Shop Items (Brochures and Articles) 90 of 241


DESKLINE 3.0 STANDARD INTERFACE

must be provided.
Variation Details Parameter DateFrom must be provided.
Variation Documents Parameter DateFrom must be provided. Also, the
Systems Enumeration must be filled. E.g. Systems=”T” to
get all documents that should be displayed online.
Variation Descriptions Parameter DateFrom must be provided. Also, the
Systems Enumeration must be filled. E.g. Systems=”T” to
get all descriptions that should be displayed online.
Descriptions Enum: true/false default: false
Markup when you set the optional attribute Markup=”true” you
get back html format tags which might be selected from
the customers.
Variation Links Parameter DateFrom must be provided.

EXAMPLE

Get all brochures details:


<?xml version="1.0" encoding="utf-8"?>
<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://interface.deskline.net/DSI/XSD">
<Request Originator="FERATEL" Company="xxx">
<Range Code="RG">
<Item Id="xxx" />
</Range>
<BasicData>
<Filters>
<ShopItem Type="Brochure" />
<Languages>
<Language Value="de" />
<Language Value="en" />
</Languages>
</Filters>
<ShopItems>
<Details DateFrom="1980-01-01" />
<Documents DateFrom="1980-01-01" Systems="T" />
<Descriptions DateFrom="1980-01-01" Systems="T” Markup="true" />
<Links DateFrom="1980-01-01" />
<Variations>
<Details DateFrom="1980-01-01" />
<Documents DateFrom="1980-01-01" Systems="T" />
<Descriptions DateFrom="1980-01-01" Systems="T" Markup="true" />
</Variations>
</ShopItems>
</BasicData>
</Request>
</FeratelDsiRQ>

RESPONSE
Response field Description Can be empty? Multiple?
Name Name in different requested languages
Type Brochure or Article
Status True or false
Order Order inside the brochures

Basic Data For Shop Items (Brochures and Articles) 91 of 241


DESKLINE 3.0 STANDARD INTERFACE

Owner Code of Data-Owner responsible for this item. Use as


settler code in case of order.
Group ID ID of the group for this shop item. See function
ShopItemGroups in the KeyValues for the translations.
HolidayThemes e.g. Weekend, Wedding, Family, etc..
ShowOnWeb true/false if the shop item should be available online or
not.
DatabaseCode Database code, necessary when creating a shopping cart.
Documents (for item Documents can be images, videos, PDF-files, etc. For each
and variations) document, the URL will be provided the image can then
be downloaded into an external database. The URL will
return the original uploaded file by the user, not a resized
or otherwise manipulated version. It is also possible that
documents have different names in different languages,
hence the translations. In addition there is also a
copyright note for each document if necessary. Each
document can either have a From-To timeframe (only
day/month, not year) or can be set to be shown as
“always” in which case From-To is send as “101”-“1231”
in the element. Documents can also be set to only be
available for different output systems such as: local
(Deskline 3.0 backend), internet presentation, Informator
or catalog productions. When requesting basic data the
Systems-Attribute must already be provided to filter only
internet-documents for example. The extension is part of
the response.
Links (for item and There is a URL, name, type and order for each link
variations) address connected to the parent. Type categorizes the
link in different groups. E.g. Object URL for homepage
Descriptions (for item Descriptions in various languages. Each description can
and variations) either have a From-To timeframe (only day/month, not
year) or can be set to be shown as “always” in which case
From-To is send as “101”-“1231” in the element.
Descriptions can also be set to only be available for
different output systems such as: local (Deskline 3.0
backend), internet presentation, Informator or catalog
productions. When requesting basic data the Systems-
Attribute must already be provided to filter only internet-
descriptions for example.
Type=Article only: Name in different requested languages.
Variation Details Names
Type=Article only: Price of the article.
Variation Details Price
Type=Brochure only: Language code of brochure variation to find out the
Variation Details different languages a brochure is available in.
Language
Variation Details Code Internal Code of the Variation, not used online

Example:

<?xml version="1.0"?>
<FeratelDsiRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
Status="0" Message="OK" xmlns="http://interface.deskline.net/DSI/XSD">
<Result Index="1">
<ShopItems>

Basic Data For Shop Items (Brochures and Articles) 92 of 241


DESKLINE 3.0 STANDARD INTERFACE

<ShopItem Id="75d36b3f-dca5-4616-87fc-ecedd9d1359c">
<Details>
<Names>
<Translation Language="de">testprospekt schn</Translation>
<Translation Language="en">testprospekt schn</Translation>
</Names>
<Type>Brochure</Type>
<Active>true</Active>
<Order>1</Order>
<Owner>FERATEL</Owner>
<Group Id="c5a9ca6e-b1a8-4130-9457-371ee0ab4efb" />
<HolidayThemes>
<Item Id="090A18AE-5D50-421E-A65A-C5A2B8227AE5" />
</HolidayThemes>
</Details>
<Documents>
<Document Id="372c103e-2e70-4104-9fb1-8e1821bd7d88"
Type="ShopItem" Class="Document" Systems="L T I C" Order="1" ShowFrom="101" ShowTo="1231" Copyright=""
Extension="pdf" ChangeDate="2010-06-02T10:27:00">
<Names>
<Translation Language="de">test</Translation>
<Translation Language="en">test</Translation>
</Names>

<URL>http://interfacetest.deskline.net/Handlers/Document?code=FRT&amp;id=372c103e-2e70-4104-9fb1-
8e1821bd7d88</URL>
</Document>
</Documents>
<Variations>
<Variation Id="a76cb89d-2be0-4126-895c-8a6b56cfbcfb">
<Details>
<Names>
<Translation
Language="de">de</Translation>
<Translation
Language="en">de</Translation>
</Names>
<Code>TPS</Code>
</Details>
</Variation>
</Variations>
</ShopItem>
</ShopItems>
</Result>
</FeratelDsiRS>

Basic Data For Shop Items (Brochures and Articles) 93 of 241


DESKLINE 3.0 STANDARD INTERFACE

BASIC DATA FOR DESTINATION PACKAGES


A bundle of different services and products is called destination package. The destination defines the bundle of
products and is responsible for this package.

STRUCTURE OF A DESTINATION PACKAGE


First a short overview how data regarding a destination package is entered and connected in Deskline 3.0 is
given. There are general details like the name and meeting points, which can have translations and wether the
package is active or not, its priority and the owner, the organization which is responsible for this offer.

Each package has to have at least one period in which it is valid. For each period it is possible to set different
prices.

One or more holiday themes can be checked for a package equal to them on product level.

Each package has at least one category. Each category has an order, a name, which can be translated, and a
meal. The price from is only for orientation, this information is not used for price calculation.

General settings of a package includes the price settings, durations, possible occupancies and if package is part
of a package group or not.

Basic Data For Destination Packages 94 of 241


DESKLINE 3.0 STANDARD INTERFACE

There are four different settings which affects the price structure:

1. Price per Person and Fixed Price per Category

In this case sell prices are entered on package level like this:

Per Period and per Category and per Duration days you enter sell prices and sell price for additional
nights for single adult and child categories.

Interface output looks like this:

<Package Id="" ChangeDate="" >



<Prices>
<Price DateFrom="" DateTo="" CategoryId="" Duration="" >
<PriceValue Type="AdultSingle" SalesPrice="" AdditionalNight=""/>
<PriceValue Type="Adults" SalesPrice="" AdditionalNight=""/>
<PriceValue Type="Children" AgeFrom="" AgeTo="" SalesPrice="" AdditionalNight="" />
</Price>
<Price DateFrom="" DateTo="" CategoryId="" Duration="" SalesPrice="" AdditionalNight="">
<PriceValue Type="AdultSingle" SalesPrice="" AdditionalNight=""/>
<PriceValue Type="Adults" SalesPrice="" AdditionalNight=""/>
<PriceValue Type="Children" AgeFrom="" AgeTo="" SalesPrice="" AdditionalNight="" />
</Price>
</Prices>

</Package>

Basic Data For Destination Packages 95 of 241


DESKLINE 3.0 STANDARD INTERFACE

2. Price per Package and Fixed Price per Category

Prices are entered on package level, no extra prices for persons needed

Output on interface looks like this:

<Package Id="" ChangeDate="" >



<Prices>
<Price DateFrom="" DateTo="" CategoryId="" Duration="" SalesPrice="" AdditionalNight="" />
<Price DateFrom="" DateTo="" CategoryId="" Duration="" SalesPrice="" AdditionalNight=""/>
</Prices>

</Package>

3. Price per Person and Dynamic Price

If price is dynamic it cannot be entered on package level, it has to be entered on sections level.
Window looks the same like on Package level, but is on sections level.

Basic Data For Destination Packages 96 of 241


DESKLINE 3.0 STANDARD INTERFACE

Interface output would look like this:

<Package Id="" ChangeDate="" >



<Sections>
<Section Id="" ChangeDate="">

<Prices>
<Price DateFrom="" DateTo="" CategoryId="" Duration="" >
<PriceValue Type="AdultSingle" SalesPrice="" AdditionalNight=""/>
<PriceValue Type="Adults" SalesPrice="" AdditionalNight=""/>
<PriceValue Type="Children" AgeFrom="" AgeTo="" SalesPrice="" AdditionalNight="" />
</Price>
<Price DateFrom="" DateTo="" CategoryId="" Duration="">
<PriceValue Type="AdultSingle" SalesPrice="" AdditionalNight=""/>
<PriceValue Type="Adults" SalesPrice="" AdditionalNight=""/>
<PriceValue Type="Children" AgeFrom="" AgeTo="" SalesPrice="" AdditionalNight="" />
</Price>
</Prices>

</Section>
</Sections>

</Package>

4. Price per Package and Dynamic Price

If price is dynamic it cannot be entered on package level, it has to be entered on sections level per
Package. Window looks the same like on Package level if prices are per Package, but is on sections
level.

<Package Id="" ChangeDate="" >



<Sections>
<Section Id="" ChangeDate="">

<Price DateFrom="" DateTo="" CategoryId="" Duration="" SalesPrice="" AdditionalNight="" />
<Price DateFrom="" DateTo="" CategoryId="" Duration="" SalesPrice="" AdditionalNight=""/>

Basic Data For Destination Packages 97 of 241


DESKLINE 3.0 STANDARD INTERFACE

</Section>
</Sections>

</Package>

Sections:

A package consists of at least one section, which makes it possible to group products e.g. one accommodation
section and one section for an additional service like rent a ski. Sections can be optional.

Sections have a name, type and order. They can have different durations from the package itself. E.g. 4 days
package with a section “Rent a ski” for 3 days. Also they can have dependencies on other sections and
limitations concerning the amount.

If a section is optional it has its own prices, also if Fixed Price is selected. Output is the same as for Dynamic
Prices on Section level (two different ways: for Per Person and for Per Package).

Each Section has assigned Products:

Basic Data For Destination Packages 98 of 241


DESKLINE 3.0 STANDARD INTERFACE

OVERVIEW
Packages get split into the following parts:

 Details
 Description
 Documents
 Links
 Prices
 ContentDescription
 Sections

And Sections are also separated into:


 Details
 Description
 Prices
 Products
o Availability
o Prices

This overview structure is used for request and for response.

REQUEST
A request consists of three different parts: first, the mandatory values, then the optional filter and then the
definition, which elements to provide in the response.

Request field Description Can be empty? Multiple?


Originator The code of the point of sale requesting the data.
Provided by feratel.
Company The code of the company requesting the data. Provided
by feratel.
Range and GUIDs First, a range code to select the data must be defined.
IDs This is an enumeration if it is a region (RG) or a town (TO)
or a district (DI) for example. It is also possible to select
one or more data owners instead of a geographical
selection. The IDs of regions/towns/districts are part of
the KeyValues function. If there is a need to call data
owners (DO) directly, the IDs are provided by feratel. The
top location (i.e. highest/widest range possible) will be
provided by feratel to get started (see range example in
KeyValues.xml)
Filters Request on Packages can be filtered to a specific Sales

Basic Data For Destination Packages 99 of 241


DESKLINE 3.0 STANDARD INTERFACE

Channel.
Filters: Packages There is the possibility to filter the Status. Therefore set
the attribute Status to Active, Inactive or All. Active is
default. Also you can request only packages within a
specific time period, therfore set From and To with the
required date. These parameters are optional
Filters: Languages The request must already include the languages that
should be returned upon one request for Shop Items.
HolidayThemes Basic data request for packages can be limited to provide
only packages that are related to a specific holiday
theme. The list of these IDs is provided in the Key Values
Function.
Package Details To receive details about the Package. Parameter
DateFrom must be provided.
Package Descriptions Parameter DateFrom must be provided. Also, the
Systems Enumeration must be filled. E.g. Systems=”T” to
get all descriptions that should be displayed online.
Description Enum: true/false default: false
Markup when you set the optional attribute Markup=”true” you
get back html format tags which might be selected from
the customers.
Package Documents Parameter DateFrom must be provided. Also, the
Systems Enumeration must be filled. E.g. Systems=”T” to
get all documents that should be displayed online.
Package Links Parameter DateFrom must be provided.
Package Prices Parameter DateFrom must be provided.
Package Parameter DateFrom must be provided. Also, the
ContentDescriptions Systems Enumeration must be filled. E.g. Systems=”T” to
get all content descriptions that should be displayed
online.
Description Enum: true/false default: false
Markup when you set the optional attribute Markup=”true” you
get back html format tags which might be selected from
the customers.
Package Sections To request list of sections
Section Detail Parameter DateFrom must be provided.
Section Descriptions Parameter DateFrom must be provided. Also, the
Systems Enumeration must be filled. E.g. Systems=”T” to
get all documents that should be displayed online.
Section Prices Parameter DateFrom must be provided.
Section Products Parameter DateFrom must be provided.
Product Availabilities Parameter DateFrom must be provided.
Product Prices Parameter DateFrom must be provided.
Package Sections Coming soon…

EXAMPLE
Get all package details:
<?xml version="1.0" encoding="utf-8"?>
<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://interface.deskline.net/DSI/XSD">
<Request Originator="FERATEL" Company="FERATEL">
<Range Code="RG">
<Item Id="F180FFD5-4FBF-4F2C-AC00-7E8B94462F2C" />
</Range>

Basic Data For Destination Packages 100 of 241


DESKLINE 3.0 STANDARD INTERFACE

<BasicData>
<Filters SalesChannelId="BB556229-E7B1-4F21-9C6A-2BEA7120BF5A">
<Packages Status="Active" From="" To=""/>
<Languages>
<Language Value="de" />
<Language Value="en" />
</Languages>
<HolidayThemes>
<Item Id="DC26D00A-1B99-4C7C-A09A-AFC16578C144" />
<Item Id="25F0588A-A040-48C4-A555-FA18D17A134E" />
</HolidayThemes>
</Filters>
<Packages>
<Details DateFrom="1980-01-01" />
<Documents DateFrom="1980-01-01" Systems="T" />
<Descriptions DateFrom="1980-01-01" Systems="T" Markup="true" />
<Links DateFrom="1980-01-01" />
<Prices DateFrom="1980-01-01" />
<ContentDescriptions DateFrom="1980-01-01" Systems="T" />
<Sections>
<Details DateFrom="1980-01-01" />
<Descriptions DateFrom="1980-01-01" Systems="T" Markup="true" />
<Prices DateFrom="1980-01-01" />
<Products>
<Availabilities DateFrom="1980-01-01" />
<Prices DateFrom="1980-01-01" />
</Products>
</Sections>
</Packages>
</BasicData>
</Request>
</FeratelDsiRQ>

RESPONSE
Below is an example of a full response of package with all elements and attributes possible. Mind that based on
the request it’s possible that not all of these elements are part of the response. For details on the data types
and XML enumerations refer to the XSD documents.

Package:

Response field Description Can be empty? Multiple?


ID GUID of the package
ChangeDate Date/time indicator when the item was last changed.
Name List of names of the package in requested languages
Priority Number to define the priority in lists, to allow
customers their own sort order
MeetingPoint List of Meeting Points of the package in requested
languages
HolidayThemes e.g. Weekend, Wedding, Family, etc..
Active Indicates if the package is active or not.
Bookable Indicates if the package is bookable or not.
Bookable Attribute DaysBookingStops shows the number of days
DaysBookingStops before arrival a booking is allowed.
DBCode 3 letter code of the database. This is also part of the
search response and is used for adding items to the
shopping cart and for generating a direct link.
Position Latitude, GPS Coordinates

Basic Data For Destination Packages 101 of 241


DESKLINE 3.0 STANDARD INTERFACE

Longitude
ValidDates List of periods in which the package is offerable
PackageCategories List of categories of the package container including Id
Order and PriceFrom as well as name in all requested
languages
Settings Element which contains several general settings
concerning the package
Owner Organisation code of the data owner of this package
PriceSettings PriceType can be perPerson or prepackage and
PackagePrice can be Dynamic or Fixed, for details see
structure of a destination package
PackageDuration Defines the duration of a package in days (3 days
means 2 nights) and the possible days, when a package
can be (list of days ture or false)
Occupancy Defines the possible occupancies in generl for adults
and children
ChildAgeGroup List of different defined age groups of children. Same
groups are used for definition of prices
Calculation Includes the information if booking fee is already
included in the price or not and the value
Documents Documents can be images, videos, PDF-files, etc. For
each document, the URL will be provided the image can
then be downloaded into an external database. The
URL will return the original uploaded file by the user,
not a resized or otherwise manipulated version. It is
also possible that documents have different names in
different languages, hence the translations. In addition
there is also a copyright note for each document if
necessary. Each document can either have a From-To
timeframe (only day/month, not year) or can be set to
be shown as “always” in which case From-To is send as
“101”-“1231” in the element. Documents can also be
set to only be available for different output systems
such as: local (Deskline 3.0 backend), internet
presentation, Informator or catalog productions. When
requesting basic data the Systems-Attribute must
already be provided to filter only internet-documents
for example. The extension is part of the response.
Descriptions Descriptions in various languages. Each description can
either have a From-To timeframe (only day/month, not
year) or can be set to be shown as “always” in which
case From-To is send as “101”-“1231” in the element.
Line-breaks are not converted to HTML-line-breaks, the
description will be returned as entered in the system.
Descriptions can also be set to only be available for
different output systems such as: local (Deskline 3.0
backend), internet presentation, Informator or catalog
productions. When requesting basic data the Systems-
Attribute must already be provided to filter only
internet-descriptions for example.
Links There is a URL, name, type and order for each link
address connected to the parent. Type categorizes the
link in different groups. E.g. Object URL for homepage
Prices Price structure is different according to the price
settings, for details see structure of a destination

Basic Data For Destination Packages 102 of 241


DESKLINE 3.0 STANDARD INTERFACE

package
ContentDescription In general same logic as Descriptions, but different
format. Types are PackageContentShort and
PackageContentLong. List of content plus optional title
called IntroText

EXAMPLE PACKAGE
Package:
<?xml version="1.0" encoding="utf-8"?>
<FeratelDsiRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
Status="0" Message="OK" xmlns="http://interface.deskline.net/DSI/XSD">
<Result Index="1">
<Packages>
<Package Id="61ff04c2-9bf0-40b5-8bca-d86e4eb938ca" ChangeDate="2011-07-12T16:00:00">
<Details>
<Name>
<Translation Language="de">SchnittstellenKonzept</Translation>
<Translation Language="en">InterfaceConcept</Translation>
</Name>
<Priority>99</Priority>
<MeetingPoint>
<Translation Language="de">Beim Baum</Translation>
<Translation Language="en">At the Tree</Translation>
</MeetingPoint>
<HolidayThemes>
<Item Id="BD369B0E-AD82-47E6-902A-101917331660" />
</HolidayThemes>
<Active>true</Active>
<Bookable>false</Bookable>
<DBCode>FRT</DBCode>
<Position Latitude="0" Longitude="0" />
<ValidDates Type="Period">
<ValidDate From="2010-12-15" To="2011-12-31" />
</ValidDates>
<Settings>
<PriceSettings PriceType="perPerson" PackagePrice="perCategory" />
<PackageDuration>
<DurationDays Days="3" Mon="false" Tue="false" Wed="false" Thu="false" Fri="true" Sat="true" Sun="true" />
<DurationDays Days="4" Mon="true" Tue="true" Wed="true" Thu="true" Fri="false" Sat="false" Sun="false" />
</PackageDuration>
<Occupancy>
<Beds Min="2" Max="4" />
<Adults Min="2" Max="4" />
<Children Min="0" Max="2" />
</Occupancy>
<ChildAgeGroups>
<ChildAgeGroup AgeFrom="1" AgeTo="7" />
<ChildAgeGroup AgeFrom="8" AgeTo="15" />
</ChildAgeGroups>
<Calculation>
<BookingFee Included="false" Value="0.00" />
</Calculation>
</Settings>
<Owner>FERATEL</Owner>
</Details>
<Descriptions>
<Description Id="a265eabb-e4f5-42a1-8d4f-12d340455988" Type="Package" Language="de" Systems="L T I C"
ShowFrom="101" ShowTo="1231" ChangeDate="2011-07-12T15:54:00">Description German 1</Description>
<Description Id="c6f26c4f-d944-4a6d-b889-50db7a866e67" Type="PackageShortText" Language="de" Systems="L T I C"
ShowFrom="101" ShowTo="1231" ChangeDate="2011-07-12T15:55:00">Short Description 1</Description>
<Description Id="3294f200-8e8d-463e-a6c2-66e56e3b1319" Type="Package" Language="en" Systems="L T I C"
ShowFrom="101" ShowTo="1231" ChangeDate="2011-07-12T15:55:00">Description English 1</Description>
</Descriptions>
<Documents>
<Document Id="919af4e6-7145-48ce-ae9a-89f667cb8c24" Type="Package" Class="Image" Systems="L T I C" Order="1"
ShowFrom="101" ShowTo="1231" Copyright="" Extension="jpg" ChangeDate="2011-07-12T15:55:00">
<Names>

Basic Data For Destination Packages 103 of 241


DESKLINE 3.0 STANDARD INTERFACE

<Translation Language="de">Picture 1</Translation>


<Translation Language="en">Picture 1</Translation>
</Names>
<URL>http://interfacetest.deskline.net/Handlers/Document?code=FRT&amp;id=919af4e6-7145-48ce-ae9a-
89f667cb8c24</URL>
</Document>
<Document Id="cc7eeb1b-fdb9-4203-84dc-6c8739353517" Type="Package" Class="Image" Systems="L T I C" Order="2"
ShowFrom="101" ShowTo="1231" Copyright="" Extension="jpg" ChangeDate="2011-07-12T15:55:00">
<Names>
<Translation Language="de">Picture 2</Translation>
<Translation Language="en">Picture 2</Translation>
</Names>
<URL>http://interfacetest.deskline.net/Handlers/Document?code=FRT&amp;id=cc7eeb1b-fdb9-4203-84dc-
6c8739353517</URL>
</Document>
</Documents>
<Links>
<Link Id="2a13dff3-2492-4287-8558-9fc9d6cc358e" Name="Feratel com" URL="http://feratel.com" ChangeDate="2011-
07-12T15:56:00" Type="0" Order="1" />
<Link Id="156b9c4e-02e0-427c-82b3-43fb193c66f2" Name="Feratel at" URL="http://www.feratel.at"
ChangeDate="2011-07-12T15:56:00" Type="0" Order="2" />
</Links>
<Prices>
<Price DateFrom="2010-12-15" DateTo="2011-12-31" CategoryId="b0e29d1e-aa8b-49be-bc64-1005e67b4fd4"
Duration="4">
<PriceValue Type="Children" AgeFrom="1" AgeTo="7" SalesPrice="120" AdditionalNight="0.00" />
<PriceValue Type="Children" AgeFrom="8" AgeTo="15" SalesPrice="250" AdditionalNight="0.00" />
<PriceValue Type="Adults" SalesPrice="400" AdditionalNight="0.00" />
</Price>
<Price DateFrom="2010-12-15" DateTo="2011-12-31" CategoryId="b0e29d1e-aa8b-49be-bc64-1005e67b4fd4"
Duration="3">
<PriceValue Type="Children" AgeFrom="1" AgeTo="7" SalesPrice="100" AdditionalNight="0.00" />
<PriceValue Type="Children" AgeFrom="8" AgeTo="15" SalesPrice="200" AdditionalNight="0.00" />
<PriceValue Type="Adults" SalesPrice="300" AdditionalNight="0.00" />
</Price>
<Price DateFrom="2010-12-15" DateTo="2011-12-31" CategoryId="aa695b63-0a83-4118-9d82-c9fd08679e2c"
Duration="3">
<PriceValue Type="Children" AgeFrom="1" AgeTo="7" SalesPrice="100" AdditionalNight="0.00" />
<PriceValue Type="Adults" SalesPrice="300" AdditionalNight="0.00" />
<PriceValue Type="Children" AgeFrom="8" AgeTo="15" SalesPrice="200" AdditionalNight="0.00" />
</Price>
<Price DateFrom="2010-12-15" DateTo="2011-12-31" CategoryId="aa695b63-0a83-4118-9d82-c9fd08679e2c"
Duration="4">
<PriceValue Type="Children" AgeFrom="1" AgeTo="7" SalesPrice="120" AdditionalNight="0.00" />
<PriceValue Type="Children" AgeFrom="8" AgeTo="15" SalesPrice="250" AdditionalNight="0.00" />
<PriceValue Type="Adults" SalesPrice="400" AdditionalNight="0.00" />
</Price>
<Price DateFrom="2010-12-15" DateTo="2011-12-31" CategoryId="b16d230f-d63e-447a-b3b1-d895dc146470"
Duration="4">
<PriceValue Type="Children" AgeFrom="8" AgeTo="15" SalesPrice="220" AdditionalNight="0.00" />
<PriceValue Type="Children" AgeFrom="1" AgeTo="7" SalesPrice="100" AdditionalNight="0.00" />
<PriceValue Type="Adults" SalesPrice="300" AdditionalNight="0.00" />
</Price>
<Price DateFrom="2010-12-15" DateTo="2011-12-31" CategoryId="b16d230f-d63e-447a-b3b1-d895dc146470"
Duration="3">
<PriceValue Type="Children" AgeFrom="1" AgeTo="7" SalesPrice="80" AdditionalNight="0.00" />
<PriceValue Type="Children" AgeFrom="8" AgeTo="15" SalesPrice="150" AdditionalNight="0.00" />
<PriceValue Type="Adults" SalesPrice="250" AdditionalNight="0.00" />
</Price>
</Prices>
<ContentDescriptions>
<ContentDescription Id="0f7ee1dc-daaf-4d1d-9263-ce0cda4f99ce" Type="PackageContentShort" Language="de"
Systems="L T I C" ShowFrom="101" ShowTo="1231" ChangeDate="2014-03-27T14:56:00">
<IntroText />
<Items>
<Item>2 Übernachtung</Item>
<Item>1 Bungee Sprung</Item>
</Items>
</ContentDescription>
<ContentDescription Id="0212f2f3-c3eb-43b7-ad92-e9ed65fc8cbb" Type="PackageContentLong" Language="de"

Basic Data For Destination Packages 104 of 241


DESKLINE 3.0 STANDARD INTERFACE

Systems="L T I C" ShowFrom="101" ShowTo="1231" ChangeDate="2014-03-27T14:56:00">


<IntroText>In unser Superpauschale sind enthalten...</IntroText>
<Items>
<Item>2 Übernachtung</Item>
<Item>1 Bungee Sprung</Item>
</Items>
</ContentDescription>
</ContentDescriptions>
</Package>
<Package Id="a9fd13d6-8dce-4e48-946a-eb0e6f449977" ChangeDate="2010-12-15T11:28:00">
<Details>
<Name>
<Translation Language="de">Winter Spezial</Translation>
<Translation Language="en">Winter-Special</Translation>
</Name>
<Priority>99</Priority>
<MeetingPoint>
<Translation Language="de" />
<Translation Language="en" />
</MeetingPoint>
<HolidayThemes>
<Item Id="3D7B461A-DDAC-4CDD-A1CD-76A370807D13" />
<Item Id="4CA469F6-F84D-449D-AB5C-39C45200139B" />
</HolidayThemes>
<Active>true</Active>
<Bookable>false</Bookable>
<DBCode>FRT</DBCode>
<Position Latitude="47.2904079381293" Longitude="15.4385375976563" />
<ValidDates Type="Period">
<ValidDate From="2011-01-09" To="2011-02-03" />
</ValidDates>
<Settings>
<PriceSettings PriceType="perPerson" PackagePrice="perCategory" />
<PackageDuration>
<DurationDays Days="3" Mon="false" Tue="false" Wed="false" Thu="true" Fri="true" Sat="true" Sun="false" />
<DurationDays Days="4" Mon="true" Tue="true" Wed="true" Thu="false" Fri="false" Sat="false" Sun="true" />
</PackageDuration>
<Occupancy>
<Beds Min="2" Max="4" />
<Adults Min="2" Max="2" />
<Children Min="0" Max="2" />
</Occupancy>
<ChildAgeGroups>
<ChildAgeGroup AgeFrom="0" AgeTo="2" />
<ChildAgeGroup AgeFrom="3" AgeTo="5" />
<ChildAgeGroup AgeFrom="6" AgeTo="10" />
<ChildAgeGroup AgeFrom="11" AgeTo="12" />
</ChildAgeGroups>
<Calculation>
<BookingFee Included="false" Value="0.00" />
</Calculation>
</Settings>
<Owner>FERATEL</Owner>
</Details>
<Descriptions>
<Description Id="e188a5b9-b027-4ff4-9e8a-94bd3461da94" Type="Package" Language="de" Systems="L T I C"
ShowFrom="101" ShowTo="1231" ChangeDate="2010-12-15T11:39:00">
Ruhe, unberührte Natur, beruhigende Landschaften, gesunde Luft, klares Wasser, ein umfassendes Wellnessangebot im
Hotel, heimische Spezialitäten aus eigenen Gewässern und der Alm. Ausgezeichnete steirische Weine aus dem eigenen
Weingut in Gamlitz fehlen natürlich auch nicht. Dies sind die Voraussetzungen für Ihren erholsamen und kraftgebenden Urlaub,
der auch Wirkung zeigt, wenn man nur ein paar Tage bleibt.
1 x geführte Wanderung auf den Hochlantsch mit Yogaübungen beim Gipfelkreuz
1 x Morgenwanderung mit Sonnenaufgang zur Sinneswahrnehmung
1 x Almyoga mit Pranayamaübungen (Atem- und Energieübungen)
1 x Schneeschuhwanderung auf den Heulantsch mit heißem Punsch am Gipfelkreuz
1 x Atemmeditation
1 x Tiefenentspannung "Traumreise ins Regenbogenland"
1 x Meditation "für ein glückliches und gesundes Herz"
1 x Entspannungsmassage mit ätherischen Ölen (ca. 25 Min.)
1 x Tremo-Flex-Anwendung (ca. 30 Min.)

Basic Data For Destination Packages 105 of 241


DESKLINE 3.0 STANDARD INTERFACE

1 x Almwohlfühlbad in der Whirlwanne "Wintertraum"


1 x Teeverkostung
1 x "Almenlandkräutertee" für Zuhause
Diverse Yogastunden mit verschiedenen Schwerpunkten
</Description>
<Description Id="783b782b-e138-4f19-8c19-a5191442ee96" Type="PackageShortText" Language="de" Systems="L T I C"
ShowFrom="101" ShowTo="1231" ChangeDate="2010-12-15T11:41:00">
Ruhe, unberührte Natur, beruhigende Landschaften, gesunde Luft, klares Wasser, ein umfassendes Wellnessangebot im
Hotel, heimische Spezialitäten aus eigenen Gewässern und der Alm. Ausgezeichnete steirische Weine aus dem eigenen
Weingut in Gamlitz fehlen natürlich auch nicht. Dies sind die Voraussetzungen für Ihren erholsamen und kraftgebenden Urlaub,
der auch Wirkung zeigt, wenn man nur ein paar Tage bleibt.
</Description>
</Descriptions>
<Documents>
<Document Id="d6e0f720-1c85-4a6b-a0bb-617250d3bf26" Type="Package" Class="Image" Systems="L T I C" Order="1"
ShowFrom="101" ShowTo="1231" Copyright="" Extension="jpg" ChangeDate="2010-12-15T11:37:00">
<Names>
<Translation Language="de">Winter-Special</Translation>
<Translation Language="en">Winter-Special</Translation>
</Names>
<URL>http://interfacetest.deskline.net/Handlers/Document?code=FRT&amp;id=d6e0f720-1c85-4a6b-a0bb-
617250d3bf26</URL>
</Document>
<Document Id="4a97b297-aee9-485a-b5a0-39a790c9383b" Type="Package" Class="Image" Systems="L T I C" Order="2"
ShowFrom="101" ShowTo="1231" Copyright="" Extension="jpg" ChangeDate="2010-12-15T11:38:00">
<Names>
<Translation Language="de">Planschen</Translation>
<Translation Language="en">Planschen</Translation>
</Names>
<URL>http://interfacetest.deskline.net/Handlers/Document?code=FRT&amp;id=4a97b297-aee9-485a-b5a0-
39a790c9383b</URL>
</Document>
<Document Id="c996de84-bee6-4616-9d84-2ae5bc42b50b" Type="Package" Class="Image" Systems="L T I C" Order="3"
ShowFrom="101" ShowTo="1231" Copyright="" Extension="jpg" ChangeDate="2010-12-15T11:38:00">
<Names>
<Translation Language="de">Alternative Sportarten</Translation>
<Translation Language="en">Alternative Sportarten</Translation>
</Names>
<URL>http://interfacetest.deskline.net/Handlers/Document?code=FRT&amp;id=c996de84-bee6-4616-9d84-
2ae5bc42b50b</URL>
</Document>
</Documents>
<Prices>
<Price DateFrom="2011-01-09" DateTo="2011-02-03" CategoryId="143deaa7-f190-4141-8b4b-a7e43f8f55dc"
Duration="4">
<PriceValue Type="Children" AgeFrom="3" AgeTo="5" SalesPrice="220" AdditionalNight="20.00" />
<PriceValue Type="Adults" SalesPrice="490" AdditionalNight="90.00" />
<PriceValue Type="Children" AgeFrom="11" AgeTo="12" SalesPrice="460" AdditionalNight="80.00" />
<PriceValue Type="Children" AgeFrom="6" AgeTo="10" SalesPrice="420" AdditionalNight="40.00" />
<PriceValue Type="Children" AgeFrom="0" AgeTo="2" SalesPrice="40" AdditionalNight="0.00" />
</Price>
<Price DateFrom="2011-01-09" DateTo="2011-02-03" CategoryId="143deaa7-f190-4141-8b4b-a7e43f8f55dc"
Duration="3">
<PriceValue Type="Children" AgeFrom="6" AgeTo="10" SalesPrice="180" AdditionalNight="40.00" />
<PriceValue Type="Children" AgeFrom="11" AgeTo="12" SalesPrice="320" AdditionalNight="70.00" />
<PriceValue Type="Children" AgeFrom="3" AgeTo="5" SalesPrice="70" AdditionalNight="20.00" />
<PriceValue Type="Children" AgeFrom="0" AgeTo="2" SalesPrice="30" AdditionalNight="0.00" />
<PriceValue Type="Adults" SalesPrice="390" AdditionalNight="90.00" />
</Price>
<Price DateFrom="2011-01-09" DateTo="2011-02-03" CategoryId="1ce4c568-d550-41c2-b25d-efcf8e66691e"
Duration="3">
<PriceValue Type="Adults" SalesPrice="460" AdditionalNight="110.00" />
<PriceValue Type="Children" AgeFrom="11" AgeTo="12" SalesPrice="390" AdditionalNight="90.00" />
<PriceValue Type="Children" AgeFrom="6" AgeTo="10" SalesPrice="210" AdditionalNight="50.00" />
<PriceValue Type="Children" AgeFrom="3" AgeTo="5" SalesPrice="90" AdditionalNight="20.00" />
<PriceValue Type="Children" AgeFrom="0" AgeTo="2" SalesPrice="45" AdditionalNight="0.00" />
</Price>
<Price DateFrom="2011-01-09" DateTo="2011-02-03" CategoryId="1ce4c568-d550-41c2-b25d-efcf8e66691e"
Duration="4">
<PriceValue Type="Children" AgeFrom="6" AgeTo="10" SalesPrice="500" AdditionalNight="50.00" />

Basic Data For Destination Packages 106 of 241


DESKLINE 3.0 STANDARD INTERFACE

<PriceValue Type="Children" AgeFrom="3" AgeTo="5" SalesPrice="280" AdditionalNight="20.00" />


<PriceValue Type="Children" AgeFrom="11" AgeTo="12" SalesPrice="520" AdditionalNight="90.00" />
<PriceValue Type="Children" AgeFrom="0" AgeTo="2" SalesPrice="60" AdditionalNight="0.00" />
<PriceValue Type="Adults" SalesPrice="570" AdditionalNight="110.00" />
</Price>
<Price DateFrom="2011-01-09" DateTo="2011-02-03" CategoryId="007ef356-8de4-41af-8803-fa7345ce238b"
Duration="4">
<PriceValue Type="Children" AgeFrom="6" AgeTo="10" SalesPrice="110" AdditionalNight="30.00" />
<PriceValue Type="Children" AgeFrom="11" AgeTo="12" SalesPrice="200" AdditionalNight="40.00" />
<PriceValue Type="Children" AgeFrom="0" AgeTo="2" SalesPrice="0" AdditionalNight="0.00" />
<PriceValue Type="Children" AgeFrom="3" AgeTo="5" SalesPrice="60" AdditionalNight="20.00" />
<PriceValue Type="Adults" SalesPrice="280" AdditionalNight="70.00" />
</Price>
<Price DateFrom="2011-01-09" DateTo="2011-02-03" CategoryId="007ef356-8de4-41af-8803-fa7345ce238b"
Duration="3">
<PriceValue Type="Children" AgeFrom="11" AgeTo="12" SalesPrice="150" AdditionalNight="40.00" />
<PriceValue Type="Children" AgeFrom="0" AgeTo="2" SalesPrice="0" AdditionalNight="0.00" />
<PriceValue Type="Children" AgeFrom="3" AgeTo="5" SalesPrice="50" AdditionalNight="20.00" />
<PriceValue Type="Children" AgeFrom="6" AgeTo="10" SalesPrice="90" AdditionalNight="30.00" />
<PriceValue Type="Adults" SalesPrice="210" AdditionalNight="70.00" />
</Price>
</Prices>
</Package>
</Packages>
</Result>
</FeratelDsiRS>

Section:

Response field Description Can be


Multiple?
empty?
Section ID The ID of the section
ChangeDate Date/time indicator when the item was last changed.
Name Translations of service name
ParentSection ID of a section which is parent, if there is no parent id is zero guid
Order Order of the section of a package
UseAvailability Does this section use availabilities or not (1..true, 0…false)
AssignedProducts perCategorie or allCategories, defines if the products assignments
are done for each categorie or an assigned product is for all
categories
SelectionRules Type can be Optional or Fixed. Optional sections means that the
package can be booked also without any item of this section, fixed
means that the section and one according item has to be booked.
If Optional two further parameters can be true. AddPrice and
ShowPrice. AddPrice means price of the section is added to fixed
package price and ShowPrice means that the price has to be shown
in Shopping Cart
Dependency Provides the information if a section has any dependency. Type can
be NoDependency or WithDependency.
DependenyRules A section can have dependency to another section of to any
specific start or and date. Type defines to which other part the
section is depended to (Enumeration: NoDependency,
PackageStart, SectionStart, SectionEnd, DependentSectionStart,
DependendSectionEnd). StartDaysAfter defnies the days this
section starts after the event defined in Type. If there is a
dependency on any other section, the id of this section will be
provided; else it is a zero guid.
BookingRules UnitsBookable defines the maximum number of units of this

Basic Data For Destination Packages 107 of 241


DESKLINE 3.0 STANDARD INTERFACE

section which can be booked per Package or Person. BookablePer


defines whether this section is bookable perPackage or perPerson
and MaxPerPackage defines the maximal number of units which
can be booked per overall package
SectionDuration Provides a list of DurationDays, defines the duration of the section
in days according to the different durations of the package.
Descriptions Descriptions in various languages. Each description can either have
a From-To timeframe (only day/month, not year) or can be set to
be shown as “always” in which case From-To is send as “101”-
“1231” in the element. Line-breaks are not converted to HTML-
line-breaks, the description will be returned as entered in the
system. Descriptions can also be set to only be available for
different output systems such as: local (Deskline 3.0 backend),
internet presentation, Informator or catalog productions. When
requesting basic data the Systems-Attribute must already be
provided to filter only internet-descriptions for example.
Prices Price structure is different according to the price settings, for
details see structure of a destination package.
Products Each section can have multiple products assigned. All Product
details can be called via Basic Data Request for accommodation
and additional services.
Product For each assigned product, the according product and service
provider id is provided. Products have a specific type
(Accommodation or AdditionalService). If the product is assigned
to a specific category, the id is provided and if it is assigned to all
categories the id is a zero guid. A product can be defined as
preselected or not.
Availabilities For assigned products it is whether possible to take the existing
availabilities or to define special availabilities for this package
(OwnAvailability: true or false). If there are special availabilities for
this product package combination, these availabilities are listed.
Prices For assigned products it is whether possible to take the existing
prices or to define special prices for this package (OwnPrice: true
or false). If there are special Prices for this product package
combination, these prices are listed.

Package example with sections and products:


<?xml version="1.0" encoding="UTF-8"?>
<FeratelDsiRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
Status="0" Message="OK" xmlns="http://interface.deskline.net/DSI/XSD">
<Result Index="1">
<Packages>
<Package Id="61ff04c2-9bf0-40b5-8bca-d86e4eb938ca" ChangeDate="2011-07-12T16:00:00">
<Details> … </Details>
<Descriptions> … </Descriptions>
<Documents> … </Documents>
<Links> … </Links>
<Prices> … </Prices>
<Sections>
<Section Id="b69a9d6d-6705-4aef-a6bc-54edbc8158da" ChangeDate="2011-02-18T14:58:00">
<Details>
<Name>
<Translation Language="de">Hotel</Translation>
<Translation Language="en">Hotel</Translation>
</Name>
<ParentSection Id="00000000-0000-0000-0000-000000000000" />
<ProductType>Accommodation</ProductType>
<Order>1</Order>
<UseAvailability>1</UseAvailability>

Basic Data For Destination Packages 108 of 241


DESKLINE 3.0 STANDARD INTERFACE

<AssignedProducts>perCategory</AssignedProducts>
<SelectionRules Type="Mandatory" AddPrice="false" ShowPrice="false" />
<Dependency Type="NoDependency">
<DependencyRules StartDaysAfter="0" Type="NoDependency" DependendSectionId="00000000-0000-0000-0000-
000000000000" />
</Dependency>
<BookingRules UnitsBookable="1" BookablePer="perPackage" MaxPerPackage="1" />
<SectionDuration>
<DurationDays PackageDays="5" SectionDays="5" />
</SectionDuration>
</Details>
<Descriptions>
<Description Id="1f8e816c-e325-4979-b608-b8b7183c158d" Type="ShopItemDescription" Language="en" Systems="L T
I C" ShowFrom="101" ShowTo="1231" ChangeDate="2011-02-21T22:11:00">please select the accommodation of your
choice</Description>
</Descriptions>
<Prices>
<Price DateFrom="2011-04-01" DateTo="2011-08-30" CategoryId="6c148389-c75d-47d9-963a-78198a9ea7c1"
Duration="3">
<PriceValue Type="AdultSingle" SalesPrice="0.00" AdditionalNight="0.00" />
<PriceValue Type="Adults" SalesPrice="0.00" AdditionalNight="0.00" />
<PriceValue Type="Children" AgeFrom="0" AgeTo="15" SalesPrice="0.00" AdditionalNight="0.00" />
</Price>
<Price DateFrom="2011-04-01" DateTo="2011-08-30" CategoryId="bf90ee27-9d0e-49d1-a4c2-d0fd08613f1b"
Duration="3">
<PriceValue Type="AdultSingle" SalesPrice="0.00" AdditionalNight="0.00" />
<PriceValue Type="Adults" SalesPrice="0.00" AdditionalNight="0.00" />
<PriceValue Type="Children" AgeFrom="0" AgeTo="15" SalesPrice="0.00" AdditionalNight="0.00" />
</Price>
</Prices>
<Products>
<Product ServiceProviderId="85cb2b50-5577-49d8-bb3d-1256024f15a9" ProductId="2b5b7e0e-3eb9-4c6b-a9cb-
7f3427f5caea" ProductType="Accommodation" CategoryId="6c148389-c75d-47d9-963a-78198a9ea7c1" PreSelected="false">
<Availabilities OwnAvailability="true">
<Availability Day="2011-03-02" Count="12" />
<Availability Day="2011-03-03" Count="12" />
<Availability Day="2011-03-04" Count="12" />
<Availability Day="2011-03-05" Count="12" />
<Availability Day="2011-03-06" Count="12" />
<Availability Day="2011-03-07" Count="12" />
<Availability Day="2011-03-08" Count="12" />
<Availability Day="2011-03-09" Count="12" />
<Availability Day="2011-03-10" Count="12" />
<Availability Day="2011-03-11" Count="12" />
<Availability Day="2011-03-12" Count="12" />
<Availability Day="2011-03-13" Count="12" />
<Availability Day="2011-03-14" Count="12" />
<Availability Day="2011-03-15" Count="12" />
<Availability Day="2011-03-16" Count="12" />
<Availability Day="2011-03-17" Count="12" />
<Availability Day="2011-03-18" Count="12" />
<Availability Day="2011-03-19" Count="12" />
<Availability Day="2011-03-20" Count="12" />
</Availabilities>
<Prices OwnPrice="false" />
</Product>
<Product ServiceProviderId="77a7c00d-fc50-4e36-a7d8-4582116c0742" ProductId="45e5ca09-c159-44c7-8bc7-
969afc71f0b1" ProductType="Accommodation" CategoryId="bf90ee27-9d0e-49d1-a4c2-d0fd08613f1b" PreSelected="false">
<Availabilities OwnAvailability="false" />
<Prices OwnPrice="false" />
</Product>
<Product ServiceProviderId="159c796f-aac8-4541-908f-5832fdd60e17" ProductId="8a923522-fde8-4e4d-aac9-
99804b442620" ProductType="Accommodation" CategoryId="6c148389-c75d-47d9-963a-78198a9ea7c1" PreSelected="false">
<Availabilities OwnAvailability="false" />
<Prices OwnPrice="true" />
</Product>
</Products>
</Section>
<Section Id="e5f59704-85b9-41f3-aca6-06a4a873c922" ChangeDate="2011-08-23T10:22:00">
<Details>

Basic Data For Destination Packages 109 of 241


DESKLINE 3.0 STANDARD INTERFACE

<Name>
<Translation Language="de">Ski Pass</Translation>
<Translation Language="en">Ski Pass</Translation>
</Name>
<ParentSection Id="00000000-0000-0000-0000-000000000000" />
<ProductType>AdditionalService</ProductType>
<Order>2</Order>
<UseAvailability>1</UseAvailability>
<AssignedProducts>perCategory</AssignedProducts>
<SelectionRules Type="Mandatory" AddPrice="false" ShowPrice="false" />
<Dependency Type="NoDependency">
<DependencyRules StartDaysAfter="0" Type="NoDependency" DependendSectionId="00000000-0000-0000-0000-
000000000000" />
</Dependency>
<BookingRules UnitsBookable="1" BookablePer="perPerson" MaxPerPackage="1" />
<SectionDuration>
<DurationDays PackageDays="5" SectionDays="5" />
</SectionDuration>
</Details>
<Descriptions />
<Prices />
<Products>
<Product ServiceProviderId="5cfb095f-4da6-4c67-a7b5-c7d031c2ba38" ProductId="41ea520f-518b-48a8-b2bd-
3644f9824958" ProductType="AdditionalService" CategoryId="00000000-0000-0000-0000-000000000000"
PreSelected="false">
<Availabilities OwnAvailability="false" />
<Prices OwnPrice="false" />
</Product>
<Product ServiceProviderId="5cfb095f-4da6-4c67-a7b5-c7d031c2ba38" ProductId="41ea520f-518b-48a8-b2bd-
3644f9824958" ProductType="AdditionalService" CategoryId="6c148389-c75d-47d9-963a-78198a9ea7c1"
PreSelected="false">
<Availabilities OwnAvailability="false" />
<Prices OwnPrice="false" />
</Product>
<Product ServiceProviderId="f870aa62-bc37-45ff-b911-3533742d78fb" ProductId="9016623c-4012-4021-a918-
d45dc5c3c705" ProductType="AdditionalService" CategoryId="00000000-0000-0000-0000-000000000000"
PreSelected="false">
<Availabilities OwnAvailability="false" />
<Prices OwnPrice="false" />
</Product>
</Products>
</Section>
</Package>
</Packages>
</Result>
</FeratelDsiRS>

BASIC DATA FOR HOUSE PACKAGE CONTAINER


Each service provider can offer hie indivudal packages, so called house packages. This kind of products are
already available in basic data for service providers (<ProductType>Accommodation</ProductType> in Details
on Product level). A destination can put this house packages into a container and add some further details to
this package group like valid period, descriptions, and images and so on.

REQUEST
A request consists of three different parts: first, the mandatory values, then the optional filter and then the
definition, which elements to provide in the response.

Request field Description Can be empty? Multiple?


Originator The code of the point of sale requesting the data.
Provided by feratel.
Company The code of the company requesting the data. Provided

Basic Data For House Package Container 110 of 241


DESKLINE 3.0 STANDARD INTERFACE

by feratel.
Range and GUIDs First, a range code to select the data must be defined.
IDs This is an enumeration if it is a region (RG) or a town (TO)
or a district (DI) for example. It is also possible to select
one or more data owners instead of a geographical
selection. The IDs of regions/towns/districts are part of
the KeyValues function. If there is a need to call data
owners (DO) directly, the IDs are provided by feratel. The
top location (i.e. highest/widest range possible) will be
provided by feratel to get started (see range example in
KeyValues.xml)
Filters Request on Packages can be filtered to a specific Sales
Channel.
Filters: There is the possibility to filter the Status. Therefore set
PackageContainer the attribute Status to Active, Inactive or All. Active is
default. Also you can request only packages within a
specific time period, therfore set From and To with the
required date. These parameters are optional
Filter: Languages The request must already include the languages that
should be returned upon one request for Shop Items.
HolidayThemes Basic data request for package container can be limited
to provide only package containers that are related to a
specific holiday theme. The list of these IDs is provided in
the Key Values Function.
PackageContainers To receive details about the Package. Parameter
Details DateFrom must be provided.
PackageContainers Parameter DateFrom must be provided. Also, the
Documents Systems Enumeration must be filled. E.g. Systems=”T” to
get all documents that should be displayed online.
PackageContainers Parameter DateFrom must be provided. Also, the
Descriptions Systems Enumeration must be filled. E.g. Systems=”T” to
get all descriptions that should be displayed online.
Descriptions Enum: true/false default: false
Markup when you set the optional attribute Markup=”true” you
get back html format tags which might be selected from
the customers.
PackageContainers Parameter DateFrom must be provided.
Links
PackageContainers To request all the products of ProductType Package
AssignedProducts within this package container

EXAMPLE REQUEST

Get all details of a package container


<?xml version="1.0" encoding="utf-8"?>
<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://interface.deskline.net/DSI/XSD">
<Request Originator="FERATEL" Company="FERATEL">
<Range Code="RG">
<Item Id="F180FFD5-4FBF-4F2C-AC00-7E8B94462F2C" />
</Range>
<BasicData>
<Filters SalesChannelId="BB556229-E7B1-4F21-9C6A-2BEA7120BF5A">

Basic Data For House Package Container 111 of 241


DESKLINE 3.0 STANDARD INTERFACE

<PackageContainer From="2013-02-01" To="2013-03-31"/>


<Languages>
<Language Value="de" />
<Language Value="en" />
</Languages>
</Filters>
<PackageContainers>
<Details DateFrom="1980-01-01" />
<Documents DateFrom="1980-01-01" Systems="T" />
<Descriptions DateFrom="1980-01-01" Systems="T" Markup="true" />
<Links DateFrom="1980-01-01" />
<AssignedProducts DateFrom="1980-01-01" />
</PackageContainers>
</BasicData>
</Request>
</FeratelDsiRQ>

RESPONSE
Response field Description Can be empty? Multiple?
ID GUID of the package
ChangeDate Date/time indicator when the item was last changed.
Name List of names of the package in requested languages
Priority Number to define the priority in lists, to allow
customers their own sort order
MeetingPoint List of Meeting Points of the package in requested
languages
HolidayThemes e.g. Weekend, Wedding, Family, etc..
Active Indicates if the package is active or not.
DBCode 3 letter code of the database. This is also part of the
search response and is used for adding items to the
shopping cart and for generating a direct link.
Position Latitude, GPS Coordinates
Longitude
ValidDates List of periods in which the package is offerable
PackageCategories List of categories of the package container including Id
Order and PriceFrom as well as name in all requested
languages
Owner Organisation code of the data owner of this package
AssignedProducts List of the assigned house packages (accommodation
products of type package) to this container, including Id
of service provider, of the assigned product and the
according category as well as if this product is
preselected or not. Preselected means, that one of the
products inside a container categora can be
preselected, means it should have first priority when
offering it to the guest.

Basic Data For House Package Container 112 of 241


DESKLINE 3.0 STANDARD INTERFACE

EXAMPLE RESPONSE

Basic data for package container


<?xml version="1.0" encoding="UTF-8"?>
<FeratelDsiRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
Status="0" Message="OK" xmlns="http://interface.deskline.net/DSI/XSD">
<Result Index="1">
<PackageContainers>
<Package Id="4ee053eb-a06e-48b4-8b56-4bf12d6dccc3" ChangeDate="2012-05-25T07:51:00">
<Details>
<Name>
<Translation Language="de">Hotelpauschalen-Sammlung</Translation>
<Translation Language="en">Hotelpauschalen-Sammlung</Translation>
</Name>
<Priority>99</Priority>
<MeetingPoint>
<Translation Language="de" />
<Translation Language="en" />
</MeetingPoint>
<HolidayThemes />
<Active>true</Active>
<DBCode>FRT</DBCode>
<Position Latitude="46.3521411920093" Longitude="13.8008880615234" />
<ValidDates Type="Period">
<ValidDate From="2012-04-17" To="2020-04-17" />
</ValidDates>
<PackageCategories>
<PackageCategory Id="98558f60-ca3b-43af-8a85-0eba38f4b9bf" Order="2" PriceFrom="0.00">
<Name>
<Translation Language="de">3*-Häuser</Translation>
<Translation Language="en">3*-Häuser</Translation>
</Name>
</PackageCategory>
<PackageCategory Id="131464b2-834f-4167-a4b4-5b0563c029e4" Order="1" PriceFrom="0.00">
<Name>
<Translation Language="de">4*-Häuser</Translation>
<Translation Language="en">4*-Häuser</Translation>
</Name>
</PackageCategory>
</PackageCategories>
<Owner>ATDEMO</Owner>
</Details>
<Descriptions>
<Description Id="3631b008-09ca-441c-be4b-73c04fc43f18" Type="Package" Language="de" Systems="L T I C"
ShowFrom="101" ShowTo="1231" ChangeDate="2012-04-17T14:41:00">
Sammel-Info Package...
Im Rahmen aller Packages, die Sie nachfolgend finden, sind spezielle Wellness-Arrangements inkludiert, die Sie im
gewählten Haus genießen können.
</Description>
</Descriptions>
<Documents>
<Document Id="1a8e5cf1-705e-4244-b562-fe6a4384a776" Type="Package" Class="Image" Systems="L T I C" Order="1"
ShowFrom="101" ShowTo="1231" Copyright="" Extension="jpg" Size="3" ChangeDate="2012-04-17T14:40:00">
<Names>
<Translation Language="de">Sammel-Info</Translation>
<Translation Language="en">Sammel-Info</Translation>
</Names>
<URL>http://interfacetest.deskline.net/Handlers/Document?code=FRT&amp;id=1a8e5cf1-705e-4244-b562-
fe6a4384a776</URL>
</Document>
</Documents>
<AssignedProducts>
<AssignedProduct ServiceProviderId="5cf454ea-c793-4257-8638-0fc6e98860b0" ProductId="8debcec2-db93-498b-b7d2-
1230fe210b63" CategoryId="98558f60-ca3b-43af-8a85-0eba38f4b9bf" PreSelected="false" />
<AssignedProduct ServiceProviderId="5ad99730-be1f-4c75-84c4-afb26072c5f0" ProductId="3c5651db-cbe6-4199-8419-
9edaca6f9322" CategoryId="98558f60-ca3b-43af-8a85-0eba38f4b9bf" PreSelected="false" />
<AssignedProduct ServiceProviderId="5d2fb51b-f2f0-4f0e-b4e1-fc1ed38e0cf0" ProductId="8ba93d0c-bef4-4c10-aa2f-
2d88aa9bad6a" CategoryId="98558f60-ca3b-43af-8a85-0eba38f4b9bf" PreSelected="false" />
<AssignedProduct ServiceProviderId="5d2fb51b-f2f0-4f0e-b4e1-fc1ed38e0cf0" ProductId="e7d86b05-cbd4-498b-9f16-

Basic Data For House Package Container 113 of 241


DESKLINE 3.0 STANDARD INTERFACE

cdba5c0fe64c" CategoryId="98558f60-ca3b-43af-8a85-0eba38f4b9bf" PreSelected="false" />


<AssignedProduct ServiceProviderId="8906e074-8a26-4cac-93d7-4109d872f3f3" ProductId="be9dc544-8add-433e-b697-
469e2118380a" CategoryId="131464b2-834f-4167-a4b4-5b0563c029e4" PreSelected="false" />
<AssignedProduct ServiceProviderId="8906e074-8a26-4cac-93d7-4109d872f3f3" ProductId="723a15a7-03da-42eb-9c93-
f8234b4d6ccd" CategoryId="131464b2-834f-4167-a4b4-5b0563c029e4" PreSelected="false" />
<AssignedProduct ServiceProviderId="030e555c-8423-4043-bbb4-63555feb75a6" ProductId="4a59a4da-23d0-488b-
b745-05a1d16887f0" CategoryId="131464b2-834f-4167-a4b4-5b0563c029e4" PreSelected="false" />
<AssignedProduct ServiceProviderId="030e555c-8423-4043-bbb4-63555feb75a6" ProductId="1bbbf1ce-2ab8-4cb2-aac1-
159a52c4f88a" CategoryId="131464b2-834f-4167-a4b4-5b0563c029e4" PreSelected="false" />
</AssignedProducts>
</Package>
<Package Id="d690bfdd-2373-4982-b3cf-c513aef6e984" ChangeDate="2012-10-01T16:52:00">
<Details>
<Name>
<Translation Language="de">Frühlingspauschalen 15735</Translation>
<Translation Language="en">Frühlingspauschalen 15735</Translation>
</Name>
<Priority>99</Priority>
<MeetingPoint>
<Translation Language="de" />
<Translation Language="en" />
</MeetingPoint>
<HolidayThemes />
<Active>true</Active>
<DBCode>FRT</DBCode>
<Position Latitude="0" Longitude="0" />
<ValidDates Type="Period">
<ValidDate From="2012-10-01" To="2030-10-01" />
</ValidDates>
<PackageCategories>
<PackageCategory Id="937f75a8-c4af-426d-b944-cff424034240" Order="2" PriceFrom="0.00">
<Name>
<Translation Language="de">Pension</Translation>
<Translation Language="en">Pension</Translation>
</Name>
</PackageCategory>
<PackageCategory Id="08975d6d-d557-4928-a647-d0e171f66554" Order="1" PriceFrom="0.00">
<Name>
<Translation Language="de">Hotel</Translation>
<Translation Language="en">Hotel</Translation>
</Name>
</PackageCategory>
</PackageCategories>
<Owner>FERATEL</Owner>
</Details>
<AssignedProducts>
<AssignedProduct ServiceProviderId="030e555c-8423-4043-bbb4-63555feb75a6" ProductId="4a59a4da-23d0-488b-
b745-05a1d16887f0" CategoryId="937f75a8-c4af-426d-b944-cff424034240" PreSelected="false" />
<AssignedProduct ServiceProviderId="2807f642-e21b-4a15-a4b9-8a561e0fec18" ProductId="4b422076-f0fb-4cd1-bcab-
1ce3aa493ebb" CategoryId="08975d6d-d557-4928-a647-d0e171f66554" PreSelected="false" />
</AssignedProducts>
</Package>
</PackageContainers>
</Result>
</FeratelDsiRS>

114 of 241
DESKLINE 3.0 STANDARD INTERFACE

BASIC DATA: DELETED ITEMS


It is always possible that items are deleted from a database. This can cause problems if a document is shown
online that was deleted by the service provider. These changes cannot be part of the basic data when
requesting “changed items” so there is a new function to request the IDs of deleted items. Based on the needs
this can be done for different parts of the basic data, i.e. only for events or only for service provider
descriptions, but not necessarily for service provider documents. The function to log deleted items must be
activated per customer database so it’s not active by default but on demand.

Note: Because of various reasons there can always be a lot of IDs in the response that were never in a previous
basic data export to begin with, we just list all IDs that were deleted.

IDs of deleted items are only kept in the system for 30 days.

REQUEST
A request consists of two different parts: first, the mandatory values and then the definition, which elements to
provide in the response.

Request field Description Can be empty? Multiple?


Originator The code of the point of sale requesting the data.
Provided by feratel.
Company The code of the company requesting the data. Provided
by feratel.
Range and GUIDs The Range Code/ID Combination for DeletedItems can be
IDs the top location because the list of IDs can’t be requested
per town.
DeletedItems Container element
DateFrom Returns the IDs that were deleted from this day on.
DateTimeFrom Same affect as DateFrom, just to be more precise. If
DateTimeFrom is provided DateFrom will be ignored
DeletedItem Element to define what kind of deleted items should be
returned.
DeletedItem Enumeration. Possible values:
Type  ServiceProviders
 Addresses
 AddressContacts
 Services
 Products
 Descriptions
 Documents
 WebLinks
 Events
 InfrastructureItems
 PriceTemplates
 SalesRuleTemplates
 ArrivalDepartureTemplates
DeletedItem Only used for the types “Descriptions”, “Documents”.
ParentTypes Documents can either be assigned to a service, to a
product, to a service provider or to an event.

The ParentTypes Attribute can be a combination of the


following values: ServiceProvider Service Products
ShopItem Event Infrastructure
Basic Data: Deleted Items 115 of 241
DESKLINE 3.0 STANDARD INTERFACE

Example: <DeletedItem Type="Documents"


ParentTypes="Event Infrastructure" />

Note: If you work with the addresses in basic data then the ID in the basic data response refers to the item
Address in the deleted items function, not the AddressContacts!

EXAMPLE

Get deleted items for service providers, description and documents:


<?xml version="1.0" encoding="utf-8"?>
<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://interface.deskline.net/DSI/XSD">
<Request Originator="FERATEL" Company="FERATEL">
<Range Code="RG">
<Item Id="F180FFD5-4FBF-4F2C-AC00-7E8B94462F2C" />
</Range>
<BasicData>
<DeletedItems DateFrom="2010-01-01">
<DeletedItem Type="ServiceProviders" />
<DeletedItem Type="Descriptions" ParentTypes="ServiceProvider Service Product"
/>
<DeletedItem Type="Documents" ParentTypes="ServiceProvider Service Product"
/>
</DeletedItems>
</BasicData>
</Request>
</FeratelDsiRQ>

RESPONSE
The response for DeletedItems is grouped by the requesting types.

Request field Description Can be empty? Multiple?


DeletedItems Container Element per type
DeletedItems Type based on the request. Elements are grouped by
Type type. Can be missing if no items were deleted for the
requested time frame.
Item List of Items with attribute ID – the ID of the deleted
record, can be multiple.

EXAMPLE

<?xml version="1.0" encoding="UTF-8"?>


<FeratelDsiRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
Status="0" Message="OK" xmlns="http://interface.deskline.net/DSI/XSD">
<Result Index="1">
<DeletedItems Type="PriceTemplates">
<Item Id="827ea406-cfb6-410b-ac4c-5cecf64f054e" />
<Item Id="735389b1-e7f6-4e52-bb0d-c0d34041317c" />
</DeletedItems>
<DeletedItems Type="Products">
<Item Id="6843b612-5914-4e0f-8341-217a70e8f3a6" />
</DeletedItems>
<DeletedItems Type="SalesRuleTemplates">
<Item Id="820501dd-139f-40e2-aec0-c2e4fb1756b0" />
</DeletedItems>
</Result>
</FeratelDsiRS>

Basic Data: Deleted Items 116 of 241


DESKLINE 3.0 STANDARD INTERFACE

SEARCH FOR AVAILABILITIES


The search function that the DSI uses is the same function as for the Deskline 3.0 Web application and the
Deskline 3.0 ExpertClient and therefore supports the same functionality.

There are maximal three search lines possible. Each search line can have different filters and occupancy
settings, therefore a search line must include a number to identify the corresponding response item.

The search result will provide the basic information about the price and service provider and product. To
display the full details, the service provider basic data must already be stored in the requesting system. Keep in
mind that since it is possible in Deskline 3.0 to create a search like “2 nights in the timeframe of December 23rd
to January 5th” the response will also provide DateFrom and DateTo values. Please note that search requests
where more arrival dates are possible will have longer response times. We recommend a maximum period of
14 days.

The search response will be internally cached for 200 seconds after the last query. This way, paging will also be
possible. If the same search is made after 200 seconds, a new result set will be generated.

All the prices listed in the response are in the requested currency; if no currency code is send the default
currency code of the point of sale (originator) is taken.

Search response can be requested in different types. Due to the response type given in request the structure of
reponse is different. For further details please see following chapter “Response”.

Important: If a currency code is send for which the destination did not entered a rate, the search result is
empty.

REQUEST
Request field Description Can be empty? Multiple?
Originator The code of the point of sale requesting the data.
Provided by feratel.
Company The code of the company requesting the data. Provided
by feratel.
Range and GUIDs First, a range code to select the data must be defined.
IDs This is an enumeration if it is a region (RG) or a town
(TO) or a district (DI) for example. It is also possible to
select one or more data owners instead of a
geographical selection. The IDs of
regions/towns/districts are part of the KeyValues
function. If there is a need to call data owners (DO)
directly, the IDs are provided by feratel. The top
location (i.e. highest/widest range possible) will be
provided by feratel to get started (see range example in
KeyValues.xml)
Language The language that is expected of the response.
CurrencyCode If this element is not send the defined Currency for the
Point of Sale is taken (Originator). If a CurrencyCode
different to the point of sale currency is send all the
prices in the search result get converted automatically.
CurrencyCode is the 3-digits long international currency
code (e.g. EUR, CHF,…)
SearchLines - Paging StartIndex and PageSize are used for paging, e.g. if the
response should contain 20 items, starting at the 70th

Search For Availabilities 117 of 241


DESKLINE 3.0 STANDARD INTERFACE

search result. The total amount of available objects will


be available in the Response (TotalObjects). The
maximum page size allowed is 300 but should not be
used with total price calculation because of
performance reasons.
Examples:
StartIndex=1, PageSize=100 – will return 100 results.
StartIndex=1, PageSize=10 – will return 10 results.
StartIndex=11, PageSize=10 – will return the next 10
results.
SortOrder Enumeration. This can be used to sort the result
directly at the interface to (for example) only get the
first 20 results, ordered by TotalPrice. Combinations of
the following values are possible:
Random: Randomizes the result.
TotalPrice, TotalPriceDesc: Sorted by total price
ascending or descending.
Price, PriceDesc: Sorted by base price ascending or
descending.
Bookable, BookableDesc: Sorted by bookable
ascending or descending.
Rating, RatingDesc: Sorted by overall rating value
ascending or descending.
Town, TownDesc: Sorted by town name ascending or
descending.
Name, NameDesc: Sorted by service provider name
ascending or descending.
Distance, DistanceDesc: Sorted by Distance to
requested Hotspot ascending or descending
Stars, StarsDesc: Sorted by service provider stars
ascending or descending.
ServiceProviderPriority, ServiceProviderPriorityDesc:
Sorted by service provider priority ascending or
descending.
Example: SortOrder=”Bookable Price” or
SortOrder=”Random” or SortOrder=”Town Name”
SearchType Optional, three values possible: OneProductPerHotel,
Standard (which is the default value) or
EachProductSeparated. By default, the search function
returns all available products for one service provider.
If the value “OneProductPerHotel” is passed, then only
one product is returned. In combination with the total
price calculation this will increase the performance of
the search result! EachProductSeparated means if a
service provider has more than one product available
they will be listed separately in the response, also
TotalObjects is based on products found and not
service providers found, so paging can be done on
product level as well. May be useful for products of
type Package.
ResponseType Enumeration “Standard”, “Expanded” and
“ExpandedPaymentInfo”. Standard is default if you do
not include this attribute in request.
For further details to the different structure of
response and how to interpret the result correctly see
following chapters “Default Response

Search For Availabilities 118 of 241


DESKLINE 3.0 STANDARD INTERFACE

(ResponseType=”Standard”)” and “Response


(ResponseType=”Expanded”)”. For Typ
ExpandedPaymentInfo we give back additional to
the information in ResponseTyp Expanded also the
CancelationInformation about the accomodations.
SearchParameters Every SearchParameters element can have a different
occupancy and different facility requirements.
Index Search parameter index will be reflected in the
response. Up to 3 search lines are possible.
SalesChannel The GUID of the SalesChannel for the products.
Assigned by feratel.
Note: In case of muliti line search each container
element SearchParameters include the SalesChannel, it
is not possible to search with different SalesChannels, if
you provide different one only the one of the first
search line will be taken to proceed.
Units Amount of required units
Adults Amount of Adults (per unit)
From Date of arrival
To Date of departure
Nights Length of stay. It is possible to search for 3 nights in a 5
day timeframe. In this case, one product may be in the
response more than once but with different possible
arrival dates.
LastMinuteOnly Optional Filter. Can be true or false. Is false per default
and this means all kind of search results are included in
the response. If true only last minute offers are
included in response.
SplitOffersOnly Optional Filter. Can be true or false. Is false per default
and this means all kind of search results are included in
the response. If true only split offers (e.g. stay 7 pay 6
nights) are included in response.
MultilineSearchCondition If there are two or three search lines the first and the
second search line has to include the attribute
MultilineSearchCondition which can be “Or”, “And” or
“None”. If it is none the next search lines will be
ignored
ServiceProvider ID To search inside one service provider only, the Deskline
3.0 GUID can be provided in the request. Passing the ID
to one hotel will guarantee the best performance
available.
ServiceProvider Code To search inside one service provider only, the Deskline
object code can be provided in the request. When
passing a code, still a search is done for the provided
range because it’s possible that the code is not unique.
Slower than passing the ID!
ServiceProvider Name To search inside one service provider only, the full
name of the service provider can be provided in the
request. When passing a name, still a search is done for
the provided range because it’s possible that the name
is not unique. Slower than passing the ID!
ServiceProvider The optional attribute ContentScoreMin is a filter for
ContentScoreMin the contentscore of the Serviceprovider. The value
must be percentage (0-99). When you set filter to 80
you will only get back ServiceProvider in searchresult

Search For Availabilities 119 of 241


DESKLINE 3.0 STANDARD INTERFACE

with contentscore >= 80


ServiceProvider Within the element ServiceProvider the subelement
RadiusSearch RadiusSearch can be provided. Attributes are
Longitude, Latitude and Distance (in kilometers)
Example:
<ServiceProvider>
<RadiusSearch Longitude="13.82479"
Latitude="46.6188492" Distance="10"/>
</ServiceProvider>

Response will include onle those service providers


within the requested radius.
Note: ID/Code/Name is either/or: if an ID is provided, Code/Name will not be
checked and so on.
PreSelected- <PreSelectedServiceProviderIDs> can be used to search
ServiceProviderIDs inside more than one service provider based on the SP-
ID. This can also be used for targeted searches if more
than one hotel should be checked.
Service Container Element for service filters inside the service
provider element.
LastAvailability- Integer value for the number of days that the service
ChangeDays provider must have last changed the availabilities. For
example to make a search and only return the service
providers that last changed their availabilities within 7
days. Customer can set this value in backoffice system
ExpertClient. If you are willing to take the same
restriction customer has entered send with value zero
and search will be automatically done with customer
settings.
MinRooms Integer value for the number of rooms a service should
have at least.
MinSleepingRooms ="M Integer value for the number of sleeping rooms a
service should have at least.
MinRoomSize Integer value for the size of a service in square meter
should have at least.
Code Service code, which can be called with Key Values
method to restrict response to a specific service type
ServiceFacility Information of required service facilities.
Item Id: Id of the facility to filter search result.
Refer to the list of Key Values for the GUIDs.
Item Value: If facility has ValueType IntDigit a minimum
value can be provided, unless default value is 1.
Item Mandatory: If set to true (default), all selected
facilities must match with the service provider. If set to
false facility can match, how much it matches is in
element Match of search response of type Expanded.
ServiceClassification Information of required service classifications. All
selected classifications must match with the service.
Refer to the list of Key Values for the GUIDs.
ServiceHandicapFacility Information of required service handicap facilities.
Item Id: Id of the facility to filter search result.
Refer to the list of Key Values for the GUIDs.
Item Value: If facility has ValueType IntDigit a minimum
value can be provided, unless default value is 1.
Item Mandatory: If set to true (default), all selected
facilities must match with the service provider. If set to

Search For Availabilities 120 of 241


DESKLINE 3.0 STANDARD INTERFACE

false facility can match, how much it matches is in


element Match of search response of type Expanded.
Product Container Element for product filters inside the service
provider element.
Product ID To search inside one specific product, the Deskline 3.0
product GUID can be provided in the request in
addition to the service provider ID.
AccommodationType Enumeration of HotelRoom, Apartment, Camping
ProductType Enumeration of Accommodation, AdditionalService or
Package
SearchCode Searchcode of the product as given in the BasicData
response.
BasePriceOnly True/false, set to true to only get a base price for each
product returned or to false to get a calculated total
price. The total price calculation decreases
performance so it must not be used without using
paging and it should not be used during a wide area
search, but rather for example in a search for a single
item. ResponseType=”Expanded” requires this
attribute set to true.

The base price is the regular price for a bed as defined


by the service provider (per night / per unit / ...) and
does not include any calculations regarding meals,
surcharges, discounts, children prices etc. whatsoever.
Only the total price calculation will return the total
price with all calculations necessary.
HolidayThemes Used to query for holiday themes like “wedding”,
“sports”, and so on. Refer to the list of Key Values for
the GUIDs.
Children Ages of children, comma separated if more than one
child is requested. Is regarded as per unit. Provide a
maximum of 20 characters.
Meal Type of meal requested.
MaxPrice Search can be restricted to a specific maximum price
MinPrice Search can be restricted to a specific minimum price
BookOnly Indicator if only bookable or all products should be
found.
BookOnly true/false value, true by default. Provides possibility to
IncludeOnlyOnRequest get back only those products directly bookable.
AccommodationFacility Information of required service provider facilities.
Item Id: Id of the facility to filter search result.
Refer to the list of Key Values for the GUIDs.
Item Value: If facility has ValueType IntDigit a minimum
value can be provided, unless default value is 1.
Item Mandatory: If set to true (default), all selected
facilities must match with the service provider. If set to
false facility can match, how much it matches is in
element Match of search response of type Expanded.
Category Used to query only hotels or pensions for example.
Refer to the list of Key Values for the GUIDs.
Stars Used to query only 3-star hotels for example. Refer to
the list of Key Values for the GUIDs.
MarketingGroup Used to query service providers that are part of one of
the required marketing groups. Refer to the list of Key
Search For Availabilities 121 of 241
DESKLINE 3.0 STANDARD INTERFACE

Values for the GUIDs. Per default logical connection if


more than one marketing group is provided is OR. If
search has to be done for service providers which
should have all the Marketing groups use optional
attribute LogicalConnectionAND="true" in
MarketingGroup element. (This is only working for
single line search not for mutli line search)
Chain Used to query service providers that are part of a
specific chain like Best Western. Refer to the list of Key
Values for the GUIDs
Classification Used to query for flowers or similar classification
information. Refer to the list of Key Values for the
GUIDs.
HotSpot Used to query only service provider with a specific
distance to a hotspot. List of hotspots and hotspot
types available via Key Value request. There are three
different ways to search via hotspots:
<HotSpot SearchBy="HotSpotId " Id="" Distance="" /> <!--
Id is of HotSpot-->
Search for road distance between hotspot and service
provider
or
<HotSpot SearchBy="HotSpotTypeId" Id="" Distance="" />
<!-- Id is of HotSpotType-->
Search for road distance between any hotspot of this
hotspot type and service provider
or
<HotSpot SearchBy="Coordinates" Id="" Distance="" /> <!-
- Id is of HotSpot-->
Search for linear distance between hotspot and service
provider

Distance is always in kilometers.


Accommodation- Information of required service provider handicap
HandicapFacility facilities.
Item Id: Id of the facility to filter search result.
Refer to the list of Key Values for the GUIDs.
Item Value: If facility has ValueType IntDigit a minimum
value can be provided, unless default value is 1.
Item Mandatory: If set to true (default), all selected
facilities must match with the service provider. If set to
false facility can match, how much it matches is in
element Match of search response of type Expanded.
PackageContainer Provide Id of any package container to search for
products only within the specific container. To get Ids
of specific package container use basic data request for
package container. It is also possible to search within
one specific categoriy of the package container. In this
case provide attribute CategoryId as well, if no category
id is provided or id is zero guid, search is done within all
categories of the package container.
TotalPriceFilter Set attributes Min and Max to filter the result to the
given price range. In case of
ResponseType=”Expanded” the filter is used on the
price for one unit always.

Search For Availabilities 122 of 241


DESKLINE 3.0 STANDARD INTERFACE

Example of a search:

<?xml version="1.0" encoding="utf-8"?>


<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://interface.deskline.net/DSI/XSD">
<Request Originator="FERATEL" Company="FERATEL" Language="en" CurrencyCode="EUR" >
<Range Code="TO">
<Item Id="E8446CC9-8388-4100-8646-544FF03004EA" />
</Range>
<SearchLines StartIndex="1" PageSize="15" SortOrder="Random" SearchType="OneProductPerHotel">
<SearchParameters Index="1" SalesChannel="BB556229-E7B1-4F21-9C6A-2BEA7120BF5A" Units="1"
Adults="2" Nights="7" From="2010-09-19" To="2010-09-26">
<ServiceProvider Id="f4a3d76e-68e9-4b27-b7d8-249398a6ee8f">
<Service LastAvailabilityChangeDays="7">
<ServiceFacility>
<Item Id="E36CEDCE-5082-4256-BA65-2DCBBCD49432" />
</ServiceFacility>
<ServiceClassification>
<Item Id="A999F70B-04B7-4EA3-BEB0-46259EEE88EA" />
</ServiceClassification>
<ServiceHandicapFacility>
<Item Id="77235371-70B1-4517-9EEF-C93CD5FDB646" />
</ServiceHandicapFacility>
</Service>
<Product AccommodationType="HotelRoom" ProductType="Package" BasePriceOnly="true">
<HolidayThemes>
<Item Id="DC26D00A-1B99-4C7C-A09A-AFC16578C144" />
</HolidayThemes>
</Product>
</ServiceProvider>
<Children>5,9</Children>
<Meal>FB</Meal>
<MaxPrice>454</MaxPrice>
<MinPrice>100</MinPrice>
<BookOnly IncludeOnlyOnRequest="true" >1</BookOnly>
<AccommodationFacility>
<Item Id="F2045434-62E0-4A09-B427-85002FCE18C3" />
</AccommodationFacility>
<Category>
<Item Id="AB4F2086-F06D-4DAC-8B99-09EDA5577C67" />
</Category>
<Stars>
<Item Id="EFFAF367-FA5F-4048-BB06-70B402F805E8" />
</Stars>
<Chain>
<Item Id="C5572A2A-4C87-4FFA-B314-BA2A850AD771" />
</Chain>
<MarketingGroup>
<Item Id="78CBF6CE-5BE7-4B86-B65F-4D578F83B7E8" />
</MarketingGroup>
<Classification>
<Item Id="50A3AF54-33DB-4612-8848-B9CF0A65C558" />
</Classification>
<AccommodationHandicapFacility>
<Item Id="9A6092A9-B6E9-4E97-85E0-2E91D5128934" />
</AccommodationHandicapFacility>
<TotalPriceFilter Min="500" Max="2000" />
</SearchParameters>
</SearchLines>
</Request>

Search For Availabilities 123 of 241


DESKLINE 3.0 STANDARD INTERFACE

</FeratelDsiRQ>

Example of a multiline search:

<?xml version="1.0" encoding="utf-8"?>


<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://interface.deskline.net/DSI/XSD">
<Request Originator="FERATEL" Company="FERATEL" Language="en" CurrencyCode="EUR" >
<Range Code="RG">
<Item Id="6C23D36D-BE29-414F-B550-B79518686C5D" />
</Range>
<SearchLines StartIndex="1" PageSize="15">
<SearchParameters Index="1" SalesChannel="BB556229-E7B1-4F21-9C6A-2BEA7120BF5A" Adults="3"
Nights="7" Units="1" From="2011-02-19" To="2011-02-26" MultilineSearchCondition="Or" />
<SearchParameters Index="2" SalesChannel="BB556229-E7B1-4F21-9C6A-2BEA7120BF5A" Adults="2"
Nights="7" Units="2" From="2011-02-19" To="2011-02-26" MultilineSearchCondition="Or" />
<SearchParameters Index="3" SalesChannel="BB556229-E7B1-4F21-9C6A-2BEA7120BF5A" Adults="1"
Nights="3" Units="1" From="2011-03-11" To="2011-03-14" />
</SearchLines>
</Request>
</FeratelDsiRQ>

Example of a Radius Search:


<?xml version="1.0" encoding="utf-8"?>
<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://interface.deskline.net/DSI/XSD">
<Request Originator="FERATEL" Company="FERATEL" Language="en">
<Range Code="RG">
<Item Id="F180FFD5-4FBF-4F2C-AC00-7E8B94462F2C" />
</Range>
<SearchLines StartIndex="1" PageSize="15">
<SearchParameters Index="1" SalesChannel="BB556229-E7B1-4F21-9C6A-2BEA7120BF5A" Adults="2"
Nights="7" Units="1" From="2011-03-19" To="2011-03-26">
<ServiceProvider>
<RadiusSearch Longitude="13.82479" Latitude="46.6188492" Distance="10"/>
</ServiceProvider>
</SearchParameters>
</SearchLines>
</Request>
</FeratelDsiRQ>

Example of a Package Container Search:


<?xml version="1.0" encoding="utf-8"?>
<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://interface.deskline.net/DSI/XSD">
<Request Originator="FERATEL" Company="FERATEL" Language="en">
<Range Code="RG">
<Item Id="F180FFD5-4FBF-4F2C-AC00-7E8B94462F2C" />
</Range>

Search For Availabilities 124 of 241


DESKLINE 3.0 STANDARD INTERFACE

<SearchLines StartIndex="1" PageSize="15">


<SearchParameters Index="1" SalesChannel="BB556229-E7B1-4F21-9C6A-2BEA7120BF5A" Adults="2"
Nights="7" Units="1" From="2013-04-03" To="2013-04-10">
<PackageContainer Id="de704591-8237-402b-830d-64e6b5219c97"/>
</SearchParameters>
</SearchLines>
</Request>
</FeratelDsiRQ>

Search For Availabilities 125 of 241


DESKLINE 3.0 STANDARD INTERFACE

DEFAULT RESPONSE (REPONSETYPE=”S TANDARD”)


Request field Description Can be empty? Multiple?
Status Status="0" Message="OK" / Status="1"
Message="Error message"
Result Index is the same number from the SearchParameters
to relate the response with request. TotalObjects is the
amount of results in total. In case of SearchType of
request was OneProductPerHotel or Standard
TotalObject refers to count of Service Providers in the
result. In case of search type EachProductSeparated it is
count of products.
ServiceProvider A collection of search results.
Code Object code of the service provider.
Name Name of the service provider.
TownName Name of the town of the service provider.
DistrictName Name of the district in the town of the service provider.
Rating Value Average points given for this service provider for all
ratings
Total Ratings Number of active ratings for this service provider.
Recommended Number of visitors recommended this parent with their
rating
Satisfaction Average satisfaction for this service provider for all
ratings
Products A collection of search results (products) in this service
provider.
Name Name of the product in the requested language.
Bookable Information, if the product is bookable, bookable on
request or not bookable at all.
MealCode The meal that is included in the total price for this
product. If a search is not done for a specific meal this
information can be used to find out which meal was
calculated.
Occupancy Standard, Minimum and Maximum occupancy for this
product.
Prices Attribute Currency displays the requested currency.

BasePrice and TotalPrice, the BasePrice without any


surcharges or reductions of the standard occupancy,
not the occupancy of the search request. Also refer to
price information from basic data if this price is per
Person or per Unit. This can be used to display a “day
price” information.

For BasePrice only: If the base price changes during the


stay the value is always taken from the first day of
arrival.

TotalPrice is the total price for the stay including all


additional fees and taxes. If search is done for 3 units,
the price is calculated for 3 units in total.

Important: if you are requesting the TotalPrice then it


is possible that in some cases the TotalPrice is 0. This
Search For Availabilities 126 of 241
DESKLINE 3.0 STANDARD INTERFACE

happens, when the basic data of the product is not


entered correctly and a total price can’t be calculated.
If a search result is returned with a TotalPrice of 0 it
should not be displayed to the guest.
SpecialPrice If SpecialPrice is in the result it’s the name of the
special price defined by the service provider
(LastMinute, EarlyBooker or user defined text)
indicating that the TotalPrice is a reduced price. This is
only returned when using the total price calculation.
Additionally price splitting is possible. E.g. service
provider defines stay 7 nights and pay 6 would be
shown like “Split(7:6)”. Price Splitting is possible in
combination with Last Mminute as well, so there would
be two Elements SpecialPrice listed.
AmountSaved If SpecialPrice is in the result it’s the name of the
special price defined by the service provider indicating
that the TotalPrice is a reduced price. The amount
saved is then returned in this element AmountSaved
and can still be 0! This is only returned when using the
total price calculation.
IsBestPrice True/false if this price is the best price that the service
provider offers for this product. This is not based on a
calculation but based on a flag set by the service
provider. The AmountSaved can still be 0 in this case!
This is only returned when using the total price
calculation.
DateFrom, DateTo The arrival and departure days are always provided
since it is possible to have a product more than once in
the search result but with different lengths of stay if the
request is not a fixed timeframe.
SettlerCode This is only relevant for bookings via DSI and will
represent the organization code of the guest settler.
The SettlerCode is mandatory when putting an item to
the shopping cart. See chapter booking for more
details.
SearchLineNo If a multiline search was done the element
SearchLineNo in the result indicates to which search
line the result refers to. Element is not listed if a single
line search was done.
DatabaseCode This is only relevant for bookings via DSI and will
represent the code of the local database where this
service provider can be found. The DatabaseCode is
mandatory when putting an item to the shopping cart.
See chapter booking for more details.

Response for the search example:

<?xml version="1.0"?>
<FeratelDsiRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" Status="0" Message="OK"
xmlns="http://interface.deskline.net/DSI/XSD">
<Result Index="1" TotalObjects="38">
<ServiceProvider Id="030e555c-8423-4043-bbb4-63555feb75a6">
<Code>PARKVI</Code>
<Name>Parkhotel Villach</Name>

Search For Availabilities 127 of 241


DESKLINE 3.0 STANDARD INTERFACE

<TownName>Innsbruck</TownName>
<DistrictName>Innsbruck Innenstadt</DistrictName>
<Rating Value="3.1" TotalRatings="7" Recommended="5" Satisfaction="1" />
<Products>
<Product Id="fb702717-b6a6-478c-8369-987442687424">
<Name>Doppelzimmer, Bad, WC, Meerblick</Name>
<Bookable>Yes</Bookable>
<Occupancy Standard="2" Min="1" Max="4" />
<Prices Currency="EUR">
<BasePrice>60.00</BasePrice>
<TotalPrice>720</TotalPrice>
<SpecialPrice>None</SpecialPrice>
<AmountSaved>0</AmountSaved>
<IsBestPrice>false</IsBestPrice>
</Prices>
<DateFrom>2010-09-19</DateFrom>
<DateTo>2010-09-26</DateTo>
<MealCode>BB</MealCode>
<SettlerCode>FERATEL</SettlerCode>
</Product>
</Products>
<DatabaseCode>FRT</DatabaseCode>
</ServiceProvider>
<ServiceProvider Id="0327882a-e538-4f4c-a4fd-18ce6f2f1195">
<Code>ROSE</Code>
<Name>Hotel Rosengarten</Name>
<TownName>Innsbruck</TownName>
<DistrictName>Gewerbegebiet Rossau</DistrictName>
<Rating Value="0.0" TotalRatings="0" Recommended="0" Satisfaction="0" />
<Products>
<Product Id="1cc7dd80-688f-4efc-b61a-c261b7c241a6">
<Name>Doppelzimmer, Dusche oder Bad, WC, kopie app.</Name>
<Bookable>Yes</Bookable>
<Occupancy Standard="2" Min="1" Max="3" />
<Prices>
<BasePrice>50.00</BasePrice>
<TotalPrice>700</TotalPrice>
<SpecialPrice>Bikeweek</SpecialPrice>
<AmountSaved>50</AmountSaved>
<IsBestPrice>false</IsBestPrice>
</Prices>
<DateFrom>2010-09-19</DateFrom>
<DateTo>2010-09-26</DateTo>
<MealCode>BB</MealCode>
<SettlerCode>FERATEL</SettlerCode>
</Product>
</Products>
<DatabaseCode>FRT</DatabaseCode>
</ServiceProvider>
</Result>
</FeratelDsiRS>

Response for the search example, nothing found:

<?xml version="1.0"?>
<FeratelDsiRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" Status="0" Message="OK"
xmlns="http://interface.deskline.net/DSI/XSD">
<Result Index="1" />
</FeratelDsiRS>

Search For Availabilities 128 of 241


DESKLINE 3.0 STANDARD INTERFACE

Based on the IDs in the response it is either possible to create a link to the Deskline 3.0 web application or to
use the result in a booking for the Deskline 3.0 Standard Interface. (See options in the example workflow).

I fyou want to get cancellation policies of the products found use GetCancellationInformation.

RESPONSE (REPONSETYPE=”EXPANDED”)
This new response type provides much more information in the search result to give customers more
possibilities. There are some major changes included compared to “Standard” response type. Please be aware
that changes in user interface are needed before switching to new response structure.

This search is service crossing! This means that when you are searching for more than one unit in standard
search you only get single products which fit to the amount of requested units. When there was one single
service provider with two different products for 2 adults each having one availability, in standard search this
service provider was not included in the result. In this new search it is included in the result, because all in all it
fulfills search criteria. Therefore we also had to change information in search result. All prices given are always
for one single unit! To give the guest the total price for his requested amount of units you have to multiply the
result with number of requested units. But always have a look at the Availabilities in Product element. This
attribute shows the amount of free units. Be aware that Availbilities on service level can be shared between
products within one service. So also include the AvialabilityReference information in your logic in front end to
provide correct results.

According to the information given in Availbailities you can show the guest that it is e.g. last available room or
e.g. that she or he would have the possibility to book more units if needed. Best way is to show pick list from 0
to max availabilities and always multiply users selection with UnitPrice to show total price for all requested
units.

Request field Description Can be empty? Multiple?


Status Status="0" Message="OK" / Status="1"
Message="Error message"
Result Index is the same number from the SearchParameters
to relate the response with request. TotalObjects is the
amount of results in total. In case of SearchType of
request was OneProductPerHotel or Standard
TotalObject refers to count of Service Providers in the
result. In case of search type EachProductSeparated it is
count of products.
CurrencyCode valid for the whole search result.
ServiceProviderData A collection of search results.
Id Id of service provider.
Code Object code of the service provider.
Name Name of the service provider.
TownId Id of the town of the service provider.
TownName Name of the town of the service provider.
DistrictName Name of the district in the town of the service provider.
DatabaseCode This is only relevant for bookings via DSI or to create
booking link and will represent the code of the local
database where this service provider can be found. The
DatabaseCode is mandatory when putting an item to
the shopping cart. See chapter booking for more
details.
SettlerCode This is only relevant for bookings via DSI and will
Search For Availabilities 129 of 241
DESKLINE 3.0 STANDARD INTERFACE

represent the organization code of the guest settler.


The SettlerCode is mandatory when putting an item to
the shopping cart. See chapter booking for more
details.
Rating Information about Ratings for the service provider
Value Average points given for this service provider for all
ratings. Zero if no ratings are available.
TotalRatings Number of active ratings for this service provider.
Recommended Number of visitors recommended this parent with their
rating. Zero if rating type is None, TrustYou or
HotelNavigator.
Satisfaction Average satisfaction for this service provider for all
ratings. Zero if rating type is None, TrustYou or
HotelNavigator.
Type Enumeration None, Deskline, TrustYou, HotelNavigator.
Gives information about the source of the ratings.
Match Information about the matching between given
facilities in request.
Facility Percentage value between 0 and 100 how much
requested facilities from request match. If facilities are
requested as mandatory only 100 percent matching
items are in result, if mandatory in request is set to
false also items with less than a 100 percent match are
shown.
HandicapFacility Percentage value between 0 and 100 how much
requested handicap facilities from request match. If
handicap facilities are requested as mandatory only 100
percent matching items are in result, if mandatory in
request is set to false also items with less than a 100
percent match are shown.
GeoDistance Information about distance to a requested place.
HotSpotName Name of the hotspot the distance refers to. Empty if
search request was done without hot spot.
Distance Distance to the hot spot in hot spot name in kilometers.
Zero if no hotspot was provided in search request.
Services Collection of services within one service provider
Service Specific service information
Id Id of the service found
Name Name of service in requested language
UseAvailability Does this service use availabilities or not. If false related
products are not bookable because no details
information about exact count of availabilities
available.
Rooms Number of rooms of the service, zero if not definied.
BedRooms Number of bed rooms of the service, zero if not
definied.
Size Size of the service in square meter, zero if not definied.
Match Information about the matching between given service
related facilities in request.
Facility Percentage value between 0 and 100 how much
requested service facilities from request match. If
facilities are requested as mandatory only 100 percent
matching items are in result, if mandatory in request is

Search For Availabilities 130 of 241


DESKLINE 3.0 STANDARD INTERFACE

set to false also items with less than a 100 percent


match are shown.
HandicapFacility Percentage value between 0 and 100 how much
requested service handicap facilities from request
match. If handicap facilities are requested as
mandatory only 100 percent matching items are in
result, if mandatory in request is set to false also items
with less than a 100 percent match are shown.
Products A collection of search results (products) in this service
inside service provider.
Product Specific product information
Id Name of the product.
Name Name of the product in the requested language.
OrgPaymentRequired Defines the payment type how the product has to be
inserted into shopping cart. If true set PaymentType to
OrganisationPayment when putting product into
shopping cart.
InclVT Defines if base price already includes visitor tax or not.
Only refers to base price! Total price (=”UnitPrice”)
always includes the visitor tax if it was entered by
customer. If VT price information in PriceDetails is zero,
VT is not included in price, because system has no
information about hight of VT!
Availability Number of available units of this product. Very
important information for front end. This response type
always gives back price for one unit. To get total price
for requested number of units multiply with it, but do
not exceed number of given availabilities here. If
number of requested units exceeds available units
given here, take the rest from next according service
and so on.
AvailabilityReference Enumeration Service or Product. Very important
information where the availability belongs to. Products
within one service, which have AvailabilityRefererence
Service, take availabilities from the same amount. So if
inside one service there are two products both
availabilities refer to service and amount is each one, it
is the same availability, which means only one of
products can be booked once, not both.
ServiceLineNo If a multiline search was done the element
SearchLineNo in the result indicates to which search
line the result refers to. Attribute has value 1 if a single
line search was done.
Occupancy Information about possible occupancies for this
product
StandardOccupancy Standard occupancy for this product.
MinOccupancy Minimum occupancy for this product.
MaxOccupancy Maximum occupancy for this product.
MinAdults Minimum adult occupancy for this product.
MaxAdults Maximum adult occupancy for this product.
MinChild Minimum children occupancy for this product.
MaxChild Maximum children occupancy for this product.
PriceRule Enumeration PerPerson, PerUnit, Total. Defines how

Search For Availabilities 131 of 241


DESKLINE 3.0 STANDARD INTERFACE

the base price is entered and how to calculate prices.


PerNights Defines for how much nights base price is entered.
Prices Element includes all price relevant information.
Important: All prices shown here are always for ONE
unit. To show total price to customers multiply with
units requested, but never exceed value given in
Availability on Product level!
Price Includes price related information.
UnitPrice Total price for ONE unitn for the requested period and
occupancy.
DateFrom, DateTo The arrival and departure days are always provided
since it is possible to have a product more than once in
the search result but with different lengths of stay if the
request is not a fixed timeframe.
Duration Duration from search request.
PayNights Shows for how much nights guest would have to pay.
There are special offers like stay 7 nights pay 6.
SplitPrice Shows if this product is one of the above special offers.
MealCode The meal that is included in the total price for this
product. If a search is not done for a specific meal this
information can be used to find out which meal was
calculated.
Bookable Information, if the product is bookable, bookable on
request or not bookable at all. Enumeration Yes,
YesOnRequestOnly, No.
InGap Shows if this result is within a specific gap. Gaps can be
entered separately in our system. Eg usually a product
is only bookable for Saturday to Saturday, but because
of special circumstances the room is free from
Thursday to Saturday. The Landlord marks this period
as a bookable gap to improve occupancy rate.
IsBestPrice True/false if this price is the best price that the service
provider offers for this product. This is not based on a
calculation but based on a flag set by the service
provider.
SpecialPrice Marks if this offer is Special Price like LastMinute,
EarlyBooker, BestPrice or any individual special.
SpecialPriceName Name of the special price
AmountSaved If product has special price saved amount is also
provided.
RevenueName This attribute shows the name of the Revenue
surcharge or discount. This attribute is only included in
response when the search request is only for one
specified serviceprovider
RevenueAmount This attribute shows the original price without
reveneue settings, so you can display the difference for
the guest. This attribute is only included in response
when the search request is only for one specified
serviceprovider
PriceDetails Element to provide further information about
components, always reffering to one unit. Sum of all
this componants leads to total UnitPrice in Price
element.
TotalAdultPrice Total price for adults

Search For Availabilities 132 of 241


DESKLINE 3.0 STANDARD INTERFACE

TotalAdultMeal Total meal price for adults


TotalAdultVT Total price for adult’s visitor tax
TotalChildrenPrice Total price for children
TotalChildrenMeal Total meal price for children
TotalChildrenVT Total price for children’s visitor tax
TotalBedlinen Total price for bedlinen
TotalFinalCleaning Total price for final cleaning
TotalUserExtra Total price for any further user extras
ExtraName Name of user extras, if more than one, comma
separated list.
BaseInformation Provides some base information about the product and
its price structure
BasePrice Base price of the product for StandardOccupancy and
per x nights (refer to information given in Occupancy
element)
StandardMealCode Standard meal code for this product. Landlord can
discounts or surcharges for different meal codes
BasePriceWithMeal If search result is for different meal code than standard
base price with meal code can be different than base
price
MealPrice Difference between BasePrice and BasePriceWithMeal
CancellationInformation Provides information about the cancellation conditions
FreeCancellation Enumeration true/false. If true means at the moment
free cancellation but there is might a due date
DateUntil Date until when cancellation is free, if there is no
settings because cancellation is not free at all, Date is
system neutral date "1980-01-01"
TimeUntil Time until when cancellation is free corresponding to
DateUntil
CalculationBase In case of 0 the base for cancellation fees is the whole
stay. If >0 the amount of first days as base for
cancellation fee. E.g. cancellation fee is 10% of whole
stay or 50% of the first 2 days.
Percentage Percentage value for cancellation fee.

Response for the search example ResponseType=”Expanded”:

<?xml version="1.0" encoding="utf-8"?>


<FeratelDsiRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" Status="0" Message="OK"
xmlns="http://interface.deskline.net/DSI/XSD">
<Result Index="1" TotalObjects="1" CurrencyCode="EUR">
<ServiceProviderData Id="dc1defe3-999a-4097-a5bf-7bd86a14e28a" Code="SIM22" Name="Simotel"
TownId="5c7e1d37-0060-4811-a996-a8b36094d01e" TownName="Tux" DistrictName="Hintertux"
DatabaseCode="FRT" SettlerCode="FERATEL">
<Rating Value="0" TotalRatings="0" Recommended="0" Satisfaction="0" Type="None" />
<Match Facility="100" HandicapFacility="100" />
<GeoDistance HotSpotName="" Distance="0.0" />
<Services>
<Service Id="94e9f02a-5001-446f-9b7b-78b43ef558da" Name="Double room, bath, toilet, superior"
UseAvailability="true" Rooms="0.0" BedRooms="0" Size="0">
<Match Facility="100" HandicapFacility="100" />

Search For Availabilities 133 of 241


DESKLINE 3.0 STANDARD INTERFACE

<Products>
<Product Id="c584a48f-0fbf-458f-a9c9-bdb18f489d5d" Name="Doppelzimmer, LM"
OrgPaymentRequired="false" InclVT="false" Availability="100" AvailabilityReference="Service"
SearchLineNo="1">
<Occupancy StandardOccupancy="2" MinOccupancy="1" MaxOccupancy="3" MinAdults="1"
MaxAdults="3" MinChild="0" MaxChild="1" PriceRule="PerPerson" PerNights="1" />
<Prices>
<Price UnitPrice="2580.4" DateFrom="2013-10-17" DateTo="2013-10-24" Duration="7" PayNights="7"
SplitPrice="false" MealCode="HB" Bookable="Yes" InGap="false" IsBestPrice="false" SpecialPrice="LastMinute"
SpecialPriceName="Last Minute " AmountSaved="283.6">
<PriceDetails TotalAdultPrice="2520" TotalAdultMeal="0" TotalAdultVT="28" TotalChildrenPrice="0"
TotalChildrenMeal="0" TotalChildrenVT="0" TotalBedlinen="2.7" TotalFinalCleaning="29.7" TotalUserExtra="0"
ExtraName="" />
<BaseInformation BasePrice="200.00" StandardMealCode="HB" BasePriceWithMeal="200.00"
MealPrice="0.00" />
<CancellationInformation FreeCancellation="false" DateUntil="2013-19-17" TimeUntil="00:00"
CalculationBase="0" Percentage="30.00" />
<CancellationInformation FreeCancellation="false" DateUntil="2013-10-15" TimeUntil="18:00"
CalculationBase="0" Percentage="90.00" />
</Price>
</Prices>
</Product>
<Product Id="dfa7d798-9c15-4c93-b172-fe20277590dd" Name="Doppelzimmer EB"
OrgPaymentRequired="false" InclVT="true" Availability="100" AvailabilityReference="Service"
SearchLineNo="1">
<Occupancy StandardOccupancy="2" MinOccupancy="1" MaxOccupancy="3" MinAdults="1"
MaxAdults="3" MinChild="0" MaxChild="0" PriceRule="PerPerson" PerNights="1" />
<Prices>
<Price UnitPrice="1400" DateFrom="2013-10-17" DateTo="2013-10-24" Duration="7" PayNights="7"
SplitPrice="false" MealCode="HB" Bookable="Yes" InGap="false" IsBestPrice="false" SpecialPrice="None"
SpecialPriceName="" AmountSaved="0">
<PriceDetails TotalAdultPrice="1372" TotalAdultMeal="0" TotalAdultVT="28" TotalChildrenPrice="0"
TotalChildrenMeal="0" TotalChildrenVT="0" TotalBedlinen="0" TotalFinalCleaning="0" TotalUserExtra="0"
ExtraName="" />
<BaseInformation BasePrice="100.00" StandardMealCode="HB" BasePriceWithMeal="100.00"
MealPrice="0.00" />
<CancellationInformation FreeCancellation="false" DateUntil="1980-01-01" TimeUntil="00:00"
CalculationBase="0" Percentage="90.00" />
</Price>
</Prices>
</Product>
</Products>
</Service>
<Service Id="45424b08-922c-4c48-8550-c23d32b24243" Name="Single room, shower or bath, toilet,
quiet" UseAvailability="true" Rooms="1.0" BedRooms="1" Size="15">
<Match Facility="100" HandicapFacility="100" />
<Products>
<Product Id="14e87834-11f5-4b10-b15e-b489974ff70d" Name="Einzelzimmer, Dusche oder Bad, WC,
ruhig" OrgPaymentRequired="false" InclVT="false" Availability="10" AvailabilityReference="Service"
SearchLineNo="1">
<Occupancy StandardOccupancy="1" MinOccupancy="1" MaxOccupancy="2" MinAdults="1"
MaxAdults="2" MinChild="0" MaxChild="2" PriceRule="PerPerson" PerNights="1" />
<Prices>
<Price UnitPrice="28" DateFrom="2013-10-17" DateTo="2013-10-24" Duration="7" PayNights="6"
SplitPrice="true" MealCode="BB" Bookable="YesOnlyOnRequest" InGap="false" IsBestPrice="false"
SpecialPrice="None" SpecialPriceName="Split(7:6)" AmountSaved="0">
<PriceDetails TotalAdultPrice="0" TotalAdultMeal="0" TotalAdultVT="28" TotalChildrenPrice="0"
TotalChildrenMeal="0" TotalChildrenVT="0" TotalBedlinen="0" TotalFinalCleaning="0" TotalUserExtra="0"
ExtraName="" />
<BaseInformation BasePrice="100.00" StandardMealCode="BB" BasePriceWithMeal="100.00"
MealPrice="0.00" />

Search For Availabilities 134 of 241


DESKLINE 3.0 STANDARD INTERFACE

<CancellationInformation FreeCancellation="false" DateUntil="1980-01-01" TimeUntil="00:00"


CalculationBase="0" Percentage="90.00" />
</Price>
</Prices>
</Product>
</Products>
</Service>
</Services>
</ServiceProviderData>
</Result>
</FeratelDsiRS>

Response for the search example, nothing found:

<?xml version="1.0" encoding="UTF-8"?>


<FeratelDsiRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" Status="0" Message="OK"
xmlns="http://interface.deskline.net/DSI/XSD">
<Result Index="1" TotalObjects="0" CurrencyCode="EUR" />
</FeratelDsiRS>

Based on the IDs in the response it is either possible to create a link to the Deskline 3.0 web application or to
use the result in a booking for the Deskline 3.0 Standard Interface. (See options in the example workflow).

GET CANCELLATION INFORMATION


If you use search for availabilities with response type standard you might want to show the guest the
cancellation conditions which you can request. This request is also suitable to provide additional cancellation
information in booking process. This request is part of search so please sen to web service URL of search.

Request
More
Can be
Request field Description empty?*
than one
possible?

Originator The code of the point of sale requesting the data.


Provided by feratel.
Company The code of the company requesting the data. Provided
by feratel.
CurrencyCode If this element is not send the defined Currency for the
Point of Sale is taken (Originator).
GetCancellationInformation 3 character DB code provided in response of search
DBCode
GetCancellationInformation Id of sales channel provided by Feratel and already in use
SalesChannelId for search
GetCancellationInformation Id of the service provider
ServiceProviderId
GetCancellationInformation Id of the product
ProductId
GetCancellationInformation Occupancy information, number of adults
Adults
GetCancellationInformation Occupancy information, comma separated children ages
Children
GetCancellationInformation Arrival date
From

Get Cancellation Information 135 of 241


DESKLINE 3.0 STANDARD INTERFACE

GetCancellationInformation To Departure date

<?xml version="1.0" encoding="utf-8"?>


<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://interface.deskline.net/DSI/XSD">
<Request Originator="FERATEL" Company="FERATEL">
<GetCancellationInformation DBCode="FRT" SalesChannelId="BB556229-E7B1-4F21-9C6A-2BEA7120BF5A"
ServiceProviderId="DC1DEFE3-999A-4097-A5BF-7BD86A14E28A" ProductId="c584a48f-0fbf-458f-a9c9-
bdb18f489d5d" Adults="2" Children="" From="2013-10-26" To="2013-11-02"/>
</Request>
</FeratelDsiRQ>

Response
More than
Can be
Response field Description empty?*
one
possible?

CancellationInformation Element containing all cancellation information. Can be


multiple according to he different settings for different
days between arrival and cancellation
FreeCancellation Enumeration true/false. If true means at the moment free
cancellation but there is might a due date
DateUntil Date until when cancellation is free, if there is no settings
because cancellation is not free at all, Date is system
neutral date "1980-01-01"
TimeUntil Time until when cancellation is free corresponding to
DateUntil
CalculationBase In case of 0 the base for cancellation fees is the whole
stay. If >0 the amount of first days as base for cancellation
fee. E.g. cancellation fee is 10% of whole stay or 50% of
the first 2 days.
Percentage Percentage value for cancellation fee.
Amount Calculated amount of cancellation fee after due date.
CurrencyCode International 3 character currency code

Example

<?xml version="1.0" encoding="UTF-8"?>


<FeratelDsiRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" Status="0" Message="OK"
xmlns="http://interface.deskline.net/DSI/XSD">
<Result Index="1">
<CancellationInformation FreeCancellation="true" DateUntil="2013-10-21" TimeUntil="00:00"
CalculationBase="3" Percentage="5.00" Amount="143" CurrencyCode="EUR" />
<CancellationInformation FreeCancellation="true" DateUntil="2013-11-21" TimeUntil="18:00"
CalculationBase="3" Percentage="50.00" Amount="1430" CurrencyCode="EUR" />
</Result>
</FeratelDsiRS>

Get Cancellation Information 136 of 241


DESKLINE 3.0 STANDARD INTERFACE

GET PAYMENT INFORMATION


If you use search for availabilities you might want to show the guest the payment conditions which you can
request. This request is also suitable to provide additional payment information in booking process. This
request is part of search so please sen to web service URL of search.

Request
More
Can be
Request field Description empty?*
than one
possible?

Originator The code of the point of sale requesting the data.


Provided by feratel.
Company The code of the company requesting the data. Provided
by feratel.
CurrencyCode If this element is not send the defined Currency for the
Point of Sale is taken (Originator).
GetPaymentInformation DBCode 3 character DB code provided in response of search
GetPaymentInformation Id of sales channel provided by Feratel and already in use
SalesChannelId for search
GetPaymentInformation Id of the service provider
ServiceProviderId
GetPaymentInformation Id of the product
ProductId
GetPaymentInformation Adults Occupancy information, number of adults
GetPaymentInformation Occupancy information, comma separated children ages
Children
GetPaymentInformation From Arrival date
GetPaymentInformation To Departure date

<?xml version="1.0" encoding="utf-8"?>


<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://interface.deskline.net/DSI/XSD">
<Request Originator="FERATEL" Company="xxx">
<GetPaymentInformation DBCode="FRT" SalesChannelId="BB556229-E7B1-4F21-9C6A-2BEA7120BF5A"
ServiceProviderId="DC1DEFE3-999A-4097-A5BF-7BD86A14E28A" ProductId="c584a48f-0fbf-458f-a9c9-
bdb18f489d5d" Adults="2" Children="" From="2014-03-26" To="2014-04-02"/>
</Request>
</FeratelDsiRQ>

Response
More than
Can be
Response field Description empty?*
one
possible?

PaymentInformation Element containing all payment information


HasPrePayment Can be true or false and defines if a pre payment will be
required
PrePaymentPercent Percentage value of the required pre payment else 0
PrePayDueDays In case of pre payment via invoice this value gives the
information how much days after the booking was done
the pre payment is due.
FinalPayDueDays If a final payment is reuired this values shows the days

Get Payment Information 137 of 241


DESKLINE 3.0 STANDARD INTERFACE

before arrival until the final payment is due


PossiblePaymentMethods For how many days before arrival the payment method
InvoicePossibleDays invoice is possible
PossiblePaymentMethods Each value can be true or false and gives the information
Invoice, CreditCard, ELV, if the method is possible or not
Sofortueberweisung, iDeal
ServiceProviderPayment Is service provider payment a valid payment type
Active
ServiceProviderPayment Is a guarantee requested
GuaranteeRequested
ServiceProviderPayment Is the guarantee a required or optional one
GuaranteeType
Guarantee Type At the moment a guarantee can only be given by
CreditCard, else type is None. May further methods will
follow in future.
SplitPayment Active Is split payment a valid payment type
OrganisationPayment Active Is organisation payment a valid payment type

Example

<?xml version="1.0" encoding="utf-8"?>


<FeratelDsiRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" Status="0" Message="OK"
xmlns="http://interface.deskline.net/DSI/XSD">
<Result Index="0">
<PaymentInformation HasPrePayment="true" PrePaymentPercent="34.00" PrePayDueDays="7"
FinalPayDueDays="0">
<PossiblePaymentMethods InvoicePossibleDays="7" Invoice="true" CreditCard="false" ELV="false" />
<ServiceProviderPayment Active="true" GuaranteeRequested="false" GuaranteeType="Required">
<Guarantee Type="None" />
</ServiceProviderPayment>
<SplitPayment Active="false" />
<OrganisationPayment Active="false" />
</PaymentInformation>
</Result>
</FeratelDsiRS>

Additional Information

The Response Information must always been seen from the position of the destination.
If the Payment Elements SplitPayment and Organisation Payment Active = true, and you want to create the
shoppingcart with on of this PaymentTypes, all possible PaymentMethods which are on active are valid for this
typs, in contrast to ServiceProviderPayment there are only the Methods Invoice and CreditCard valid.

If ServiceProviderPayment = true it is also possible that there are not active invoice neither creditcard method
in this case you have to create the shoppingcart with PaymentMethod=”NoPayment” this type is only
permitted for ServiceProviderPayment.

Get Payment Information 138 of 241


DESKLINE 3.0 STANDARD INTERFACE

SEARCH FOR ADDITIONAL SERVICES


Additional Services are all the services that are offered from service providers that are not overnight stays. For
example ski tickets or entrance to the spa.

The search result will list all the available additional services including the variations for different durations and
starting days and starting times. These choices should be displayed accordingly.

The search response will be internally cached for 200 seconds after the last query. This way, paging will also be
possible. If the same search is made after 200 seconds, a new result set will be generated.

REQUEST
Request field Description Can be empty? Multiple?
Originator The code of the point of sale requesting the data.
Provided by feratel.
Company The code of the company requesting the data.
Provided by feratel.
Range and GUIDs First, a range code to select the data must be defined.
IDs This is an enumeration if it is a region (RG) or a town
(TO) or a district (DI) for example. It is also possible to
select one or more data owners instead of a
geographical selection. The IDs of
regions/towns/districts are part of the KeyValues
function. If there is a need to call data owners (DO)
directly, the IDs are provided by feratel. The top
location (i.e. highest/widest range possible) will be
provided by feratel to get started (see range example
in KeyValues.xml)
Language The language that is expected of the response.
CurrencyCode If this element is not send the defined Currency for the
Point of Sale is taken (Originator). If a CurrencyCode
different to the point of sale currency is send all the
prices in the search result get converted automatically.
CurrencyCode is the 3-digits long international
currency code (e.g. EUR, CHF,…)
AdditionalServiceSearch Container Element for the additional services search.
Paging StartIndex and PageSize are used for paging, e.g. if the
response should contain 20 items, starting at the 70th
search result. The total amount of available objects will
be available in the Response (TotalObjects). The
maximum page size allowed is 300 but should not be
used with total price calculation because of
performance reasons.
Examples:
StartIndex=1, PageSize=100 – will return 100 results.
StartIndex=1, PageSize=10 – will return 10 results.
StartIndex=11, PageSize=10 – will return the next 10
results.
SortOrder Enumeration. This can be used to sort the result
directly at the interface to (for example) only get the
first 20 results, ordered by Name. Combinations of the
following values are possible:
Random: Randomizes the result.
Price, PriceDesc: Sorted by total price ascending or

Search For Additional Services 139 of 241


DESKLINE 3.0 STANDARD INTERFACE

descending. Depending on the request this is either


total price or base price.
Bookable, BookableDesc: Sorted by bookable
ascending or descending.
Rating, RatingDesc: Sorted by overall rating value
ascending or descending.
Town, TownDesc: Sorted by town name ascending or
descending.
Name, NameDesc: Sorted by service provider name
ascending or descending.
Example: SortOrder=”Bookable Price” or
SortOrder=”Random” or SortOrder=”Town Name”
SearchParameters Every SearchParameters element can have a different
occupancy and different facility requirements. Only
one element possible at the moment.
Index Search parameter index will be reflected in the
response. Once more than one SearchParameters
element is possible the index is necessary to relate
response to request.
SalesChannel The GUID of the SalesChannel for the products.
Assigned by feratel.
Units Amount of required units
From Date of arrival
To Date of departure
Days For how much days is the service requested
ServiceProvider ID To search inside one service provider only, the
Deskline 3.0 GUID can be provided in the request.
Passing the ID to one hotel will guarantee the best
performance available.
ServiceProvider Filters- Information of required service provider facilities. All
Facility selected facilities must match with the service
provider. Refer to the list of Key Values for the GUIDs.
PreSelected- <PreSelectedServiceProviderIDs> can be used to
ServiceProviderIDs search inside more than one service provider based on
the SP-ID. This can also be used for targeted searches if
more than one hotel should be checked.
Service Container Element for service filters inside the service
provider element.
Service ID To search inside one specific service, the service GUID
can be provided in the request in addition to the
service provider ID.
ServiceFacility Information of required service facilities. All selected
facilities must match with the service. Refer to the list
of Key Values for the GUIDs.
Product Container Element for product filters inside the service
provider element.
Product ID To search inside one specific product, the Deskline 3.0
product GUID can be provided in the request in
addition to the service provider ID.
HolidayThemes Used to query for holiday themes like “wedding”,
“sports”, and so on. Refer to the list of Key Values for
the GUIDs.
BookOnly Indicator if only bookable or all products should be
found.

Search For Additional Services 140 of 241


DESKLINE 3.0 STANDARD INTERFACE

BookOnly true/false value, true by default. Provides possibility to


IncludeOnlyOnRequest get back only those products directly bookable.

Example of a search:

<?xml version="1.0" encoding="utf-8"?>


<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://interface.deskline.net/DSI/XSD">
<Request Originator="FERATEL" Company="FERATEL" Language="en"
CurrencyCode="EUR">
<Range Code="RG">
<Item Id="F180FFD5-4FBF-4F2C-AC00-7E8B94462F2C" />
</Range>
<AdditionalServicesSearch StartIndex="1" PageSize="2">
<SearchParameters Index="1" SalesChannel="59994450-0280-4CC1-B097-
5C1D7EB09FAE" Days="7" Units="1" From="2010-10-29" To="2010-11-05" />
</AdditionalServicesSearch>
</Request>
</FeratelDsiRQ>

RESPONSE
Request field Description Can be empty? Multiple?
Status Status="0" Message="OK" / Status="1"
Message="Error message"
Result Index is the same number from the SearchParameters
to relate the response with request. TotalObjects is the
amount of results in total.
ServiceProvider A collection of search results.
Id ID of the service provider.
Availability Information of how much availabilities of this additional
service products are left. -1 if endless availabilities
Name Name of the service provider.
AdditionalServices A collection of search results (products) in this service
provider.
Products A collection of search results (products) in this service
provider.
Name Name of the product in the requested language.
Bookable Information, if the product is bookable, bookable on
request or not bookable at all.
Prices Attribute Currency displays the requested currency.

BasePrice for this service per unit.


StartDay Day when this product is available.
StartTime Time of day when this product is available
Duration Type (Hour, Minute, Day, None) and value for the
product, i.e. a guided hiking tour for 4 hours.
MinParticipants Minimum amount of participants for the service to be
confirmed. I.e. a guided hiking tour requires at least 5
participants or it will be cancelled.

Search For Additional Services 141 of 241


DESKLINE 3.0 STANDARD INTERFACE

SettlerCode This is only relevant for bookings via DSI and will
represent the organization code of the guest settler.
The SettlerCode is mandatory when putting an item to
the shopping cart. See chapter booking for more
details.
DatabaseCode This is only relevant for bookings via DSI and will
represent the code of the local database where this
service provider can be found. The DatabaseCode is
mandatory when putting an item to the shopping cart.
See chapter booking for more details.

Response for the search example:

<?xml version="1.0" encoding="UTF-8"?>


<FeratelDsiRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" Status="0" Message="OK"
xmlns="http://interface.deskline.net/DSI/XSD">
<Result Index="1" TotalObjects="0">
<ServiceProvider Id="9da77d25-d845-45b1-988e-cf39f6a487a5">
<Name>Rundflüge Flattach</Name>
<AdditionalServices>
<Products>
<Product Id="6a6d2198-0375-4284-aee8-9fdf23cb4b3f" Availability="-1" >
<Name>Round trip</Name>
<Bookable>Yes</Bookable>
<Prices Currency="EUR">
<BasePrice>200.00</BasePrice>
</Prices>
<StartDay>2011-08-19</StartDay>
<StartTime>00:00:00</StartTime>
<Duration Type="Day">2</Duration>
<MinParticipants>0</MinParticipants>
<SettlerCode>FERATEL</SettlerCode>
</Product>
<Product Id="6a6d2198-0375-4284-aee8-9fdf23cb4b3f" Availability="10" >
<Name>Round trip</Name>
<Bookable>Yes</Bookable>
<Prices Currency="EUR">
<BasePrice>200.00</BasePrice>
</Prices>
<StartDay>2011-08-20</StartDay>
<StartTime>00:00:00</StartTime>
<Duration Type="Day">2</Duration>
<MinParticipants>0</MinParticipants>
<SettlerCode>FERATEL</SettlerCode>
</Product>
</Products>
</AdditionalServices>
<DatabaseCode>FRT</DatabaseCode>
</ServiceProvider>
<ServiceProvider Id="46b85c22-4541-4a57-8d7e-1f6b19b6638c">
<Name>Wanderung CHF</Name>
<AdditionalServices>
<Products>
<Product Id="8e2a8b16-bc98-463b-bc56-171352f8ad31" Availability="3" >
<Name>Ballonfahrt CHF</Name>

Search For Additional Services 142 of 241


DESKLINE 3.0 STANDARD INTERFACE

<Bookable>Yes</Bookable>
<Prices Currency="EUR">
<BasePrice>9.12</BasePrice>
</Prices>
<StartDay>2011-08-19</StartDay>
<StartTime>00:00:00</StartTime>
<Duration Type="Day">1</Duration>
<MinParticipants>0</MinParticipants>
<SettlerCode>FERATEL</SettlerCode>
</Product>
</Products>
</AdditionalServices>
<DatabaseCode>FRT</DatabaseCode>
</ServiceProvider>
</Result>
</FeratelDsiRS>

Search For Additional Services 143 of 241


DESKLINE 3.0 STANDARD INTERFACE

SEARCH FOR DESTINATION PACKAGES


The search function that the DSI uses is the same function as for the Deskline 3.0 Web application and the
Deskline 3.0 ExpertClient and therefore supports the same functionality.

The search for destination packages has two steps. The search result of the first search step will provide the
basic information of all packages which fits to the search criteria. The second search will provide all details to
one special package (see chapter “search for destination package details”).

The search response will be internally cached for 200 seconds after the last query. This way, paging will also be
possible. If the same search is made after 200 seconds, a new result set will be generated.

REQUEST
Request field Description Can be empty? Multiple?
Originator The code of the point of sale requesting the data.
Provided by feratel.
Company The code of the company requesting the data. Provided
by feratel.
Range and GUIDs First, a range code to select the data must be defined.
IDs This is an enumeration if it is a region (RG) or a town (TO)
or a district (DI) for example. It is also possible to select
one or more data owners instead of a geographical
selection. The IDs of regions/towns/districts are part of
the KeyValues function. If there is a need to call data
owners (DO) directly, the IDs are provided by feratel. The
top location (i.e. highest/widest range possible) will be
provided by feratel to get started (see range example in
KeyValues.xml)
Language The language that is expected of the response.
PackageSearch - Paging StartIndex and PageSize are used for paging, e.g. if the
response should contain 20 items, starting at the 70th
search result. The total amount of available objects will
be available in the Response (TotalObjects). The
maximum page size allowed is 300 but should not be
used with total price calculation because of performance
reasons.
Examples:
StartIndex=1, PageSize=100 – will return 100 results.
StartIndex=1, PageSize=15 – will return 15 results.
StartIndex=16, PageSize=15 – will return the next 15
results.
PackageSearch - Enumeration. This can be used to sort the result directly
SortOrder at the interface to (for example) only get the first 15
results, ordered by Name. Combinations of the following
values are possible:
Name, NameDesc: Sorted by name ascending or
descending.
StartDate, StartDateDesc: Sorted by start date ascending
or descending.
Duration, DurationDesc: Sorted by duration ascending or
descending.
People, PeopleDesc: Sorted by minimal amount of adults
ascending or descending.

Search For Destination Packages 144 of 241


DESKLINE 3.0 STANDARD INTERFACE

Example: SortOrder=”Name” or
SortOrder=”DurationDesc”
SearchParameters SearchParameters include the different search criteria.
Only one element possible for package search.
Index For package search always 1
SalesChannel The GUID of the SalesChannel for the packages. Assigned
by feratel.
StartDate Required arrival date of guest
Name Name of package
ProviderCode Code of service provider to search inside one service
provider only. When passing a code, still a search is done
for the provided range because it’s possible that the code
is not unique.
ProviderName Name of service provider. When passing a name, still a
search is done for the provided range because it’s
possible that the name is not unique.
ToleranceDays Tolerance days plus and minus of arrival date of guest. If
a guest says I want to arrive on 2011-02-17 but it doesn’t
matter if I arrive one day before or after set
ToleranceDays to one.
Note: Code/Name is either/or: if a Code is provided, Name will not be checked.
PreSelected- <PreSelectedHolidayThemeIDs> Information of required
HolidayThemeIDs package classifications. All selected classifications must
match with the package. Refer to the list of Key Values for
the GUIDs.

Example of a search:

<?xml version="1.0" encoding="utf-8"?>


<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://interface.deskline.net/DSI/XSD">
<Request Originator="FERATEL" Company="FERATEL" Language="en" >
<Range Code="RG">
<Item Id="F180FFD5-4FBF-4F2C-AC00-7E8B94462F2C" />
</Range>
<PackagesSearch StartIndex="1" PageSize="15" >
<SearchParameters Index="1" SalesChannel="BB556229-E7B1-4F21-9C6A-2BEA7120BF5A" StartDate="2011-02-18"
Name="test"
ToleranceDays="3">
<PreSelectedHolidayThemeIDs>
<Item>25f0588a-a040-48c4-a555-fa18d17a134e</Item>
</PreSelectedHolidayThemeIDs>
</SearchParameters>
</PackagesSearch>
</Request>
</FeratelDsiRQ>

RESPONSE
Request field Description Can be empty? Multiple?
Status Status="0" Message="OK" / Status="1"
Message="Error message"
Result Index is the same number from the SearchParameters

Search For Destination Packages 145 of 241


DESKLINE 3.0 STANDARD INTERFACE

to relate the response with request. TotalObjects is the


amount of results in total.
StartDates A collection of search results in the packages found
StartDate Attribute Date includes the start date of the package
Durations A collection of search results for the package and the
start date
Duration List of elements Duration depending on the start date
and package
SettlerCode This is only relevant for bookings via DSI and will
represent the organization code of the guest settler.
The Settler Code is mandatory when putting an item to
the shopping cart. See chapter booking for more
details.
HeaderSectionPriceType Whether Fixed or Dynamic. Fixed price for package
means fixed price without dependency on the products
chosen. Dynamic price for package means depending
on the product chosen the price will differ.
MinChild Minimal amount of children
MinAdult Minimal amount of adults
MaxChild Maximal amount of children
MaxAdult Maximal amount of adults
DbCode This is relevant for package details search and booking
via DSI and will represent the code of the local
database where this package can be found. The
DbCode is mandatory when putting an item to the
shopping cart. See chapter booking for more details.

Response for the search example:

<?xml version="1.0" encoding="UTF-8"?>


<FeratelDsiRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" Status="0" Message="OK"
xmlns="http://interface.deskline.net/DSI/XSD">
<Result Index="1" TotalObjects="2">
<Package Id="1edff3bc-ece3-48ff-a452-54ebf454ae9c">
<Name>test package 3</Name>
<StartDates>
<StartDate Date="2011-02-18">
<Durations>
<Duration>3</Duration>
<Duration>4</Duration>
</Durations>
</StartDate>
<StartDate Date="2011-02-19">
<Durations>
<Duration>3</Duration>
<Duration>4</Duration>
</Durations>
</StartDate>
<StartDate Date="2011-02-20">
<Durations>
<Duration>3</Duration>
<Duration>4</Duration>
</Durations>
</StartDate>
<StartDate Date="2011-02-21">
<Durations>

Search For Destination Packages 146 of 241


DESKLINE 3.0 STANDARD INTERFACE

<Duration>3</Duration>
<Duration>4</Duration>
</Durations>
</StartDate>
</StartDates>
<SettlerCode>FERATEL</SettlerCode>
<HeaderSectionPriceType>Fixed</HeaderSectionPriceType>
<MinChild>1</MinChild>
<MinAdult>2</MinAdult>
<MaxChild>1</MaxChild>
<MaxAdult>2</MaxAdult>
<DbCode>FRT</DbCode>
</Package>
<Package Id="07303c2c-accd-44de-91d9-8e573d87e5f7">
<Name>testpackage 2</Name>
<StartDates>
<StartDate Date="2011-02-18">
<Durations>
<Duration>7</Duration>
</Durations>
</StartDate>
<StartDate Date="2011-02-19">
<Durations>
<Duration>7</Duration>
</Durations>
</StartDate>
<StartDate Date="2011-02-20">
<Durations>
<Duration>7</Duration>
</Durations>
</StartDate>
<StartDate Date="2011-02-21">
<Durations>
<Duration>7</Duration>
</Durations>
</StartDate>
</StartDates>
<SettlerCode>FERATEL</SettlerCode>
<HeaderSectionPriceType>Dynamic</HeaderSectionPriceType>
<MinChild>0</MinChild>
<MinAdult>2</MinAdult>
<MaxChild>2</MaxChild>
<MaxAdult>2</MaxAdult>
<DbCode>FRT</DbCode>
</Package>
</Result>
</FeratelDsiRS>

Response for the search example, nothing found:

<?xml version="1.0" encoding="UTF-8"?>


<FeratelDsiRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" Status="0" Message="OK"
xmlns="http://interface.deskline.net/DSI/XSD">
<Result Index="1" TotalObjects="0" />
</FeratelDsiRS>

Based on the IDs in the response it is possible to search for package details or to open a link to the Deskline 3.0
web application.

Search For Destination Packages 147 of 241


DESKLINE 3.0 STANDARD INTERFACE

SEARCH FOR DESTINATION PACKAGE DETAILS


The search function that the DSI uses is the same function as for the Deskline 3.0 Web application and the
Deskline 3.0 ExpertClient and therefore supports the same functionality.

The search for destination packages has two steps. The search result of the first search step will provide the
basic information of all packages which fits to the search criteria. With the information of the first search result
it is possible to get more details on one special package.

REQUEST
Request field Description Can be empty? Multiple?
Originator The code of the point of sale requesting the data.
Provided by feratel.
Company The code of the company requesting the data. Provided
by feratel.
Language The language that is expected of the response.
CurrencyCode If this element is not send the defined Currency for the
Point of Sale is taken (Originator). If a CurrencyCode
different to the point of sale currency is send all the
prices in the search result get converted automatically.
CurrencyCode is the 3-digits long international currency
code (e.g. EUR, CHF,…)
Range and GUIDs First, a range code to select the data must be defined.
IDs This is an enumeration if it is a region (RG) or a town (TO)
or a district (DI) for example. It is also possible to select
one or more data owners instead of a geographical
selection. The IDs of regions/towns/districts are part of
the KeyValues function. If there is a need to call data
owners (DO) directly, the IDs are provided by feratel. The
top location (i.e. highest/widest range possible) will be
provided by feratel to get started (see range example in
KeyValues.xml)
PackageDetailsSearch Contains the information of the package of which the
details will be requested.
DbCode Code of the database where the package can be found.
Returned with the search result of first package search.
PackageId Id of the package of which the details will be requested.
Returned with the search result of first package search.
DateFrom Start date of the package requested. Possible start dates
are returned with the search result of first package
search.
Duration Duration of the package requested. Possible durations
are returned with the search result of first package
search.
Adults Number of adults of the package requested. Possible
numbers are returned with the search result of first
package search (MinAdults and MaxAdults).
Children Children ages (comma separated), leave empty if no
children are needed.
Units Units required of the package requested.
Settler Name of the Settler of the package. Returned with the
search result of first package search (SettlerCode).
SalesChannelID The GUID of the SalesChannel for the package. Assigned
by feratel.
Search For Destination Package Details 148 of 241
DESKLINE 3.0 STANDARD INTERFACE

Example of a search:

<?xml version="1.0" encoding="utf-8"?>


<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://interface.deskline.net/DSI/XSD">
<Request Originator="FERATEL" Company="FERATEL" Language="en" CurrencyCode="EUR" >
<Range Code="RG">
<Item Id="F180FFD5-4FBF-4F2C-AC00-7E8B94462F2C" />
</Range>
<PackageDetailsSearch>
<DbCode>FRT</DbCode>
<PackageId>ed2ce907-9c96-4394-9887-de5a4010f0a6</PackageId>
<DateFrom>2011-03-11</DateFrom>
<Duration>3</Duration>
<Adults>3</Adults>
<Children>2,10</Children>
<Units>1</Units>
<Settler>FERATEL</Settler>
<SalesChannelID>BB556229-E7B1-4F21-9C6A-2BEA7120BF5A</SalesChannelID>
</PackageDetailsSearch>
</Request>
</FeratelDsiRQ>

RESPONSE
Request field Description Can be empty? Multiple?
Status Status="0" Message="OK" / Status="1"
Message="Error message"
Result Index is the same number from the SearchParameters
to relate the response with request. TotalObjects is the
amount of results in total, always 1.
PackageDetails Including Id of the requested package.
Sections A collection of sections related to the package
requested.
Section Attributes: Id of section, isArrivalDateOK can be true or
false, true means the arrival date is possible for this
section. Order is the section order defined for this
package, Type can be optional or mandatory depending
on that if section has to be booked or can be booked
optional. ProductType can be Accommodation or
AdditionalService depending on the type of products
assigned to this section. DateFrom, DateTo and
duration of the section (a section can last shorter than
package e.g. package duration 7 days and 4 days ski
ticket). Another attribute is section name.
AvailabilityCheck is true if availabilities will be checked
for the assigned products. MaxUnit is the maximal
amount of units which can be booked per package or
per person depending on attribute UnitType. ParentId
which shows the relation to a parent section, zero-
GUID if there is no relation
Categories A collection of categories related to the package
requested.

Search For Destination Package Details 149 of 241


DESKLINE 3.0 STANDARD INTERFACE

Category Attribute: Category Id, Name, PriceFrom, order and


MealCode (NO, AI, 34, BB, HB, FB).

Section List of sections related to the category with Id and


name, more details in the result in sections list (see
section above)
AssignmentItems List of assigned products to special section of special
category.
AssignmentItem Attributes: Item Id, OwnAvailability can be true or false
if true special availabilities for this package are entered
of it is false the product availabilities are taken.
Preselected can be true or false whether the item has
to be booked or not. TransactionDetailType is the type
of the product assigned, can be AccommodationHotel,
AccommodationAppartment, AccomodationCamping
and AdditionalService. ParentId and ParentName
include information about the service provider of the
product assigned to this section. ProductId and
ProductName of the product assigned to this section
and category (for more details concerning service
provider and product use basic data interface).
Availability of the product and ProviderTown is the
town where the service provider is located.
Price All prices concerning each assigned item
Adults Base Price for Adults for this specific assigned item
Children Multiple elements with name PriceChild possible
including Age of child and the price
Total AdditionalNight Total for all additional nights selected
Total Adult Total for number of adults selected
Total Children Total for number of children selected
Total Price Total price for this product in this section

Response for the search example:

<?xml version="1.0" encoding="UTF-8"?>


<FeratelDsiRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" Status="0"
Message="OK" xmlns="http://interface.deskline.net/DSI/XSD">
<Result Index="1" TotalObjects="1">
<PackageDetails Id="20ed3817-3185-4e13-af8f-47dfc4937148">
<Sections>
<Section Id="a4791628-edbe-4841-84fd-c6ab8e15d122" isArrivalDateOK="true" Order="1" Type="Mandatory"
ProductType="Accommodation" DateFrom="2011-05-11" DateTo="2011-05-13" Duration="3" Name="acco sec" AvailabilityCheck="true"
MaxUnit="1" UnitType="PerPackage" ParentId="00000000-0000-0000-0000-000000000000" />
<Section Id="c42bdc7c-a4e5-4389-95ef-eff3aefa9c4a" isArrivalDateOK="true" Order="2" Type="Mandatory"
ProductType="AdditionalService" DateFrom="2011-05-11" DateTo="2011-05-12" Duration="2" Name="additional service sec"
AvailabilityCheck="true" MaxUnit="0" UnitType="PerPerson" ParentId="00000000-0000-0000-0000-000000000000" />
</Sections>
<Categories>
<Category Id="deb61251-0e8e-4e63-8765-7d2664838353" Name="first" PriceFrom="290.00" Order="1" MealCode="BB">
<Section Id="a4791628-edbe-4841-84fd-c6ab8e15d122" Name="acco sec">
<AssignmentItems>
<AssignmentItem Id="966d500f-3a7c-4870-9bed-6d75672ba99e" OwnAvailability="false" Preselected="false"
TransactionDetailType="AccommodationHotel" ParentId="dc1defe3-999a-4097-a5bf-7bd86a14e28a" ParentName="Simotel"
ProductId="144edd77-3fef-4c20-b8f6-b19036df0fdd" ProductName="Appartement/Fewo" Availability="10" ProviderTown="Tux">
<Price>
<Adults Price="100.00" />
<Children>
<PriceChild Age="4" Price="40.00" />
<PriceChild Age="10" Price="60.00" />

Search For Destination Package Details 150 of 241


DESKLINE 3.0 STANDARD INTERFACE

</Children>
<Total AdditionalNight="0.00" Adult="200.00" Children="100.00" Price="300.00" />
</Price>
</AssignmentItem>
</AssignmentItems>
</Section>
<Section Id="c42bdc7c-a4e5-4389-95ef-eff3aefa9c4a" Name="additional service sec">
<AssignmentItems>
<AssignmentItem Id="40a5f074-a78e-4d7b-9b3b-f0efa6320302" OwnAvailability="false" Preselected="false"
TransactionDetailType="AdditionalService" ParentId="dc1defe3-999a-4097-a5bf-7bd86a14e28a" ParentName="Simotel"
ProductId="eaae1d14-2bf6-4cea-8e40-89cfb4e067b2" ProductName="Skiticket" Availability="99" ProviderTown="Tux">
<Price>
<Adults Price="30.00" />
<Children>
<PriceChild Age="4" Price="10.00" />
<PriceChild Age="10" Price="20.00" />
</Children>
<Total AdditionalNight="0.00" Adult="60.00" Children="30.00" Price="90.00" />
</Price>
</AssignmentItem>
</AssignmentItems>
</Section>
</Category>
<Category Id="0a16f4a3-cdba-49d1-89df-57bb6d0d9a23" Name="second" PriceFrom="290.00" Order="3" MealCode="BB">
<Section Id="a4791628-edbe-4841-84fd-c6ab8e15d122" Name="acco sec">
<AssignmentItems>
<AssignmentItem Id="c01b100f-3fcc-4f72-b97a-fcf6b5d050ed" OwnAvailability="false" Preselected="false"
TransactionDetailType="AccommodationHotel" ParentId="dc1defe3-999a-4097-a5bf-7bd86a14e28a" ParentName="Simotel"
ProductId="144edd77-3fef-4c20-b8f6-b19036df0fdd" ProductName="Appartement/Fewo" Availability="10" ProviderTown="Tux">
<Price>
<Adults Price="200.00" />
<Children>
<PriceChild Age="4" Price="80.00" />
<PriceChild Age="10" Price="120.00" />
</Children>
<Total AdditionalNight="0.00" Adult="400.00" Children="200.00" Price="600.00" />
</Price>
</AssignmentItem>
</AssignmentItems>
</Section>
<Section Id="c42bdc7c-a4e5-4389-95ef-eff3aefa9c4a" Name="additional service sec">
<AssignmentItems>
<AssignmentItem Id="0cd21909-80aa-4178-929a-3f0a2e2a6a60" OwnAvailability="false" Preselected="false"
TransactionDetailType="AdditionalService" ParentId="dc1defe3-999a-4097-a5bf-7bd86a14e28a" ParentName="Simotel"
ProductId="eaae1d14-2bf6-4cea-8e40-89cfb4e067b2" ProductName="Skiticket" Availability="99" ProviderTown="Tux">
<Price>
<Adults Price="30.00" />
<Children>
<PriceChild Age="4" Price="10.00" />
<PriceChild Age="10" Price="20.00" />
</Children>
<Total AdditionalNight="0.00" Adult="60.00" Children="30.00" Price="90.00" />
</Price>
</AssignmentItem>
</AssignmentItems>
</Section>
</Category>
</Categories>
<Currency>EUR</Currency>
</PackageDetails>
</Result>
</FeratelDsiRS>

Response for the search example, nothing found:

<?xml version="1.0" encoding="UTF-8"?>


<FeratelDsiRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" Status="1" Message="No results found for given request."
xmlns="http://interface.deskline.net/DSI/XSD" />

Search For Destination Package Details 151 of 241


DESKLINE 3.0 STANDARD INTERFACE

SEARCH FOR EVENTS


For better listing of events we provide additionally to the basic data request for events an event search. There
are two different profiles for event search which influence the information provided in the response.

The search result will list all events in the requested period sorted by day.

REQUEST
Request field Description Can be empty? Multiple?
Originator The code of the point of sale requesting the data.
Provided by feratel.
Company The code of the company requesting the data.
Provided by feratel.
Language The language that is expected of the response.
Note: If no language provided in request no
description given in expanded response.
Range and GUIDs First, a range code to select the data must be defined.
IDs This is an enumeration if it is a region (RG) or a town
(TO) or a district (DI) for example. It is also possible to
select one or more data owners instead of a
geographical selection. The IDs of
regions/towns/districts are part of the KeyValues
function. If there is a need to call data owners (DO)
directly, the IDs are provided by feratel. The top
location (i.e. highest/widest range possible) will be
provided by feratel to get started (see range example
in KeyValues.xml)
EventSearch Container Element for the event search.
From Start date for event search
To End date for event search
Name Optional possibility to search for specific event name
(string)
Location Optional possibility to search for specific event
location (string)
SerialEvent For search within one serial event, send ID of serial
event, provided by Key Value interface.
Profile Influence the amount of information provided in the
response. Possible values “Reduced” and “Expanded”
(Reduced per default)
IsTopEvent Optional attribute which is per default false, which
means that search result includes top events as well as
none top events. If set to true only top events are
included in response
HolidayThemes Used to query for holiday themes like “wedding”,
“sports”, and so on. Refer to the list of Key Values for
the GUIDs.
Facilities Information of required event facilities. All selected
facilities must match with the event. Refer to the list of
Key Values for the GUIDs.

Minimum example of an event search:

Search For Events 152 of 241


DESKLINE 3.0 STANDARD INTERFACE

<?xml version="1.0" encoding="utf-8"?>


<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://interface.deskline.net/DSI/XSD">
<Request Originator="FERATEL" Company="FERATEL" Language="en">
<Range Code="RG">
<Item Id="F180FFD5-4FBF-4F2C-AC00-7E8B94462F2C" />
</Range>
<EventSearch From="2011-10-15" To="2011-10-18" />
</Request>
</FeratelDsiRQ>

Example of an event search:


<?xml version="1.0" encoding="utf-8"?>
<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://interface.deskline.net/DSI/XSD">
<Request Originator="FERATEL" Company="FERATEL" Language="en">
<Range Code="RG">
<Item Id="F180FFD5-4FBF-4F2C-AC00-7E8B94462F2C" />
</Range>
<EventSearch From="2011-11-15" To="2011-11-18" Name="circus" Location="festival centre" SerialEvent="xxx"
Profile="Expanded" >
<HolidayThemes>
<Item Id="DC26D00A-1B99-4C7C-A09A-AFC16578C144" />
<Item Id="090A18AE-5D50-421E-A65A-C5A2B8227AE5" />
</HolidayThemes>
<Facilities>
<Item Id="e12259b0-1532-4c37-8f4c-fe21ce143956" />
</Facilities>
</EventSearch>
</Request>
</FeratelDsiRQ>

RESPONSE
Request field Description Can be empty? Multiple?
Status Status="0" Message="OK" / Status="1"
Message="Error message"
Result Index is the same number from the SearchParameters
to relate the response with request. TotalObjects is the
amount of results in total.
CalendarDates A collection of dates the events will take place.
Calendar Dates Container element for each calendar day.
Events Event List of events taking place within the specific calendar
date.
Event Id Id of the event.
Name Name of the event in the requested language.
Location Name of the location where the event takes place in
the requested language.
Town Name of the town, where the event takes place.
Duration Units (Hour, Minute, Day, None) and value for the
event, i.e. a circus for 2 hours. Zero if Units=”None”
Times Time List of times when the event takes place. Format
hh:mm. Element missing if no times entered for the
event.
Expanded Only part of search result if the requested profile was
set to expanded
Images List of images for the event

Search For Events 153 of 241


DESKLINE 3.0 STANDARD INTERFACE

Image Name, URL, Order and Id of the images will be provided


Description Description in the requested language which is valid on
the day of search

Response:

<?xml version="1.0" encoding="UTF-8"?>


<FeratelDsiRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" Status="0" Message="OK"
xmlns="http://interface.deskline.net/DSI/XSD">
<Result Index="1" TotalObjects="4">
<CalendarDates>
<Calendar Date="2011-11-15">
<Events>
<Event Id="80f19f42-e41a-4174-b08b-191e0d160106">
<Name>Special Event</Name>
<Location>Stadthalle, 1119 Wien, Opernring 25</Location>
<Town>Innsbruck</Town>
<Duration Units="Hours">2</Duration>
<Times>
<Time>12:00</Time>
<Time>13:00</Time>
</Times>
</Event>
<Event Id="baa39e75-8983-413c-86d3-28aad4f25358">
<Name>Villacher Kirchtag</Name>
<Location>Villach - Hauptplatz</Location>
<Town>Innsbruck</Town>
<Duration Units="Days">8</Duration>
<Times>
<Time>10:00</Time>
</Times>
<Expanded>
<Images>
<Image Name="Kirchtag"
URL="http://interfacetest.deskline.net/Handlers/Document?code=FRT&amp;id=6e32f0b4-e4f7-4913-91ca-0b961d85095a"
Order="1" Id="baa39e75-8983-413c-86d3-28aad4f25358" />
</Images>
<Description>Kirchtag Beschreibung</Description>
</Expanded>
</Event>
<Event Id="e0636eef-00c5-4d04-b372-3d7c0826ada3">
<Name>Kalender</Name>
<Location>Winterberg</Location>
<Town>Matrei am Brenner</Town>
<Duration Units="None">0</Duration>
</Event>
</Events>
</Calendar>
<Calendar>
<Events Date="2011-11-16">
<Event Id="b4bf28c9-89ca-4ba5-ae68-564853897b55">
<Name>Jazz Music Night</Name>
<Location>Hotel Flattacher Hof</Location>
<Town>Innsbruck</Town>
<Duration Units="Hours">3</Duration>
<Times>
<Time>18:00</Time>
</Times>
</Event>
</Events>
</Calendar>
</CalendarDates>
</Result>
</FeratelDsiRS>

Search For Events 154 of 241


DESKLINE 3.0 STANDARD INTERFACE

GUEST ADDRESS M ANIPULATION


It is possible to add new guest addresses for requests or bookings. The last name, country, salutation and e-
mail address of the guest are always mandatory. To avoid duplicates on customer databases it is also possible
to assign a password (transfer only the MD5 hash value) and update the address later when using either the ID
or the e-mail/password combination to authenticate.

A guest address will consist of the following information:

Field Name Description Mandatory?


Email E-Mail of the guest, format restricted to valid e-mails.

Password MD5 value of the password. This can be used if you want to offer
the guest the chance to log in again and make another booking or
see existing bookings. Also, making it mandatory is highly
recommended to avoid duplicates in the customer database. The
password will not be returned when selecting a guest address so
it’s only possible to set a password value, not read it.
Language Providing the guest languages is mandatory. The codes can be
read with the KeyValues function.
SalutationId Providing the salutation for the guest is mandatory. The codes can
be read with the KeyValues function Salutations. Only global
available Salutations can be used. So when requesting Salutations
do not use the GetLocalValues=”true” tag!
FirstName First name of the guest, please note that in case of a booking with
cancellation insurance a FirstName must be provided for
insurance company
LastName Last Name of the guest

Company Company Name

Address Street name incl. street number, please note that in case of a
booking with cancellation insurance the address must be
provided for insurance company
AltAddress Second line for address if necessary

ZipCode Postal code, please note that in case of a booking with


cancellation insurance the postal code must be provided for
insurance company
City City name, please note that in case of a booking with cancellation
insurance the city name must be provided for insurance company
Country Providing the country code for the guest is mandatory. The codes
can be read with the KeyValues function GuestCountries.
Mobile Mobile phone number, format restricted via regular expression.
Example: +431234567890
Phone Phone number, format restricted via regular expression. Example:
+434242216565
Fax Fax number, format restricted via regular expression. Example:
+43424221656565
Reusable Does the guest want to receive the newsletter of the destination /
Does the guest allow that his contact data is used for marketing

Guest Address Manipulation 155 of 241


DESKLINE 3.0 STANDARD INTERFACE

purposes by the destination? Default=false.


CurrencyCode Guest Currency. If not set via insert request. Default currency of
point of sale is set as currency for this guest
Rating Does the guest allow that his contact data is used for rating
purposes by the destination? Default=false.

Guest Address Manipulation 156 of 241


DESKLINE 3.0 STANDARD INTERFACE

C REATING A NEW GUEST ADDRESS


A guest address is only stored to the local database of the customer when a transaction (i.e. booking or
request) is committed with the address.

Request:

<?xml version="1.0"?>
<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://interface.deskline.net/DSI/XSD">
<Request Company="1234" Originator="FERATEL">

<GuestInsert Email="[email protected]"
Password="89f288757f4abc93c99b007855fc075e" SalutationId="5640FBFD-8103-4B68-B04A-469A4B57863E"
Company="frtpfw" FirstName="Thomas" LastName="Pasterk" Phone="+434242216565" Fax="+43424221656565"
Mobile ="+43123456789" Country="AT" Address="Moritschstraße 2/IV" ZipCode="9500" City="Villach"
Language="en" Reusable="false" CurrencyCode="EUR" Rating="false" />

</Request>
</FeratelDsiRQ>

Response:

<?xml version="1.0"?>
<FeratelDsiRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" Status="0" Message="OK"
xmlns="http://interface.deskline.net/DSI/XSD">

<Result Index="1">
<Guest Id="7db25c74-55e3-4f40-9ffc-18c8ef2d2a41" Email="[email protected]"
SalutationId="5640FBFD-8103-4B68-B04A-469A4B57863E" Title="Mr" Salutation="Dear Mr Pasterk"
Company="frtpfw" FirstName="Thomas" LastName="Pasterk" Phone="+434242216565" Mobile="" Fax=""
Address="" AltAddress="" Country="AT" ZipCode="9500" City="Villach" Language="en" Reusable="false"
CurrencyCode="EUR" Rating="false" />
</Result>

</FeratelDsiRS>

SEARCHING A GUEST ADDRESS


A guest address is returned either by providing the GUID of the guest or the e-mail/password combination. If
only the GUID of the guest is provided we expect the external system to take care of user authentication in
order to display the correct data to the user.

Request by ID:

<?xml version="1.0"?>
<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://interface.deskline.net/DSI/XSD">
<Request Company="1234" Originator="FERATEL">
<Guest Id="7db25c74-55e3-4f40-9ffc-18c8ef2d2a41" />
</Request>
</FeratelDsiRQ>

Request by mail/password:

<?xml version="1.0"?>
<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://interface.deskline.net/DSI/XSD">

Guest Address Manipulation 157 of 241


DESKLINE 3.0 STANDARD INTERFACE

<Request Company="1234" Originator="FERATEL">


<Guest Email="[email protected]" Password=" 89f288757f4d0693c9abc07855fc075e" />

</Request>
</FeratelDsiRQ>

Response:

<?xml version="1.0"?>
<FeratelDsiRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" Status="0" Message="OK"
xmlns="http://interface.deskline.net/DSI/XSD">

<Result Index="1">
<Guest Id="7db25c74-55e3-4f40-9ffc-18c8ef2d2a41" Email="[email protected]"
SalutationId="5640FBFD-8103-4B68-B04A-469A4B57863E" Title="Mr" Salutation="Dear Mr Pasterk"
Company="frtpfw" FirstName="Thomas" LastName="Pasterk" Phone="+434242216565" Mobile="" Fax=""
Address="" AltAddress="" Country="AT" ZipCode="9500" City="Villach" Language="en" Reusable="false"
CurrencyCode="EUR" Rating="false" />
</Result>

</FeratelDsiRS>

UPDATING A GUEST ADDRESS


Either all attributes are provided and the address is overwritten or only changed attributes are provided in the
request. Updating requires the GUID of the guest that is returned when searching for a guest address.

Request:

<?xml version="1.0"?>
<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://interface.deskline.net/DSI/XSD">

<Request Company="1234" Originator="FERATEL">

<GuestUpdate Id="7db25c74-55e3-4f40-9ffc-18c8ef2d2a41" ZipCode="9020"


City="Klagenfurt" />

</Request>
</FeratelDsiRQ>

Response:

<?xml version="1.0"?>
<FeratelDsiRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" Status="0" Message="OK"
xmlns="http://interface.deskline.net/DSI/XSD">

<Result Index="1">
<Guest Id="7db25c74-55e3-4f40-9ffc-18c8ef2d2a41" Email="[email protected]"
SalutationId="5640fbfd-8103-4b68-b04a-469a4b57863e" Title="Mr" Salutation="Dear Mr Pasterk" Company=""
FirstName="" LastName="Pasterk" Phone="+431234" Mobile="+43123456789" Fax="" Address="" AltAddress=""
Country="AT" ZipCode="9020" City="Klagenfurt" Language="en" Reusable="false" CurrencyCode="EUR"
Rating="false" />
</Result>

</FeratelDsiRS>

Guest Address Manipulation 158 of 241


DESKLINE 3.0 STANDARD INTERFACE

DELETING A G UEST A DDRESS


Deleting a guest address is possible as long as there is no transaction stored for this user.

Request:

<?xml version="1.0"?>
<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://interface.deskline.net/DSI/XSD">

<Request Company="1234" Originator="FERATEL">


<GuestDelete Id="31b850d9-11a4-47c6-a39f-44fa24ebef38" />
</Request>

</FeratelDsiRQ>

Response:

<FeratelDsiRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" Status="0" Message="OK"
xmlns="http://interface.deskline.net/DSI/XSD">
<Result Index="1" />
</FeratelDsiRS>

Guest Address Manipulation 159 of 241


DESKLINE 3.0 STANDARD INTERFACE

BOOKING PROCESS
Booking items in Deskline 3.0 is possible either in the back-office client of the tourism organisation, with the
use of the Deskline 3.0 web links or with this interface. There are two ways of bookings: regular bookings
where the booking is binding and there are “on request” bookings. This means, that for a time of x-hours
(specified by the tourism organisation) the service provider has to confirm the booking as well, otherwise it is
automatically invalid. For every booking we automatically send a confirmation to the service provider and to
the guest. If the confirmation to the guest and /or the service provider is not wanted let us know and we can
deactivate it per company.

IMPORTANT INFORMATION
There are a few restrictions for the booking process that usually won’t affect most of the customers directly but
rather databases where several different organisations are working together or projects where data from
several databases are used for one POS. These restrictions are:

 A booking can only be saved with items from one database code. Creating a booking with items from
more than one database will not work.
 A booking can only be saved with items from one guest settler organisation. Creating a booking with
items from more than one guest settlers will not work.
 If a destination works with “Booking on Request” then it is only possible to book one “on request”
service provider (note, this was “item” until 1.0.23) at a time. When trying to add items of another
service provider or of another type, the system will respond accordingly.

Another restriction is a general configuration setting that defines the payment methods used. These settings
will be configured for the guest settler.

What is a guest settler? Imagine two different databases: In one database there is only one customer and only
this organisation. This organisation is at the same time the data owner, maybe the point of sale but also the
guest settler. The restriction will not affect this customer. Now on the other hand there can be a database with
several organisations that all work differently and each one could be a guest settler. But there could be a point
of sale that is allowed to book all items from all organisations. Still, in this case, it is not possible to create one
booking with items from more than one settler. The SettlerCode is part of the search result and must be used
when adding items to the shopping cart.

Credit Cards: We are not allowed to store credit card numbers in our system; therefore we use a payment
provider when booking with the Deskline links. If you want to secure a booking with requesting or charging a
credit card you have to implement a form on your website that directly posts this data to the payment
provider. This payment provider then returns the reference number and a status (OK/not OK) which we use to
commit the booking and return a status. It is possible to use parts of the Deskline resources for this step in
order to have the status saved in the database as well, details for this see chapter “Credit Card Guarantee or
Payment with Datatrans”.

Booking Process 160 of 241


DESKLINE 3.0 STANDARD INTERFACE

PAYMENT TYPES AND PAYMENT METHODS


Each settler can support multiple payment types and payment methods. There are three different payment
types

 ServiceProviderPayment (amount has to be paid directly to the service provider)


 SplitPayment (deposit has to be paid to the organization and final payment to the service provider)
 OrganisationPayment (amount has to be paid to the organization)

There is always a combination of payment type and payment method. Payment methods are

 NoPayment (means no payment to the settler organization only possible in combination with Service
Provider Payment)
 Invoice (the guest will get an invoice via mail, each settler can define how much days until arrival has
to be that invoice can be used, else payment method automatically switches to credit card, if possible)
 CreditCard (only prepayment can be done with credit card, if credit card payment is required it is not
possible to commit the shopping card, payment to Datatrans has to be done)
 ELV (only prepayment can be done with ELV, if ELV payment is required it is not possible to commit
the shopping card, payment to Datatrans has to be done)
 Sofortueberweisung (only prepayment can be done with Sofortueberweisung, if Sofortueberweisung
payment is required it is not possible to commit the shopping card, payment to Datatrans has to be
done)
 iDeal (only prepayment can be done with iDeal, if iDeal payment is required it is not possible to
commit the shopping card, payment to Datatrans has to be done)

To find out which settler supports which payment types and payment methods use the
GetOrganisationInformation Request compared with the Parameter GetPaymentInformation =”true” and the
SalesChannelId.

The payment conditions can also be individually influenced by settings on service provider level. In this case
PaymentType and PaymentMethod are automatically changed on our side. This influences values in
PaymentType on item level as well as TransactionPrePaymentMethod, TransactionFinalPaymentMethod and
NoPayment in shopping cart. Always refer to the values provides by us in the shopping cart.

Important: When you add multiple items to a Shopping Cart you always have to provide PaymentType and
PaymentMethod. If you once create the shopping cart with specific settings they are not fixed when adding
another item. So if you want the whole shopping cart to be SplitPayment and Invoice, provide this Information
for each item.

MANDATORY S HOPPING CART PARAMETERS


Field Name Description
DbCode Code of the database where the booking will be saved.
Returned with the search result.
GuestSettlerCode Code of the organisation that deals with the guest
settlement. Returned with the search result.

Booking Process 161 of 241


DESKLINE 3.0 STANDARD INTERFACE

C REATING A NEW SHOPPING C ART


A shopping cart can consist of various accommodation, additional service, shop and package items and is used
to collect these items in order to convert them into one booking. By creating a new shopping cart, you will get a
temporary ID that you can use to add items. For every item inside the shopping cart there is a shopping cart
item ID. After the guest is finished adding items, a booking can be committed (or credit card payment has to be
done). A shopping cart is only valid for 2 hours. This restriction is necessary to avoid bookings with expired
prices or availabilities.

Important: When you are going to use the Booking Interface, you also have to send us the clicks back in our
system so we can make correct analytics. For clicks on basic data you have to use the Deskline 3.0 ClickCount
Interface. For OfferRequests, Putting one ServiceProvider in ShoppingCar or Booking of a ServiceProvider there
is no need to send us the clicks. We count the clicks on our side when we get the request for these actions from
you.

So that we have the possibility to calculate correct shopping cart conversion we need from your System the
SessionID of the guest. You have to send us this when you create the shoppingcart or offerrequest.

Important: For different items it is necessary to call the adding to shopping cart one at a time, one and the
same product can be added multiple by providing Unit attribute with according count.

Important: It is possible to send a guest currency. Shopping Cart prices are always shown in the settler
currency!!! But if a guest currency is provided a currency factor is included in the shopping cart, so it is possible
to display the prices to the guest in her/his requested currency. If no Currency Code is send the default
currency of the sales point is taken. So if the Sales Point has default currency EUR and creates a shopping cart
for a settler with currency CHF, the shopping cart prices are in CHF and a currency factor to convert to EUR is
provided (by DIVISION). If the guest currency is different to the settler currency provide this information in
each request (create new shopping cart, add items,…)!!!

With first request it is needed to create a shopping cart by adding one item. A shopping cart can be created by
adding an accommodation, additional service, shop or package item.

Request
More
Request field Description Can be empty?* than one
possible?

Originator The code of the point of sale requesting the data. Provided by
feratel.
Company The code of the company requesting the data. Provided by
feratel.
CurrencyCode If this element is not send the defined Currency for the Point
of Sale is taken (Originator). If a CurrencyCode different to the
settler currency is send all the prices stay in the settler
currency and the currency factor for the requested guest
currency is provided in the shopping cart. CurrencyCode is the
3-digits long international currency code (e.g. EUR, CHF,…)
CreateShoppingCart Tag used to create a new shopping cart.
DbCode Code of the database where the booking will be saved.
Returned with the search result.
SalesChannelId The same Sales Channel ID that is used when performing a
search.
SessionID For the click count on our side we need the session id of the
guest from your system, in this way we can calculate the
conversion in a correct way.

Booking Process 162 of 241


DESKLINE 3.0 STANDARD INTERFACE

List of possible subelements to create a shopping cart, details of their structure in following chapters about
adding of the different kinds of items.
CartItemAccommodation Element for adding accommodation items.
CartItemAdditionalService Element for adding additional services.
CartItemBrochure Element for adding brochures.
CartItemShopArticle Element for adding shop articles.
CartItemPackage Element for adding destination packages.

<?xml version="1.0"?>
<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://interface.deskline.net/DSI/XSD">
<Request Company="FERATEL" Originator="FERATEL" Language="en" CurrencyCode="EUR" >
<CreateShoppingCart DbCode="FRT" SalesChannelId="BB556229-E7B1-4F21-9C6A-2BEA7120BF5A" SessionID="gf436t543tgerg"
>
<CartItemAccommodation ItemId="7f5a4750-0043-4953-8379-16cb4dfa1fb0" From="2010-05-20" To="2010-05-25"
Adults="2" MealCode="FB" ChildrenAges="" GuestSettlerCode="FERATEL" PaymentType="ServiceProviderPayment"
PaymentMethod="NoPayment" />
</CreateShoppingCart>
</Request>
</FeratelDsiRQ>

Response:

On success: see chapter Reading A Shopping Cart.

A DDING ACCOMMODATION I TEMS TO A SHOPPING CART


If a cart already exists it is possible to put more items into the cart. For every item inside the shopping cart
there is a shopping cart item ID.

If more products than available are put into cart the message "Availability is not enough." is responded.

Request

More than one


Request field Description Can be empty?*
possible?

Originator The code of the point of sale requesting the data.


Provided by feratel.
Company The code of the company requesting the data. Provided
by feratel.
CurrencyCode If this element is not send the defined Currency for the
Point of Sale is taken (Originator). If a CurrencyCode
different to the settler currency is send all the prices stay
in the settler currency and the currency factor for the
requested guest currency is provided in the shopping
cart. CurrencyCode is the 3-digits long international
currency code (e.g. EUR, CHF,…)
AddToShoppingCart Tag used to add items to an existing shopping cart.
Id ID of the existing shopping cart.
SalesChannelId The same Sales Channel ID that is used when performing
a search.
CartItemAccommodation Element for adding accommodation items.
ItemId GUID of the product from the Search Result.

Booking Process 163 of 241


DESKLINE 3.0 STANDARD INTERFACE

From Date of Arrival from Search


To Date of Departure from Search
Adults Number of Adults from Search
MealCode Meal Code from Search/Search Result
ChildrenAges Children ages from the search parameters, leave empty if
no children are needed. Provide a maximum of 20
characters.
GuestSettlerCode Code of the organisation that deals with the guest
settlement. Returned with the search result.
PaymentType Enumeration: ServiceProviderPayment, SplitPayment,
OrganisationPayment. Each item in the shopping cart can
have different payment type. Default value is
ServiceProviderPayment
PaymentMethod Enumeration: NoPayment, Invoice, CreditCard, ELV,
Sofortueberweisung, iDeal. Each shopping cart can have
only one payment method. When adding items with
different payment method, the shopping cart switches to
the required method which was provided at least. Default
value is NoPayment.
NumberOfItems Optional attribute with default value 1. Makes it possible
to add multiple items of the same product at once in
shopping cart

<?xml version="1.0" encoding="utf-8"?>


<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://interface.deskline.net/DSI/XSD">
<Request Company="FERATEL" Originator="FERATEL" Language="en" CurrencyCode="EUR">
<AddToShoppingCart Id="b61985ae-1700-48e1-914b-7363bae7ab18" DbCode="FRT"
SalesChannelId="BB556229-E7B1-4F21-9C6A-2BEA7120BF5A">
<CartItemAccommodation ItemId="48d3133b-2f09-4793-9bf5-915ef7383e14" From="2011-09-04"
To="2011-09-11" Adults="2" MealCode="HB" ChildrenAges="" GuestSettlerCode="FERATEL"
PaymentType="ServiceProviderPayment" PaymentMethod="NoPayment" NumberOfItems="2"/>
</AddToShoppingCart>
</Request>
</FeratelDsiRQ>

Response:

On success: see chapter Reading A Shopping Cart.

A DDING ADDITIONAL SERVICES TO A SHOPPING CART


If a cart already exists it is possible to put more items into the cart. For every item inside the shopping cart
there is a shopping cart item ID.

Request
More than
Request field Description Can be empty?* one
possible?

Originator The code of the point of sale requesting the data. Provided
by feratel.
Company The code of the company requesting the data. Provided by

Booking Process 164 of 241


DESKLINE 3.0 STANDARD INTERFACE

feratel.
CurrencyCode If this element is not send the defined Currency for the
Point of Sale is taken (Originator). If a CurrencyCode
different to the settler currency is send all the prices stay
in the settler currency and the currency factor for the
requested guest currency is provided in the shopping cart.
CurrencyCode is the 3-digits long international currency
code (e.g. EUR, CHF,…)
AddToShoppingCart Tag used to add items to an existing shopping cart.
Id ID of the existing shopping cart.
SalesChannelId The same Sales Channel ID that is used when performing a
search.
CartItemAdditionalService Element for adding additional services.
ItemId GUID of the product from the Search Result.
From Date of start from search
StartTime Time of start from search
NumberOfItems Number of items to put into shopping cart
DurationType Enumeration None/Day/Minute/Hour
DurationValue Duration value (i.e. 0 or 3 hours)
GuestSettlerCode Code of the organisation that deals with the guest
settlement. Returned with the search result.
PaymentType Enumeration: ServiceProviderPayment, SplitPayment,
OrganisationPayment. Each item in the shopping cart can
have different payment type. Default value is
ServiceProviderPayment
PaymentMethod Enumeration: NoPayment, Invoice, CreditCard, ELV,
Sofortueberweisung, iDeal. Each shopping cart can have
only one payment method. When adding items with
different payment method, the shopping cart switches to
the required method which was provided at least. Default
value is NoPayment.

<?xml version="1.0" encoding="utf-8"?>


<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://interface.deskline.net/DSI/XSD">
<Request Company="FERATEL" Originator="FERATEL" Language="en" CurrencyCode="EUR" >
<AddToShoppingCart Id="b61985ae-1700-48e1-914b-7363bae7ab18" DbCode="FRT"
SalesChannelId="BB556229-E7B1-4F21-9C6A-2BEA7120BF5A">
<CartItemAdditionalService ItemId="c8f24b60-d2c2-485d-b6ac-8bdbf5a8fddc" From="2010-10-
30" StartTime="12:00:00" NumberOfItems="1" DurationType="Hour" DurationValue="2" GuestSettlerCode="FERATEL"
PaymentType="ServiceProviderPayment" PaymentMethod="NoPayment" />
</ AddToShoppingCart>
</Request>
</FeratelDsiRQ>

Response:

On success: see chapter Reading A Shopping Cart.

Booking Process 165 of 241


DESKLINE 3.0 STANDARD INTERFACE

A DDING BROCHURES TO A SHOPPING CART


If a cart already exists it is possible to put more items into the cart. For every item inside the shopping cart
there is a shopping cart item ID.

Request
More than
Request field Description Can be empty?* one
possible?

Originator The code of the point of sale requesting the data. Provided
by feratel.
Company The code of the company requesting the data. Provided by
feratel.
CurrencyCode If this element is not send the defined Currency for the
Point of Sale is taken (Originator). If a CurrencyCode
different to the settler currency is send all the prices stay in
the settler currency and the currency factor for the
requested guest currency is provided in the shopping cart.
CurrencyCode is the 3-digits long international currency
code (e.g. EUR, CHF,…)
AddToShoppingCart Tag used to add items to an existing shopping cart.
Id ID of the existing shopping cart.
SalesChannelId The same Sales Channel ID that is used when performing a
search.
CartItemBrochure Element for adding brochures.
VariationID GUID of the brochure variation from the basic data.
GuestSettlerCode Code of the organisation that deals with the guest
settlement. Returned with the basic data.

<?xml version="1.0"?>
<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://interface.deskline.net/DSI/XSD">
<Request Company="FERATEL" Originator="FERATEL" Language="en" CurrencyCode="EUR" >
<AddToShoppingCart Id="2e03156c-ceb3-47b5-a199-1c1a3311f206" SalesChannelId="59994450-0280-4CC1-
B097-5C1D7EB09FAE">
<CartItemBrochure VariationId="7AA3D49B-BF8C-40E1-A862-EEA71C8927E2"
GuestSettlerCode="FERATEL" />
</AddToShoppingCart >
</Request>
</FeratelDsiRQ>

Response:

On success: see chapter Reading A Shopping Cart.

A DDING SHOP ARTICLES TO A SHOPPING CART


If a cart already exists it is possible to put more items into the cart. For every item inside the shopping cart
there is a shopping cart item ID.

Request
More than
Request field Description Can be empty?* one
possible?

Booking Process 166 of 241


DESKLINE 3.0 STANDARD INTERFACE

Originator The code of the point of sale requesting the data. Provided
by feratel.
Company The code of the company requesting the data. Provided by
feratel.
CurrencyCode If this element is not send the defined Currency for the
Point of Sale is taken (Originator). If a CurrencyCode
different to the settler currency is send all the prices stay in
the settler currency and the currency factor for the
requested guest currency is provided in the shopping cart.
CurrencyCode is the 3-digits long international currency
code (e.g. EUR, CHF,…)
AddToShoppingCart Tag used to add items to an existing shopping cart.
Id ID of the existing shopping cart.
SalesChannelId The same Sales Channel ID that is used when performing a
search.
CartItemShopArticle Element for adding shop articles.
VariationID GUID of the shop article variation from the basic data.
GuestSettlerCode Code of the organisation that deals with the guest
settlement. Returned with the basic data.

<?xml version="1.0"?>
<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://interface.deskline.net/DSI/XSD">
<Request Company="FERATEL" Originator="FERATEL" Language="en" CurrencyCode="EUR" >
<AddToShoppingCart Id="2e03156c-ceb3-47b5-a199-1c1a3311f206" SalesChannelId="59994450-0280-4CC1-
B097-5C1D7EB09FAE">
<CartItemShopArticle VariationId="7AA3D49B-BF8C-40E1-A862-EEA71C8927E2"
GuestSettlerCode="FERATEL" />
</AddToShoppingCart >
</Request>
</FeratelDsiRQ>

Response:

On success: see chapter Reading A Shopping Cart.

A DDING DESTINATION PACKAGES TO A SHOPPING CART


If a cart already exists it is possible to put more items into the cart. For every item inside the shopping cart
there is a shopping cart item ID.

Request:
More than
Request field Description Can be empty?* one
possible?

Originator The code of the point of sale requesting the data. Provided
by feratel.
Company The code of the company requesting the data. Provided by
feratel.
CurrencyCode If this element is not send the defined Currency for the
Point of Sale is taken (Originator). If a CurrencyCode
different to the settler currency is send all the prices stay in
the settler currency and the currency factor for the
requested guest currency is provided in the shopping cart.

Booking Process 167 of 241


DESKLINE 3.0 STANDARD INTERFACE

CurrencyCode is the 3-digits long international currency


code (e.g. EUR, CHF,…)
AddToShoppingCart Tag used to add items to an existing shopping cart.
Id ID of the existing shopping cart.
SalesChannelId The same Sales Channel ID that is used when performing a
search.
CartItemPackage Element for adding destination packages.
PackageHeaderId GUID of the package
CategoryId Id of the category the guest has chosen. Important: The
following sections and products have to be of the according
category
StartDate Date of arrival
DurationValue Duration of package in days (NOT in nights)
NumberOfItems Number of package items which shall be booked
Adults Number of Adults
Children Children ages comma separate no spaces, if no children
send empty attribute, but always send attribute it is
required
GuestSettlerCode Code of the organisation that deals with the guest
settlement. Returned with the search.
PaymentType OrganisationPayment. Packages always has to be booked
with payment type organization payment
PaymentMethod Organisationpayment is only allowed in combination with
payment method Invoice, CreditCard, Sofortueberweisung,
iDeal or ELV (NO NoPayment), see Organisation Information
to get possible payment methods.
Section Container-Element for all sections within the package which
should be added to shopping cart
SectionId Id of the section within the package
ProductId Id of the selected product inside the section. Must be a
product assigned to the category and section.
Adults Number of Adults for which this section shall be booked
Children Children ages comma separate no spaces, if no children
send empty attribute, but always send attribute it is
required
NumberOfItems Number of units of this section which shall be booked. Must
not exceed MaxUnits of the section.
Note: If MaxUnits of the section is zero there is no
restriction. Also depends on the section’s UnitType which is
PerPerson or PerPackage

<?xml version="1.0" encoding="utf-8"?>


<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://interface.deskline.net/DSI/XSD">
<Request Company="FERATEL" Originator="FERATEL" Language="en">
<CreateShoppingCart DbCode="FRT"
SalesChannelId="59994450-0280-4cc1-b097-5c1d7eb09fae">
<CartItemPackage
PackageHeaderId="76e7548b-4b42-429d-a1ac-b5d1654d9a58"
CategoryId="e348e9ba-1ae4-41ad-b412-d7a180f59382" StartDate="2012-11-23"
DurationValue="8" NumberOfItems="1" Adults="2" Children=""
GuestSettlerCode="FERATEL" PaymentType="OrganisationPayment" PaymentMethod="Invoice">

Booking Process 168 of 241


DESKLINE 3.0 STANDARD INTERFACE

<Section SectionId="7c7698b6-9c17-4ac2-ac4b-df49092fcef8"
ProductId="3b7af9a2-d931-4749-bfaf-61ec24fa7e0e" Adults="2" Children="" NumberOfItems="2" />
<Section SectionId="8a254ccb-d162-42ba-8a6c-2e162cc7f91b"
ProductId="0ab90439-4c4c-4880-8f6b-f67fbd3a735e" Adults="2" Children="" NumberOfItems="1" />
<Section SectionId="8048574d-545d-4651-b831-f8b56e473c2b"
ProductId="41ea520f-518b-48a8-b2bd-3644f9824958" Adults="2" Children="" NumberOfItems="2" />
</CartItemPackage>
</CreateShoppingCart>
</Request>
</FeratelDsiRQ>

Response:

On success: see chapter Reading A Shopping Cart.

REMOVING SHOPPING CART ITEMS


It is also possible to remove an item from the shopping cart if you have the shopping cart item ID.

Request
More than
Can be
Request field Description empty?*
one
possible?

Originator The code of the point of sale requesting the data. Provided by
feratel.
Company The code of the company requesting the data. Provided by
feratel.
CurrencyCode If this element is not send the defined Currency for the Point of
Sale is taken (Originator). If a CurrencyCode different to the
settler currency is send all the prices stay in the settler
currency and the currency factor for the requested guest
currency is provided in the shopping cart. CurrencyCode is the
3-digits long international currency code (e.g. EUR, CHF,…)
DeleteFromShoppingCart Tag used to delete items from an existing shopping cart.
Id ID of the existing shopping cart.
SalesChannelId The same Sales Channel ID that is used when performing a
search.
DeleteFromShoppingCart Element for removing shopping cart items.
ShoppingCartItemId GUID of the item inside the shopping cart, not the product
GUID.

<?xml version="1.0" encoding="utf-8"?>


<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://interface.deskline.net/DSI/XSD">
<Request Company="FERATEL" Originator="FERATEL" Language="en">
<DeleteFromShoppingCart Id="a45988b8-f874-494c-9dcc-7f48f8a06b6c" SalesChannelId="BB556229-E7B1-4F21-9C6A-
2BEA7120BF5A">
<CartItem ShoppingCartItemId="8d388585-33a9-4f24-8451-0ab25816c83c" />
</DeleteFromShoppingCart>
</Request>
</FeratelDsiRQ>

Booking Process 169 of 241


DESKLINE 3.0 STANDARD INTERFACE

Important:

If the shopping cart is empty (when the last item was removed) a new shopping cart has to be created
the next time an item is added. Otherwise the settler-check or transaction-type check can prevent a
booking.

Response:

On success: see chapter Reading A Shopping Cart.

C ALCULATE OPTIONAL FEES FOR SHOPPING C ART


It is possible to precalculate the optional fees for a specific shopping cart.

Request
More
Can be
Request field Description empty?*
than one
possible?

Originator The code of the point of sale requesting the data.


Provided by feratel.
Company The code of the company requesting the data.
Provided by feratel.
CurrencyCode If this element is not send the defined Currency for
the Point of Sale is taken (Originator). If a
CurrencyCode different to the settler currency is
send all the prices stay in the settler currency and
the currency factor for the requested guest
currency is provided in the shopping cart.
CurrencyCode is the 3-digits long international
currency code (e.g. EUR, CHF,…)
CalculateOptionalFeesForShoppingCart Tag used to calculate the optional fees of an
existing shopping cart.
Id ID of the existing shopping cart.

<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://interface.deskline.net/DSI/XSD">
<Request Company="xxx" Originator="FERATEL" Language="en">
<CalculateOptionalFeesForShoppingCart Id="a98f83d9-f87e-41e0-b730-c52beb23a7fd" />
</Request>
</FeratelDsiRQ>

Response
More than
Can be
Response field Description empty?*
one
possible?

CalculatedOptionalFees Element which includes all calculated fees


CurrencyCode 3-digit international currency code (always settler
currency)
CancellationInsurance Price of the cancellation insurance
BookingFee Price of the booking fee

Booking Process 170 of 241


DESKLINE 3.0 STANDARD INTERFACE

Example

<?xml version="1.0" encoding="UTF-8"?>


<FeratelDsiRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" Status="0" Message="OK"
xmlns="http://interface.deskline.net/DSI/XSD">
<Result Index="1">
<CalculatedOptionalFees CurrencyCode="EUR" CancellationInsurance="11.16" BookingFee="10" />
</Result>
</FeratelDsiRS>

UPDATE SHOPPING CART SETTINGS


It is possible to update the shopping cart with various settings/fields.

Request
More
Can be
Request field Description empty?*
than one
possible?

Originator The code of the point of sale requesting the data. Provided
by feratel.
Company The code of the company requesting the data. Provided by
feratel.
CurrencyCode If this element is not send the defined Currency for the
Point of Sale is taken (Originator). If a CurrencyCode
different to the settler currency is send all the prices stay in
the settler currency and the currency factor for the
requested guest currency is provided in the shopping cart.
CurrencyCode is the 3-digits long international currency
code (e.g. EUR, CHF,…)
UpdateShoppingCartSettings Tag used to update settings of an existing shopping cart.
Id ID of the existing shopping cart.
WishNotes Text field that can be entered by the guest and will be
visible to the point of sale and service provider and printed
on the booking confirmation
Notes Internal Comment for the reservation settler.
AccompaniedBy Text field about other travelers or all arriving guests for a
booking. If there are multiple please separate with
semicolon. If birthday is provided please use format (YYYY-
MM-DD). Example:
<AccompaniedBy>John Doe (1975-03-14); Mickey Mouse
(2011-01-04)</AccompaniedBy>
CancellationInsuranceChecked True/false. Option for the guest if the guest wants to book
the Cancellation Insurance if it is offered. When a
cancellation insurance is wanted first name, last name and
birth date has to be given for each arriving guest, unless
committement of shopping cart is not possible. The
insurance amount always requires whether a prepayment
to the organisatio or at least a credit card guarantee to
collect the money via CC for European Travel Incurance.
UseBookingFee True/false. Not an option for the guest but an option to
decide for the POS!

Booking Process 171 of 241


DESKLINE 3.0 STANDARD INTERFACE

<?xml version="1.0" encoding="utf-8"?>


<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://interface.deskline.net/DSI/XSD">
<Request Company="FERATEL" Originator="FERATEL" Language="en" CurrencyCode="EUR" >
<UpdateShoppingCartSettings Id="470D87D8-AA0E-446D-8B01-5DB03A352E63">
<WishNotes>We will bring a dog. A friendly one.</WishNotes>
<Notes>FRT3942346</Notes>
<AccompaniedBy>John Doe (1975-03-14); Mickey Mouse (2011-01-
04)</AccompaniedBy>
<CancellationInsuranceChecked>false</CancellationInsuranceChecked>
<UseBookingFee>false</UseBookingFee>
</UpdateShoppingCartSettings>
</Request>
</FeratelDsiRQ>

Response:

On success: see chapter Reading A Shopping Cart.

UPDATE SHOPPING CART PAYMENT METHOD


If there is a payment to the organization required shopping cart can be created with PaymentMethod Invoice
or Creditcard. If both payment methods are possible (depends on the setting of the settler oragnisation) you
can give the guest the possibility to choose and change the payment method of an existing shopping cart.

Request

More
Can be than one
Request field Description empty?* possible
?

Originator The code of the point of sale requesting the data.


Provided by feratel.
Company The code of the company requesting the data.
Provided by feratel.
CurrencyCode If this element is not send the defined Currency for
the Point of Sale is taken (Originator). If a
CurrencyCode different to the settler currency is send
all the prices stay in the settler currency and the
currency factor for the requested guest currency is
provided in the shopping cart. CurrencyCode is the 3-
digits long international currency code (e.g. EUR,
CHF,…)
UpdateShoppingCartPaymentMetho Tag used to update payment method of an existing
d shopping cart.
Id ID of the existing shopping cart.
PaymentMethod Possible values: NoPayment, Invoice, CreditCard, ELV,
Sofortueberweisung, iDeal.
It depends on the settings of the settler organization
and the payment types of the items inside the
shopping cart if the change can be done. If it is not
possible to do the change the response is always a
valid shopping cart.

<?xml version="1.0" encoding="utf-8"?>


<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

Booking Process 172 of 241


DESKLINE 3.0 STANDARD INTERFACE

xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://interface.deskline.net/DSI/XSD">
<Request Company="xxx" Originator="FERATEL" Language="en">
<UpdateShoppingCartPaymentMethod Id="F145B447-F08A-4FB8-8127-8F56C300C1DB"
PaymentMethod="Invoice" />
</Request>
</FeratelDsiRQ>

Response:

On success: see chapter Reading A Shopping Cart.

UPDATE EXTERNAL SHOPPING C ART SETTINGS


It is needed to update the shopping cart with various settings/fields according to the needs of connected
external systems, such as Skidata or European Travel Insurance.

Request

More
Can be
Request field Description empty?*
than one
possible?

Originator The code of the point of sale requesting the data. Provided
by feratel.
Company The code of the company requesting the data. Provided by
feratel.
UpdateShoppingCartExternal Tag used to update settings of an existing shopping cart.
Id ID of the existing shopping cart.
This part is needed for shopping carts having Skidata items inside
ShoppingCartItem Tag used to update settings of an existing shopping cart
item.
Id ID of the existing shopping cart item.
SkidataItems Container element for data needed for items of type
Skidata
SkidataItem Element includes all needed data fro Skidata items
Person For each skidata item data of a person has to be given. This
includes Title (Enumeration Female; Male) FirstName,
LastName and DateOfBirth.
KeyCard If the person wants to load his ticket order onto an existing
keycard, he or she can provide his/her key card numer
which is build up by a ChipId,SerailNumber and Luhn
(number)
This part is needed for shopping carts having cancellation insurance cheked (only mandatory for erv de)
ERVInsuredPersons Container element for data needed for reservations
including cancellation insurance.
Person For each person which is part of the reservation and should
be insured FirstName, LastName and DateOfBirth have to
be given.

Example Request to update a shopping cart with Skidata data

<?xml version="1.0" encoding="utf-8"?>


<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://interface.deskline.net/DSI/XSD">
<Request Company="FERATEL" Originator="FERATEL" Language="en">

Booking Process 173 of 241


DESKLINE 3.0 STANDARD INTERFACE

<UpdateShoppingCartExternal Id="81389548-FC05-4203-9693-481463996E3A">
<ShoppingCartItem Id="db50f55e-234d-4296-9fb4-b9f7e4b373ca">
<SkidataItems>
<SkidataItem>
<Person>
<Title>Female</Title>
<FirstName>Simone</FirstName>
<LastName>Test</LastName>
<DateOfBirth>1986-01-01T00:00:00</DateOfBirth>
</Person>
<!--KeyCard optional-->
<KeyCard>
<ChipId>01</ChipId>
<SerialNumber>16147256250440868207</SerialNumber>
<Luhn>3</Luhn>
</KeyCard>
</SkidataItem>
<SkidataItem>
<Person>
<Title>Male</Title>
<FirstName>Armin</FirstName>
<LastName>Test</LastName>
<DateOfBirth>1986-01-01T00:00:00</DateOfBirth>
</Person>
</SkidataItem>
</SkidataItems>
</ShoppingCartItem>
<ShoppingCartItem Id="db50f55e-234d-4296-9fb4-b9f7e4b373ca">
<SkidataItems>
<SkidataItem>
<Person>
<Title>Male</Title>
<FirstName>Jakob</FirstName>
<LastName>Test</LastName>
<DateOfBirth>2010-01-01T00:00:00</DateOfBirth>
</Person>
</SkidataItem>
</SkidataItems>
</ShoppingCartItem>
</UpdateShoppingCartExternal>
</Request>
</FeratelDsiRQ>

Example Request to update a shopping cart with data of persons to insure

<?xml version="1.0" encoding="utf-8"?>


<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://interface.deskline.net/DSI/XSD">
<Request Company="FERATEL" Originator="FERATEL" Language="en">
<UpdateShoppingCartExternal Id="dc031348-9e1e-4fb2-a074-3c393717909a">
<ERVInsuredPersons>
<Person>
<FirstName>Simone</FirstName>
<LastName>Schanitz</LastName>
<DateOfBirth>1985-01-01</DateOfBirth>
</Person>
<Person>

Booking Process 174 of 241


DESKLINE 3.0 STANDARD INTERFACE

<FirstName>Armin</FirstName>
<LastName>Schanitz</LastName>
<DateOfBirth>1989-01-01</DateOfBirth>
</Person>
</ERVInsuredPersons>
</UpdateShoppingCartExternal>
</Request>
</FeratelDsiRQ>

Response:

On success: see chapter Reading A Shopping Cart.

SET OPTIONAL G UARANTEE


If an accommodation item in shopping cart offers optional guarantee it can be detected by the additional
attribute OptionalGuaranteeSelected in element AccommodationItem in shopping cart. In this case the guest
can choose to give a credit card guarantee. With this guarantee the room stays reserved also after 6 p.m. of
arrival date, so it offers guaranteed late check in. The default value is always false. With this request it is
possible to change to true or back to false again.

Request
More than
Can be
Request field Description empty?*
one
possible?

Originator The code of the point of sale requesting the data. Provided by
feratel.
Company The code of the company requesting the data. Provided by
feratel.
SetOptionalGuarantee- Id of the shopping cart which includes the item of type optional
ToShoppingCart/ Id guarantee
CartItem/ Id of the shopping cart accommodation item which should be
ShoppingCartItemId set
CartItem/ Enumeration true fals, dto set and nset optional guarantee
OptionalGuarantee-
Selected

<?xml version="1.0" encoding="utf-8"?>


<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://interface.deskline.net/DSI/XSD">
<Request Company="FERATEL" Originator=" FERATEL" Language="en">
<SetOptionalGuaranteeToShoppingCart Id="27cab67b-8ea2-44f6-b981-64e988af3de2" >
<CartItem ShoppingCartItemId="d6a1307f-e50b-4ef6-8e52-0c9e7fafa6a7"
OptionalGuaranteeSelected="true"/>
</SetOptionalGuaranteeToShoppingCart>
</Request>
</FeratelDsiRQ>

Response:

On success: see chapter Reading A Shopping Cart.

Booking Process 175 of 241


DESKLINE 3.0 STANDARD INTERFACE

READING A SHOPPING C ART


This function can be used to show the user all items that will be booked along with the payment information
before a booking is submitted.

Request
More than
Can be
Request field Description empty?*
one
possible?

Originator The code of the point of sale requesting the data. Provided by
feratel.
Company The code of the company requesting the data. Provided by
feratel.
CurrencyCode If this element is not send the defined Currency for the Point of
Sale is taken (Originator). If a CurrencyCode different to the
settler currency is send all the prices stay in the settler
currency and the currency factor for the requested guest
currency is provided in the shopping cart. CurrencyCode is the
3-digits long international currency code (e.g. EUR, CHF,…)
ShowShoppingCart Tag used to show an existing shopping cart.
Id ID of the existing shopping cart.

<?xml version="1.0"?>
<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://interface.deskline.net/DSI/XSD">
<Request Company="FERATEL" Originator="FERATEL" CurrencyCode="EUR" >
<ShowShoppingCart Id="26a39404-2325-4660-883b-38d190e5bcf1"/>
</Request>
</FeratelDsiRQ>

Response:

The content of a Shopping Cart XML is also returned after every creation/update. The Shopping Cart is basically
split into these parts: list of all items (accommodation, brochure) with IDs and prices and payment options valid
for this booking along with the total amounts to be paid either to the Service Provider directly or to the
organisation responsible for the settlement.
More
Can be
Response field Description empty?*
than one
possible?

ShoppingCart Id Id of the shopping cart


Timestamp Timestamp of create date of the shoppingcart in format YYYY-
MM-DDTHH:MM:SS
SecureValue A hashkey out of various parameters referring to the booking.
Necessary for the credit card payment/guarantee process.
RefNo Reference Number for the payment provider. Necessary for the
credit card payment/guarantee process.
TransactionType Reservation, BookingOnRequest, InfoRequest
In case of BookingOnRequest an additional attribute
ValidForHours is present, which shows the number of hours the
booking is valid and the service provider has the chance to
confirm the booking. Otherwise the booking is not confirmed.
SalesPointCode Originator/POS-Code

Booking Process 176 of 241


DESKLINE 3.0 STANDARD INTERFACE

GuestSettlerCode Code of Guest Settler responsible for this booking


Content Content of the Shopping Cart – Items and Payment Options
CartItems Accommodation items and Brochures
Accommodations List of all accommodation items in this shopping cart
AccommodationItem Information about the accommodation product in the shopping
cart.
ProductId ID of the product
ShoppingCartItemId ID of the item inside this shopping cart.
PayType Definition of the type of payment for this item.
Enumeration: ServiceProviderPayment / OrganisationPayment
/ SplitPayment
Arrival Date of arrival.
Departure Date of departure.
CancIns Amount of cancellation insurance for this item if values are set
by the guest settler.
ItemName Name of the item
Type Type of the item AccommodationHotel /
AccommodationAppartment / AccommodationCamping
OptionalGuaranteeSelected Attribute only visible if product provides optional guarantee.
False per default. If set to true by the guest CreditCard
guarantee has to be provided and room is reserved also after
18:00 on arrival date. Special Request for Settings for optional
guarantee needed, please see chapter “Set Optional
Guarantee”
NumberOfItems Number of items in the cart.
Parent LocationId Town-ID of the Service Provider connected with the product.
Parent ServiceProvider Name and ID of the Service Provider connected with the
product.
Parent Service Service ID of the service connected with the product.
Duration Length of stay
Occupancy Number of adults and ages of children
Price Detailed price information for this item.
MealCode The meal code that was used.
TotalPrice Total price for this item.
TotalAdultPrice Total adult price for this item.
TotalAdultMeal Total price of meals for adults for this item.
TotalAdultVT Total amount of visitor’s tax for adults for this item.
TotalChildrenPrice Total price for children for this item.
TotalChildrenMeal Total price for meals for children.
TotalChildrenVT Total amount of visitor’s tax for children for this item.
TotalBedlinen Total amount for bed linen for this item.
TotalFinalCleaning Total amount for final cleaning for this item.
Extras - Extra In this tag the name and the standard price of an additional
extras is provided. Note that this is a Standard Price and the
total amount of the extras can be different due to special
discounts (early booker, last minute) or Surcharges (short stay)
Extras - Total Total amount of all additional extras (except bedlinen and final
cleaning) listed in extras including special discounts and
surcharges.

Booking Process 177 of 241


DESKLINE 3.0 STANDARD INTERFACE

PayNights Amount of nights that have to be paid; can be different from


the length of the stay (“stay 7 pay 6” calculations for example).
AdditionalServices List of all additional service items in this shopping cart
AdditionalServiceItem Information about the additional service product in the
shopping cart.
ProductId ID of the product
ShoppingCartItemId ID of the item inside this shopping cart.
PayType Definition of the type of payment for this item.
Enumeration: ServiceProviderPayment / OrganisationPayment
/ SplitPayment
Arrival Date of arrival.
CancIns Amount of cancellation insurance for this item if values are set
by the guest settler.
ItemName Name of the item
Type Type of the item AdditionalService
ExternalSystemType ExternalSystemType of the item AdditionalService e.g. Skidata,
optional attribute only exists if additional service is of an
external type
NumberOfItems Number of items in the cart.
Parent LocationId Town-ID of the Service Provider connected with the product.
Parent ServiceProvider Name and ID of the Service Provider connected with the
product.
Parent Service Service ID of the service connected with the product.
Duration Type None / Days / Hours / Minutes and the according value,
zero if type is None
StartTime hh:mm:ss, 00:00:00 if no start time
Price Detailed price information for this item.
TotalPrice Total price for this item.
IsBestPrice True or false
BasePrice Base price of the item.
Brochures List of all brochure items in this shopping cart
BrochureItem Information about the brochures in the shopping cart.
ShopItemtId ID of the brochure
ShoppingCartItemId ID of the item inside this shopping cart.
ItemName Name of the brochure
Type Type of the Item Brochure
NumberOfItems Number of items in the cart.
Variation Name and Id
Weight Weight of the brochure in gram
ShopArticle List of all shop article items in this shopping cart
ShopArticleItem Information about the shop articles in the shopping cart.
ShopItemtId ID of the shop aricle
ShoppingCartItemId ID of the item inside this shopping cart.
ItemName Name of the shop article
Type Type of the Item Article
NumberOfItems Number of items in the cart.
Variation Name and Id

Booking Process 178 of 241


DESKLINE 3.0 STANDARD INTERFACE

Weight Weight of the brochure in gram


Price Price of the shop article
Packages List of all package items in this shopping cart
PackageItem Information about the packages in the shopping cart.
ProductId ID of the package
ShoppingCartItemId ID of the item inside this shopping cart.
PayType Definition of the type of payment for this item.
In case of packages always OrganisationPayment
Arrival Date of arrival.
Departure Date of departure.
CancIns Amount of cancellation insurance for this item if values are set
by the guest settler.
ItemName Name of the item
Type Type of the item Package
Duration Length of stay in DAYS
Occupancy Number of adults and ages of children
Price Detailed price information for this item.
TotalSellPrice Total price for this item.
AdultSellPrice Total adult price for this item.
ChildSellPrice Total price for children for this item.
VisitorTax Total amount of visitor’s tax for this item.
BookingFee Amount of the booking fee to the guest settler for this package
item.
Details Container elment for items inside the package
PackageProductItem Element for each item inside the package
ProductId ID of the product
ShoppingCartItemId ID of the item inside this shopping cart.
Arrival Date of arrival.
Departure Date of departure.
CancIns Amount of cancellation insurance for this item if values are set
by the guest settler.
ItemName Name of the item
Type Type of the item. Enumeration: AdditionalService,
AccommodationHotel, AccommodationAppartment,
AccommodationCamping
NumberOfItems Number of items in the section.
Parent Service Provider Id and Name of the service provider of the
product inside the section.
Duration Type can be Days, Nights, Hours and Minutes. Important:
Accommodation items have duration type nights. Package
duration is usually number of accommodation nights plus one
in days. Additional service items have duration types days,
hours or minutes.
Example: Package “Skiweek” from Saturday to Saturday, so
duration is 8 days including an accommodation item for 7
nights and skipass for 8 days, because arrival and departure day
are included in package duration.
Occupancy Number of adults and ages of children

Booking Process 179 of 241


DESKLINE 3.0 STANDARD INTERFACE

PaymentOptions Information regarding the payment process.


PaymentMethods The methods that were used when calculating the basket.
Transaction PrePaymentMethod NoPayment means that pre-payment is not required. The
values are
NoPayment/Invoice/CreditCard/ELV/Sofortueberweisung/iDeal.
Transaction NoPayment means that final payment is not required. The
FinalPaymentMethod values are NoPayment/Invoice.
Transaction NoPayment means that it’s not required to guarantee the
GuaranteePaymentMethod booking and the product can be booked directly. If it is
CreditCard a guarantee has to be provided.
PaymentSettings Additional settings about the booking.
UseCancellationInsurance True/false if cancellation insurance is available.
CancellationInsuranceChecked True/false if the cancellation insurance is checked by the guest.
UseBookingFee True/false if booking fee is used.
IsOnlyGuarantee If the credit card data was only used for a guarantee or if it was
actually charged.
Payments If there are any payments to be made they will be listed here.
ServiceProviderPayment If any amount must be paid directly to the service provider,
they will be listed here with the amount.
Name The name of the service provider that requires payment.
Id The id of the service provider that requires payment.
Amount Total Total amount that has to be paid to this service provider.
Amount PrePayment Amount required as prepayment to the service provider.
Attribute PaymentMethod shows if prepayment has to be done
via Invoice or CreditCard. In case of CreditCard only guarantee,
no real credit card payment is required
DueDate PrePayment If the pre-payment amount equals the total amount and the
pre-payment due date is the standard value of 1980-01-01 (or:
in the past) then the total amount has to be paid to the service
provider directly.
Amount FinalPayment If the due date is equal to the arrival date or the amount of the
final payment is zero then there is no final payment / the final
payment has to be paid directly to the service provider.
DueDate FinalPayment If the due date is equal to the arrival date or the amount of the
final payment is zero then there is no final payment / the
amount has to be paid directly to the service provider.
Organisation Payment If the guest has to pay directly to the guest settler than the
amounts will be visible in these values. It could also be possible
that for example the pre-payment has to be made to the guest
settler and the final payment directly to the service provider.
Amount PrePayment If the value is zero than there is no payment required to the
guest settler. If there is a prepayment required and
TransactionPrePaymentMethod is CreditCard,
Sofortueberweisung, iDeal or ELV, this amount has to be paid!
It is the same amount like in
AmountOrganisationPrePayment!
DueDate PrePayment If the value is zero the due date will have the default value
1980-01-01 and there is no payment required to the guest
settler. In case of prepayment via credit card the date time
shown is now + one hour
Amount FinalPayment If the value is zero than there is no payment required to the
guest settler. If there is a value TransactionFinalPayment is
Invoice.

Booking Process 180 of 241


DESKLINE 3.0 STANDARD INTERFACE

DueDate FinalPayment If the amount of final payment is zero the due date can be
ignored and there is no final payment required to the guest
settler.
Total Summary about the total price for all items
Amount Service Provider Total sum of all pre-payments that should be made to service
PrePayment providers.
Amount Service Provider Final Total sum of all final payments that should be made to service
Payment providers.
Amount Organisation Pre Total sum of all pre-payments that should be made to the guest
Payment settler. If there is a prepayment required and
TransactionPrePaymentMethod is CreditCard,
Sofortueberweisung, iDeal or ELV, this amount has to be paid!
It is the same amount like in
OrganisationPayment/AmountPrePayment!
Amount Organisation Final Total sum of all final payments that should be made to guest
Payment settler.
Booking Fee Set If the guest settler uses a booking fee or not. Can only be used
if the guest settler also requires payments.
Amount Booking Fee Amount of the booking fee to the guest settler. Can only be
used if the guest settler also requires payments.
Cancellation Insurance Set If the cancellation insurance is activated or not.
Amount Cancellation Insurance Amount of the cancellation insurance when available.
Amount Visitor Tax Total amount of the visitor’s tax.
AmountVat Total amount of value added tax.
Amount PrePayment Total amount of all pre-payments that have to be made by the
guest.
Amount FinalPayment Total amount of all final payments that have to be made by the
guest.
Possible Payments Methods
Transaction PrePayment Method NoPayment means that pre-payment is not required. The
values are
NoPayment/Invoice/CreditCard/ELV/Sofortueberweisung/iDeal.
Transaction FinalPayment NoPayment means that final payment is not required. The
Method values are NoPayment/Invoice.
Transaction GuaranteePayment NoPayment means that it’s not required to guarantee the
Method booking and the product can be booked directly. Guarantee can
only be NoPayment/CreditCard.
Guest Id ID of the guest address connected with the transaction (0 if
unassigned at the moment)
WishNotes Notes from guest
AccompaniedBy Information about additional travelers
Notes Internal Comment, not entered by the guest.
Currency Currency Code of the values in the shopping cart. (Settler
Currency)
Currency GuestCurrency Requested Currency (Guest Currency)
Currency Factor Factor with which the amounts in the shopping cart has to be
DIVIDED to get the prices in guest currency.
Currency Round Shows th rule for rounding on last digit, usually 1, but e.g. in
case of currency CHF the smallest unit is 5 Rappen means 1.63
CHF turns to 1.65 CHF.

Booking Process 181 of 241


DESKLINE 3.0 STANDARD INTERFACE

<?xml version="1.0" encoding="utf-8"?>


<FeratelDsiRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" Status="0" Message="OK"
xmlns="http://interface.deskline.net/DSI/XSD">
<Result Index="1">
<ShoppingCart Id="707ac6c5-3283-4d64-979b-27fcde2a47b6"
SecureValue="6e9613e76594c417c0ee19aab3f6d84c" RefNo="FERATEL9251" Timestamp="2016-09-27T15:40:00">
<TransactionType>Reservation</TransactionType>
<SalesPointCode>FERATEL</SalesPointCode>
<GuestSettlerCode>FERATEL</GuestSettlerCode>
<Content>
<CartItems>
<Accommodations>
<AccommodationItem ProductId="c584a48f-0fbf-458f-a9c9-bdb18f489d5d" ShoppingCartItemId="cc1f6ce6-
dbd2-4a7a-8f6e-cada8f909b8b" PayType="ServiceProviderPayment" Arrival="2015-03-07" Departure="2015-03-14"
CancIns="0" ItemName="Doppelzimmer, LM" Type="AccommodationHotel">
<NumberOfItems>1</NumberOfItems>
<Parent LocationId="5c7e1d37-0060-4811-a996-a8b36094d01e">
<ServiceProvider Name="Simotel">dc1defe3-999a-4097-a5bf-7bd86a14e28a</ServiceProvider>
<Service>94e9f02a-5001-446f-9b7b-78b43ef558da</Service>
</Parent>
<Duration Type="Day">7</Duration>
<Occupancy NumberOfAdults="2">
<ChildrenAges />
</Occupancy>
<Price>
<MealCode>HB</MealCode>
<TotalPrice>2580.4</TotalPrice>
<TotalAdultPrice>2403</TotalAdultPrice>
<TotalAdultMeal>0</TotalAdultMeal>
<TotalAdultVT>28</TotalAdultVT>
<TotalChildrenPrice>0</TotalChildrenPrice>
<TotalChildrenMeal>0</TotalChildrenMeal>
<TotalChildrenVT>0</TotalChildrenVT>
<TotalBedlinen>2.7</TotalBedlinen>
<TotalFinalCleaning>29.7</TotalFinalCleaning>
<Extras>
<Extra Name="Extra 100" StandardPrice="100" />
<Extra Name="ExtrasTest" StandardPrice="30" />
<Total Price="117" />
<!--Note that this total amount of extras includes discounts and surcharges and is therefore not always
assumed to be the sum of the standard prices listed above!-->
</Extras>
<PayNights>7</PayNights>
</Price>
</AccommodationItem>
</Accommodations>
<AdditionalServices>
<AdditionalServiceItem ProductId="24186928-a111-4417-a11b-49f3338743b2"
PayType="OrganisationPayment" Arrival="2015-03-21" CancIns="0" ShoppingCartItemId="9d310df1-8870-4713-
8d6b-e1750cffbf35" ItemName="2 Tages Skipass" Type="AdditionalService" ExternalSystemType="Skidata">
<NumberOfItems>1</NumberOfItems>
<Parent LocationId="69ccc2f8-2c86-4dd2-a855-fc5bdf342e88">
<ServiceProvider Name="Bergbahnen Dobratsch">7326ec1c-a9c4-4515-b1f7-
883a287a35be</ServiceProvider>
<Service>29e4b72f-d22f-4fa2-9b32-5950b51388a8</Service>
</Parent>
<Duration Type="Day">7</Duration>
<StartTime>00:00:00</StartTime>
<Price>
<TotalPrice>260</TotalPrice>

Booking Process 182 of 241


DESKLINE 3.0 STANDARD INTERFACE

<IsBestPrice>false</IsBestPrice>
<BasePrice>260</BasePrice>
</Price>
<SkidataItems>
<SkidataItem>
<Person>
<Title>Female</Title>
<FirstName>Simone</FirstName>
<LastName>Test</LastName>
<DateOfBirth>1986-01-01T00:00:00</DateOfBirth>
</Person>
<KeyCard>
<ChipId>01</ChipId>
<SerialNumber>16147256250440868207</SerialNumber>
<Luhn>3</Luhn>
</KeyCard>
</SkidataItem>
</SkidataItems>
</AdditionalServiceItem>
</AdditionalServices>
<Brochures />
<Packages />
</CartItems>
<PaymentOptions>
<CalculatedBasketResult>
<PaymentMethods>
<TransactionPrePaymentMethod>NoPayment</TransactionPrePaymentMethod>
<TransactionFinalPaymentMethod>NoPayment</TransactionFinalPaymentMethod>
<TransactionGuaranteePaymentMethod>CreditCard</TransactionGuaranteePaymentMethod>
</PaymentMethods>
<PaymentSettings>
<UseCancellationInsurance>true</UseCancellationInsurance>
<CancellationInsuranceChecked>true</CancellationInsuranceChecked>
<UseBookingFee>false</UseBookingFee>
<IsOnlyGuarantee>true</IsOnlyGuarantee>
</PaymentSettings>
<Payments>
<ServiceProviderPayment Name="Simotel" Id="3ffc7c9a-0528-49f5-9614-5a3e4a92cb26">
<AmountTotal>2580.4</AmountTotal>
<AmountPrePayment PaymentMethod="None">0</AmountPrePayment>
<DueDatePrePayment>1980-01-01T00:00:00</DueDatePrePayment>
<AmountFinalPayment>2580.4</AmountFinalPayment>
<DueDateFinalPayment>1980-01-01T00:00:00</DueDateFinalPayment>
</ServiceProviderPayment>
<OrganisationPayment Name="Feratel Demo Destination" Id="9bac10eb-4bf8-43ee-95d2-6fbba009f2ae">
<AmountTotal>260</AmountTotal>
<AmountPrePayment>260</AmountPrePayment>
<DueDatePrePayment>2015-03-04T00:00:00</DueDatePrePayment>
<AmountFinalPayment>0</AmountFinalPayment>
<DueDateFinalPayment>1980-01-01T00:00:00</DueDateFinalPayment>
</OrganisationPayment>
<ExternalPayment Type="ERVAT">
<AmountTotal>1.40</AmountTotal>
<AmountPrePayment>1.40</AmountPrePayment>
<DueDatePrePayment>2015-02-25</DueDatePrePayment>
<AmountFinalPayment>0</AmountFinalPayment>
<DueDateFinalPayment>1980-01-01</DueDateFinalPayment>
</ExternalPayment>
<Total>
<AmountServiceProviderPrePayment>0</AmountServiceProviderPrePayment>
<AmountServiceProviderFinalPayment>2580.4</AmountServiceProviderFinalPayment>

Booking Process 183 of 241


DESKLINE 3.0 STANDARD INTERFACE

<AmountOrganisationPrePayment>260</AmountOrganisationPrePayment>
<AmountOrganisationFinalPayment>0</AmountOrganisationFinalPayment>
<BookingFeeSet>false</BookingFeeSet>
<AmountBookingFee>0</AmountBookingFee>
<CancellationInsuranceSet>true</CancellationInsuranceSet>
<AmountCancellationInsurance>1.4</AmountCancellationInsurance>
<AmountVisitorTax>0</AmountVisitorTax>
<AmountVat>0</AmountVat>
<AmountPrePayment>261.40</AmountPrePayment>
<AmountFinalPayment>2580.4</AmountFinalPayment>
</Total>
</Payments>
</CalculatedBasketResult>
<PossiblePaymentsMethods>
<Option>
<TransactionPrePaymentMethod>NoPayment</TransactionPrePaymentMethod>
<TransactionFinalPaymentMethod>NoPayment</TransactionFinalPaymentMethod>
<TransactionGuaranteePaymentMethod>NoPayment</TransactionGuaranteePaymentMethod>
</Option>
<Option>
<TransactionPrePaymentMethod>NoPayment</TransactionPrePaymentMethod>
<TransactionFinalPaymentMethod>NoPayment</TransactionFinalPaymentMethod>
<TransactionGuaranteePaymentMethod>CreditCard</TransactionGuaranteePaymentMethod>
</Option>
</PossiblePaymentsMethods>
</PaymentOptions>
</Content>
<Guest Id="00000000-0000-0000-0000-000000000000">
<WishNotes />
<AccompaniedBy>FirstName1 LastName1 (1900-01-01); FirstName2 LastName2 (1900-01-
01)</AccompaniedBy>
<Notes />
</Guest>
<Currency GuestCurrency="CHF" Factor="0.7731" Round="5">EUR</Currency>
<!-- This is an example for requested currency is Swiss Franc and
settler currency is Euro, take the euro prices in the shopping cart
and DIVIDE with the factor provided to get the prices in Swiss Franc-->
</ShoppingCart>
</Result>
</FeratelDsiRS>

PRE-PAYMENT INFORMATION O RGANISATION


The settler organization defines which payment types and payment methods are provided and also defines due
dates for pre and final payments. It is also possible that the service provider has his own individual settings.
This information is shown in shopping cart. If there are items in the shopping cart of type SplitPayment or
OrganisationPayment, a payment to the organization has to be done.

If TransactionPrePaymentMethod or TransactionFinalPaymentMethod is Invoice, the guest gets a booking


confirmation with the bank data of the organization and the amounts she or he has to pay until the defined due
dates. For example total amount which has to be paid to organization is 1200. 120 (10%) has to be prepaid until
2011-09-09 and final payment of 1080 until 2011-10-23.

<OrganisationPayment Name="Feratel Demo Destination" Id="1da11046-9505-4313-9d94-82903f2bcc04">


<AmountTotal>1200</AmountTotal>
<AmountPrePayment>120</AmountPrePayment>
<DueDatePrePayment>2011-09-09T00:00:00</DueDatePrePayment>
<AmountFinalPayment>1080</AmountFinalPayment>

Booking Process 184 of 241


DESKLINE 3.0 STANDARD INTERFACE

<DueDateFinalPayment>2011-10-23T00:00:00</DueDateFinalPayment>
</OrganisationPayment>

If TransactionPrePaymentMethod is CreditCard, Sofortueberweisung, iDeal or ELV, the AmountPrePayment has


to be prepaid via credit card/bank account if the shopping cart will be committed, so the due date of
prepayment is now (+1 hour). If final payment amount not zero, there is also a final payment required. This is
only possible via method Invoice. Settler can define that in case of credit card payment the full amount has to
be paid or because there is to less time for splitting pre and final payment also the full amount has to be paid at
ones. If any of the amounts is zero the according due date can be ignored.

<OrganisationPayment Name="Feratel Demo Destination" Id="1da11046-9505-4313-9d94-82903f2bcc04">


<AmountTotal>568</AmountTotal>
<AmountPrePayment>568</AmountPrePayment>
<DueDatePrePayment>2011-08-30T13:05:39.6428297+02:00</DueDatePrePayment>
<AmountFinalPayment>0</AmountFinalPayment>
<DueDateFinalPayment>2011-09-09T00:00:00</DueDateFinalPayment>
</OrganisationPayment>

PRE-PAYMENT INFORMATION SERVICE PROVIDER


There is a setting for service providers where for any product they can define if a pre-payment is required
(percentage) and the due-date for pre-payment and final payment. If this is used then the value will be
accordingly. If the guest books 2 days in advance but the service provider requires the pre-payment 4 days in
advance then the pre-payment value will be the total price! This is a valid case, if the service provider does not
even want to allow short-term bookings there’s another option for this (booking stop).

There are several cases depending on the existing Deskline settings:

No pre-payment required, payment directly at the hotel

Booking-Date: 2013-10-04
Arrival Date: 2013-10-24, 7 nights
Total price: € 100

Product Settings: 0% Pre-Payment, Payment directly at the hotel.

Shopping Cart Content:

<ServiceProviderPayment Name="Provider A" Id="f4a3d76e-68e9-4b27-b7d8-249398a6ee8f">


<AmountTotal>100</AmountTotal>
<AmountPrePayment PaymentMethod="None" >0</AmountPrePayment>
<DueDatePrePayment>1980-01-01T00:00:00</DueDatePrePayment>
<AmountFinalPayment>100</AmountFinalPayment>
<DueDateFinalPayment>1980-01-01T00:00:00</DueDateFinalPayment>
</ServiceProviderPayment>

Output Deskline Web:

Booking Process 185 of 241


DESKLINE 3.0 STANDARD INTERFACE

AmountFinalPayment = AmountTotal
DueDatePrePayment = 0
DueDateFinalPayment = 0

Pre-Payment required and final payment before arrival to hotel

Booking-Date: 2012-04-10
Arrival Date: 2012-09-01, 7 nights
Total price: € 614

The hotel requires the pre-payment:

Product Settings: 10% Pre-Payment 10 days after the booking, Final Payment 10 days before the
arrival.

Shopping Cart Content:

<ServiceProviderPayment Name="Simotel" Id="dc1defe3-999a-4097-a5bf-7bd86a14e28a">


<AmountTotal>614</AmountTotal>
<AmountPrePayment PaymentMethod="Invoice">74</AmountPrePayment>
<DueDatePrePayment>2012-04-20T00:00:00</DueDatePrePayment>
<AmountFinalPayment>540</AmountFinalPayment>
<DueDateFinalPayment>2012-08-22T00:00:00</DueDateFinalPayment>
</ServiceProviderPayment>

Output Deskline Web:

DueDateFinalPayment = Date of Arrival – 10 days.

Pre-Payment required, but final payment directly at the hotel

Booking-Date: 2013-10-04
Arrival Date: 2013-10-24, 7 nights
Total price: € 100

The hotel only requires the pre-payment:

Product Settings: 50% Pre-Payment per credit card, Final Payment directly at the hotel.

Shopping Cart Content:

<ServiceProviderPayment Name="the Schwartz-Inn" Id="f4a3d76e-68e9-4b27-b7d8-249398a6ee8f">


<AmountTotal>100</AmountTotal>
<AmountPrePayment PaymentMethod="CreditCard">50</AmountPrePayment>
<DueDatePrePayment>1980-01-01T00:00:00</DueDatePrePayment>
<AmountFinalPayment>50</AmountFinalPayment>
<DueDateFinalPayment>2013-10-24T00:00:00</DueDateFinalPayment>
</ServiceProviderPayment>

Booking Process 186 of 241


DESKLINE 3.0 STANDARD INTERFACE

Output Deskline Web:

DueDateFinalPayment = Date of Arrival.

Pre-Payment and Final Payment required, but Final Payment days is not possible:

Booking-Date: 2010-04-22
Arrival Date: 2010-05-02, 7 nights
Total price: € 124

No Final Payment can be made 14 days before arrival, so the pre-payment will be the total amount:

Product Settings: 40% Pre-Payment 3 days after the booking, Final Payment 14 days before arrival.

Shopping Cart Content:

<ServiceProviderPayment Name="Moselebauer, Hotel" Id="83c84b24-9b1c-45b5-9c03-29e6d6845b9c">


<AmountTotal>124</AmountTotal>
<AmountPrePayment PaymentMethod="Invoice">124</AmountPrePayment>
<DueDatePrePayment>2010-04-25T00:00:00</DueDatePrePayment>
<AmountFinalPayment>0</AmountFinalPayment>
<DueDateFinalPayment>1980-01-01T00:00:00</DueDateFinalPayment>
</ServiceProviderPayment>

Output Deskline Web:

 The total price is displayed to be paid immediately to the service provider so the guest knows to
contact the hotel directly. DueDatePrePayment = booking date + “pre-pay until” value,
DueDateFinalPayment = 0, AmountPrePayment = AmountTotal

Pre-Payment and Final Payment required, but payments would not be possible in time:

Booking-Date: 2010-04-22
Arrival Date: 2010-05-02, 7 nights
Total price: € 159,6

No pre-payment and final payment can be made in time so the pre-payment will be the total amount:

Product Settings: 20% Pre-Payment 21 days after the booking, Final Payment 14 days before arrival.
Shopping Cart Content:
Booking Process 187 of 241
DESKLINE 3.0 STANDARD INTERFACE

<ServiceProviderPayment Name="the Schwartz-Inn" Id="f4a3d76e-68e9-4b27-b7d8-249398a6ee8f">


<AmountTotal>159.6</AmountTotal>
<AmountPrePayment>159.6</AmountPrePayment>
<DueDatePrePayment>2010-05-02T00:00:00</DueDatePrePayment>
<AmountFinalPayment>0</AmountFinalPayment>
<DueDateFinalPayment>1980-01-01T00:00:00</DueDateFinalPayment>
</ServiceProviderPayment>

Output Deskline Web:

 The total price is displayed to be paid immediately to the service provider so the guest knows to
contact the hotel directly. DueDatePrePayment = booking date + “pre-pay until” value,
DueDateFinalPayment = 0, AmountPrePayment = AmountTotal

Booking Process 188 of 241


DESKLINE 3.0 STANDARD INTERFACE

COMMITTING A TRANSACTION
Only when a booking is committed the services with availabilities will be blocked for the guest. If the
availabilities are gone by the time a commit is sent, then the booking will not be successful and return an error
(“Availability check failed”). If a credit card guarantee or a credit card payment is required, commitment of a
shopping cart is not possible; Message would be "Commitment of shopping cart is not possible. Credit card
data has to be provided." For committing this shopping cart see chapter “Credit Card guarantee or payment
with Datatrans”.

Request
More than
Request field Description Can be empty?* one
possible?

Originator The code of the point of sale requesting the data. Provided by
feratel.
Company The code of the company requesting the data. Provided by
feratel.
CommitShoppingCart Tag used to commit an existing shopping cart.
Id ID of the existing shopping cart.
UserId ID of the user that should be connected with this transaction.
LinkKey Optional value. LinkKey is used to mark where a booking is
coming from. For example if a summer and a winter version is
used of a website the LinkKey could be “summer” or “winter”
for the customer to have a statistic about where bookings are
coming from. Use of the LinkKey has to be coordinated with
the customer in order to get the use case / statistic that the
customer needs.

Response:

The important part of the response is of course our internal booking ID and the transaction number that is
written on the guest confirmation:
More
Response field Description Can be empty?* than one
possible?

Booking
Id Internal transaction id
SettlerCode Code of the guest settler responsible for handling the
booking.
Number Booking confirmation number written on the guest
confirmation
Type Reservation or BookingOnRequest
SalesChannelId Sales Channel that was used for the search and for
adding items.
CurrencyCode Currency of the booking (settler currency) and all prices
listed in the shopping cart are in this currency
CurrencyFactor Element GuestCurrency shows the requested Currency
of the shopping cart and the factor provided can be
used to display the result in the guest currency to the
guest. The prices should be divided by the factor to get
the right result in guest currency.
ValidUntil For booking on request, otherwise the default is 1980-
01-01. If the date is in the future than this is the date
until the service provider has to confirm the booking.
Booking Process 189 of 241
DESKLINE 3.0 STANDARD INTERFACE

DepositType The type of payment used for the deposit (pre-


payment). The values are NoPayment, Invoice,
CreditCard, Cash, ELV, Sofortueberweisung, iDeal
DepositAmount Pre-payment necessary for this booking
DepositDueDate Due-date for pre-payment
DepositPaid Amount deposit already paid (for example when credit
card was directly charged)
DepositPaidDate Date the deposit was paid.
FinalType The type of payment used for the final payment. The
values are NoPayment, Invoice, CreditCard, Cash, ELV
FinalAmount Final payment amount
FinalDueDate Final payment due-date.
FinalPaid Amount final payment already paid (for example when
credit card was directly charged)
FinalPaidDate Date the final payment was paid.
LinkKey The key used for this booking. Right now this is by
default the code of the POS. This is the same link key
used by the web system so the booking can be
identified. This code can be sent for example WINTER
for winter version of the website or SUMMER for
summer version of the website. No special characters.
BookingOptions Details about the payment calculation.
BasketCalculation
BasketSummary
CancellationInsurance If cancellation insurance was used, the amount is
Amount returned here.
CancellationInsurance VATAmount, 0 if included.
VATAmount
BookingFee Amount If a booking fee must be paid, the amount is returned
here.
BookingFee VATAmount VATAmount, 0 if included.
PrePayment Amount Amount for the pre-payment necessary for the booking.
PrePayment VAT VATAmount, 0 if included.
PrePayment DueDate Due-date for pre-payment.
FinalPayment Amount Amount for the final payment necessary for the
booking.
FinalPayment VAT VATAmount, 0 if included.
FinalPayment DueDate Due-date for final payment.
SPPayment Amount Total amount of service-provider items.
TotalPayment Amount Total booking amount.
TotalPayment VAT VATAmount, 0 if included.
Details Details of the items inside the booking
Weight Weight is in use for items like brochures.
GroupNumber Items of the same service provider are inside of one
group with same number.
Important: Items of one package are inside one group
number, the summarizing item is of type Package and
the others are presented in their own Detail element
with same group number but with their own type.
Type Type of the product
(Accommodation/AdditionalService).
Booking Process 190 of 241
DESKLINE 3.0 STANDARD INTERFACE

Order Order inside the booking.


DateFrom Day of arrival.
DateTo Day of departure.
TimeFrom Start time, will be of use for additional services.
TimeTo End time, will be of use for additional services.
UnitNumber Number of units
AdultNumber Number of adults
ChildrenNumber Number of children
ChildrenAges Ages of children
ServiceProviderId Service Provider ID
ServiceProviderName Service Provider Name
ServiceId Service ID
ProductId Product ID
ProductName Product Name
Price Total price for this item.
MealType Meal type included
VatAmount VATAmount, 0 if included.
PaymentType Enumeration: ServiceProviderPayment,
OrganisationPayment, SplitPayment
Guest The element for the guest address connected to the
reservation.
Id Id of the guest address (that is used to commit a
booking or return a guest address)
Company Company name from the guest address
LastName Last name from the guest address
LastName Last name from the guest address
SalutationId Salutation ID (see KeyValues Salutations)
Title Salutation string
Salutation Generated string based on salutation ID and name
Birthday Date of birth from the guest address
Address Address line 1
AltAddress Address line 2
Phone Phone number from the guest address
Fax Fax number from the guest address
Mobile Mobile phone number from the guest address
Email Email from the guest address
Country Country code (see KeyValues GuestCountries)
ZipCode Zip code from the guest address
City City from the guest address
Language Language assigned to the guest
Reusable Does the guest want to receive the newsletter of the
destination / Does the guest allow that his contact data
is used for marketing purposes by the destination?

Booking Process 191 of 241


DESKLINE 3.0 STANDARD INTERFACE

<?xml version="1.0"?>
<FeratelDsiRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
Status="0" Message="OK" xmlns:debug="http://interface.deskline.net/DSI/XSD">
<Result Index="1">
<Booking>
<Id>c845981e-ebff-457a-ae3e-03383628b1ff</Id>
<SettlerCode>FERATEL</SettlerCode>
<Number>639</Number>
<Type>Reservation</Type>
<SalesChannelId>59994450-0280-4cc1-b097-5c1d7eb09fae</SalesChannelId>
<CurrencyCode>EUR</CurrencyCode>
<CurrencyFactor GuestCurrency="CHF" > 0.7731</CurrencyFactor>
<!-- Example: prices in this booking are in EUR, to convert to guest currency CHF take the prices and DIVIDE with the factor
provided-->
<ValidUntil>1980-01-01T00:00:00</ValidUntil>
<CalculationOption>VisitorsTax</CalculationOption>
<DepositType>NoPayment</DepositType>
<DepositAmount>0</DepositAmount>
<DepositDueDate>1980-01-01T00:00:00</DepositDueDate>
<DepositPaid>0</DepositPaid>
<DepositPaidDate>1980-01-01T00:00:00</DepositPaidDate>
<FinalType>Cash</FinalType>
<FinalAmount>0</FinalAmount>
<FinalDueDate>1980-01-01T00:00:00</FinalDueDate>
<FinalPaid>0</FinalPaid>
<FinalPaidDate>1980-01-01T00:00:00</FinalPaidDate>
<ToscLinkKey></ToscLinkKey>
<BookingOptions>
<BasketCalculation>
<BasketSummary>
<CancellationInsurance Amount="0" VATAmount="0" />
<BookingFee Amount="0" VATAmount="0" />
<PrePayment Amount="0" VATAmount="0" DueDate="1980-01-01" />
<FinalPayment Amount="0" VATAmount="0" DueDate="1980-01-01" />
<SPPayment Amount="2394" />
<TotalPayment Amount="2394" VATAmount="0" ProductAmount="2394" />
</BasketSummary>
</BasketCalculation>
</BookingOptions>
<Details>
<Detail>
<Weight>0</Weight>
<GroupNumber>1</GroupNumber>
<Type>AccommodationHotel</Type>
<Order>1</Order>
<DateFrom>2010-05-01</DateFrom>
<DateTo>2010-05-08</DateTo>
<TimeFrom>00:00:00.0000000+02:00</TimeFrom>
<TimeTo>00:00:00.0000000+02:00</TimeTo>
<UnitNumber>1</UnitNumber>
<AdultNumber>2</AdultNumber>
<ChildrenNumber>0</ChildrenNumber>
<ChildrenAges />
<ServiceProviderId>66b3d961-b8ea-4fb2-9497-6f8b8662c8c8</ServiceProviderId>
<ServiceProviderName>Evergreen Terrace</ServiceProviderName>
<ServiceId>3de7bfad-a435-4795-baa2-d6d7b8c06bd2</ServiceId>
<ProductId>8878d803-31cb-4eeb-b807-cc1a7180b9ae</ProductId>
<ProductName>Mein Produkt</ProductName>
<ProductNameAlternative />
<Price>1400</Price>
<MealType>BB</MealType>
<VatAmount>0</VatAmount>
<PaymentType>ServiceProviderPayment</PaymentType>
</Detail>
<Detail>
<Weight>0</Weight>

Booking Process 192 of 241


DESKLINE 3.0 STANDARD INTERFACE

<GroupNumber>1</GroupNumber>
<Type>AccommodationHotel</Type>
<Order>2</Order>
<DateFrom>2010-05-01</DateFrom>
<DateTo>2010-05-08</DateTo>
<TimeFrom>00:00:00.0000000+02:00</TimeFrom>
<TimeTo>00:00:00.0000000+02:00</TimeTo>
<UnitNumber>1</UnitNumber>
<AdultNumber>2</AdultNumber>
<ChildrenNumber>0</ChildrenNumber>
<ChildrenAges />
<ServiceProviderId>6414a88a-28d7-40b4-aa85-6bd1700d7b80</ServiceProviderId>
<ServiceProviderName>Hotel Sonne</ServiceProviderName>
<ServiceId>2fdf6da5-a718-4391-9ee6-b9cf6c616976</ServiceId>
<ProductId>abe443b3-b4f4-4467-8bf4-16ab20a112ef</ProductId>
<ProductName>Zweibettzimmer, Bad, WC</ProductName>
<ProductNameAlternative />
<Price>994</Price>
<MealType>BB</MealType>
<VatAmount>0</VatAmount>
<PaymentType>ServiceProviderPayment</PaymentType>
</Detail>
</Details>
<Guest>
<Id>125bf5de-1790-4d32-b326-d03e6d27d183</Id>
<FirstName>Deskline</FirstName>
<LastName>Interface</LastName>
<Company>Thomas Test</Company>
<SalutationId>5640fbfd-8103-4b68-b04a-469a4b57863e</SalutationId>
<Title>Mr</Title>
<Salutation>Dear Mr Interface</Salutation>
<Address>a1.</Address>
<AltAddress />
<Phone />
<Fax>+432449416489</Fax>
<Mobile />
<Email>[email protected]</Email>
<Country>BT</Country>
<ZipCode>9020</ZipCode>
<City>Klagenfurt</City>
<Language>en</Language>
<Reusable>true</Reusable>
</Guest>
</Booking>
</Result>
</FeratelDsiRS>

Booking Process 193 of 241


DESKLINE 3.0 STANDARD INTERFACE

C REDIT CARD GUARANTEE OR PAYMENT WITH DATATRANS


There are two different cases when credit card information has to be provided. First is saving bookings without
payment. This means that the guest has to pay the whole amount directly to the service provider and nothing
to the tourism destination. But we offer a way to additionally check the credit card of the guest for guarantee
purposes. Second would be required organization payment with credit card/bank account. The pre payment
amount to organization then will be send to Datatrans.

Important: Since we are not allowed to handle credit card numbers directly, we are working together with a
payment provider (Datatrans). This means that there is a whole different workflow to submit bookings in this
case. This workflow is defined in the following way:

Search result &


shopping cart Portal/Website displays the
Lightbox from
data from DSI shopping cart and has to send
Datatrans opens where
values from DSI and parameters
the guest has to enter
via Lightbox or Redirect Mode to
his creditcard/account
Datatrans.
data

All the values


described below are If Datatrans sent us a success
passed on to a URL message we immediately Datatrans checks the
that has to be commit the booking. card/account details and
provided by the provides feratel with a
Portal/Website. This status
page can be used to In case of problems we (success/error/cancel) to
display the booking directly forward the a page with a URL defined
confirmation or datatrans error message. by us
error messages as
needed.

How to find out if credit card data/bank account must be provided?

Inside the shopping cart in PaymentOptions element are the defined payment methods. One of the possible
options might be TransactionGuaranteePaymentMethod=CreditCard:

<PaymentMethods>
<TransactionPrePaymentMethod>NoPayment</TransactionPrePaymentMethod>
<TransactionFinalPaymentMethod>NoPayment</TransactionFinalPaymentMethod>
<TransactionGuaranteePaymentMethod>CreditCard</TransactionGuaranteePaymentMethod>
</PaymentMethods>

In this case, the booking must not be saved directly but a credit card must be entered by the guest. Value of
Amount is 100 (1 Euro), which means 100 cent or 100 of the smallest available unit of currency. ELV (deutsches
elektonisches Lastschriftverfahren) is a German specific way to pay with providing bank account details is not
used for guarantee, only for payment.

Booking Process 194 of 241


DESKLINE 3.0 STANDARD INTERFACE

If Credit Card Payment is required the TransactionPrePaymentMethod in shopping cart is CreditCard

<PaymentMethods>
<TransactionPrePaymentMethod>CreditCard</TransactionPrePaymentMethod>
<TransactionFinalPaymentMethod>NoPayment</TransactionFinalPaymentMethod>
<TransactionGuaranteePaymentMethod>NoPayment</TransactionGuaranteePaymentMethod>
</PaymentMethods>
Or

<PaymentMethods>
<TransactionPrePaymentMethod>CreditCard</TransactionPrePaymentMethod>
<TransactionFinalPaymentMethod>Invoice</TransactionFinalPaymentMethod>
<TransactionGuaranteePaymentMethod>NoPayment</TransactionGuaranteePaymentMethod>
</PaymentMethods>

If ELV Payment is required the TransactionPrePaymentMethod in shopping cart is ELV

<PaymentMethods>
<TransactionPrePaymentMethod>ELV</TransactionPrePaymentMethod>
<TransactionFinalPaymentMethod>NoPayment</TransactionFinalPaymentMethod>
<TransactionGuaranteePaymentMethod>NoPayment</TransactionGuaranteePaymentMethod>
</PaymentMethods>
Or

<PaymentMethods>
<TransactionPrePaymentMethod>ELV</TransactionPrePaymentMethod>
<TransactionFinalPaymentMethod>Invoice</TransactionFinalPaymentMethod>
<TransactionGuaranteePaymentMethod>NoPayment</TransactionGuaranteePaymentMethod>
</PaymentMethods>

If Sofortueberweisung Payment is required the TransactionPrePaymentMethod in shopping cart is


Sofortueberweisung

<PaymentMethods>
<TransactionPrePaymentMethod>Sofortueberweisung</TransactionPrePaymentMethod>
<TransactionFinalPaymentMethod>NoPayment</TransactionFinalPaymentMethod>
<TransactionGuaranteePaymentMethod>NoPayment</TransactionGuaranteePaymentMethod>
</PaymentMethods>
Or

<PaymentMethods>
<TransactionPrePaymentMethod>Sofortueberweisung</TransactionPrePaymentMethod>
<TransactionFinalPaymentMethod>Invoice</TransactionFinalPaymentMethod>
<TransactionGuaranteePaymentMethod>NoPayment</TransactionGuaranteePaymentMethod>
</PaymentMethods>

If iDeal Payment is required the TransactionPrePaymentMethod in shopping cart is iDeal

<PaymentMethods>
<TransactionPrePaymentMethod>iDeal</TransactionPrePaymentMethod>
<TransactionFinalPaymentMethod>NoPayment</TransactionFinalPaymentMethod>
<TransactionGuaranteePaymentMethod>NoPayment</TransactionGuaranteePaymentMethod>
</PaymentMethods>
Or

<PaymentMethods>
<TransactionPrePaymentMethod>iDeal</TransactionPrePaymentMethod>
<TransactionFinalPaymentMethod>Invoice</TransactionFinalPaymentMethod>
<TransactionGuaranteePaymentMethod>NoPayment</TransactionGuaranteePaymentMethod>
</PaymentMethods>

Booking Process 195 of 241


DESKLINE 3.0 STANDARD INTERFACE

In these cases, the booking must not be saved directly but a credit card or bank account must be entered by
the guest. Value of Amount is AmountOrganisationPrePayment in cents or smallest available unit of the
currency!!!

!!! After 01.01.2016 it’s no longer possible to use the HiddenMode to send the data to
Datatrans!!!

METHODES FOR DATATRANS PAYMENT

For the payment to Datatrans there are different methods which can be used. We suggest to use the redirect
or the lightbox mode. Under following URL we provide a Test Page, on which you can make payment tests on
Live and Test environment.

http://interfaces.deskline.net/payment/getData.htm

Important: All parameter names and values for Datatrans are case specific!

A more detailed documentation of the Datatrans parameters can be found here:


http://pilot.datatrans.biz/showcase/doc/Technical_Implementation_Guide.pdf

In chapter 7.4 of this documentation is a list of possible test credit cards for the test environment. Those cards
cannot be used on the live environment.

R EDIRECT M ODE

When using the RedirectMode the merchant performs a redirect (with all the needed parameters) to the Data-
trans payment page. The whole payment process is handled by the Datatrans web application

Explanation:

Parameters Description
URL The URL from Datatrans where the data has to be sent to:
Test: https://pilot.datatrans.biz/upp/jsp/upStartIso.jsp
Live: https://payment.datatrans.biz/upp/jsp/upStart.jsp
theme standard theme DT2015
paymentmethod Credit card or payment type based on Datatrans documentation:
http://pilot.datatrans.biz/showcase/doc/Technical_Implementation_Guide.pdf

For example:
VIS VISA
ECA Mastercard
ELV Deutsches Elektronisches Lastschrift Verfahren
DIB Sofortueberweisung
DEA iDeal

amount As long as it’s about guarantee this value must always be “100”. If it is a
payment it is the AmountOrganisationPrePayment converted to cents or
smallest available unit of the currency!!!
Booking Process 196 of 241
DESKLINE 3.0 STANDARD INTERFACE

merchantId Value from GetOrganisationInformation function. (E.g.: <MerchantID


Type="Datatrans">1000011667</MerchantID>)

Careful: on the test environment the MerchantID must be used, even if


GetOrganisationInformation returns a different number sometimes.
Sign Value from GetOrganisationInformation function (E.g.: <MerchantID
Type="Datatrans"
sign=”34432524434325432532432”>1000011667</MerchantID>)

When you get empty sign from GetOrganisationInformation function then the
customer has not generated this value for his datatrans merchant, in this case
you don’t have to send this parameter to datatrans when you confirm.
useAlias Required to be set to yes. If send Datatrans redirects also an alias of the credit
card, with this information the service provider can get credit card information
in case of noshow
reqtype Always “NOA”!
uppCCValidationOnly Parameter to hide price to the guest. Recommended in case of guarantee only,
we suggest to us it any time.
language 2 char language code.
notificationTarget Always “interface”!
linkkey Optional, see chapter “Commit a booking” for details.
loadingimage While Datatrans checks the credit card a new site is displayed inside the browser
(Deskline 3.0 Standard Interface Payment Status Page) but usually this happens
so fast, that the visitor will not see this page. However, just in case, a loading
icon can be displayed and can be provided in form of this parameter.
loadingtext While Datatrans checks the credit card a new site is displayed inside the browser
(Deskline 3.0 Standard Interface Payment Status Page) but usually this happens
so fast, that the visitor will not see this page. However, just in case, a loading
text can be displayed (under the icon) and can be provided in form of this
parameter.
WebsiteURL The target URL of the website/portal that displayed the payment form in the
first place. This is where we will redirect all parameters and values that we got
from datatrans either with a success status or with an error message!
successUrl !Important: fixed values, do not change!
errorUrl Test: http://interfacetest.deskline.net/DSI/Payment/StatusPage.aspx
cancelUrl Live: https://interface.deskline.net/DSI/Payment/StatusPage.aspx
currency 3 letter currency code (EUR, CHF, …) Always take the settler currency!!!
refno Reference number to the credit card. A value returned inside the shopping cart
XML. Based on this value the customer (tourism destination) will be able to login
to Datatrans and get the credit card number in case it is needed.
desklineuserid ID of the user that must be created before committing the booking.
shoppingcart ID of the shopping cart.
securevalue This value is returned inside the shopping cart xml and is used for additional
checks about data consistency.
uppStartTarget “_top” if return URLs should be opened full screen. This is necessary for
organisations which use ACS which not allow to open 3d-secure in lightbox. We
suggest to use this Parameter any way.

Datatrans Showcase:

https://www.datatrans.ch/showcase/authorisation/redirect

Booking Process 197 of 241


DESKLINE 3.0 STANDARD INTERFACE

Example:

<a href="https://pilot.datatrans.biz/upp/jsp/upStart.jsp
?theme=DT2015
<!—how the datatrans webapplication should look-->

&paymentmethod=ECA
&paymentmethod=VIS
<!—PaymentMethod for Creditcard-->

&paymentmethod=ELV
<!—PaymentMethod for ELV-->

&paymentmethod=DIB
<!—PaymentMethod for Sofortueberweisung-->

&paymentmethod=DEA
<!—PaymentMethod for iDeal-->

&amount=100
<!-- as long as it's only for guarantee, use value 100 (=1 Euro), means 100 cent or 100 of the smallest
available unit of the currency -->
<!-- if it is payment, use the value AmountOrganisationPrePayment and convert to cents or smallest
available unit of the currency!!!-->

&useAlias=yes
<!-- to get back alias of credit card in case of noshow. required. -->

&merchantId=1000011667
<!-- different per destination/settler, value from GetOrganisationInformation-function -->

&sign=160915142721899093
<!-- different per destination/settler, value from GetOrganisationInformation-function -->

&reqtype=NOA
<!-- required for datatrans! fixed value! -->

&uppCCValidationOnly=yes
<!—Parameter to hide price to guest! Usefull for creditcard guarantee, we suggest to use it anytime -->

&language=en
<!-- language code -->

&notificationTarget=interface
&successUrl=https://interfacetest.deskline.net/DSI/Payment/StatusPage.aspx
&errorUrl=https://interfacetest.deskline.net/DSI/Payment/StatusPage.aspx
&cancelUrl=https://interfacetest.deskline.net/DSI/Payment/StatusPage.aspx
<!-- important, fixed value, do not change! -->
<!-- important: different per environment (test/live)! -->

&linkkey=test
<!-- optional LinkKey, see booking commit for explanation -->

&loadingimage=http://interfacetest.deskline.net/Pages/DSI/DT_Payment/loading.gif
&loadingtext=hold on a second, saving the booking.
<!-- optional image-url and text to be displayed on the intermediate status page (almost never shown) –
>

Booking Process 198 of 241


DESKLINE 3.0 STANDARD INTERFACE

&WebsiteURL=http://interfacetest.deskline.net/Pages/DSI/RequestHandlerPage.aspx
<!-- destination-URL of the website where we redirect in any case (error/success) with all the parameters
and values -->

&currency=EUR
<!-- 3 letter currency code always use settler currency not guest currency -->

&refno=TOSC43522
<!-- returned in shopping cart xml -->

&desklineuserid=41943986-536D-43B9-A4FE-F901E4677947
<!-- desklineuser id, required -->

&shoppingcart=e1bd7f54-0216-41a7-ab4e-2b96a6261955
<!-- shopping cart id, required -->

&securevalue=a0573a586bc1834b79846912ef2cf208
<!-- secure value, from interface shopping cart, required. -->

&uppStartTarget=_top
<!—optional paramter. Used for open 3d-secure page in new page -->

">START</a>

L IGHTBOX MODE

The Lightbox approach uses an iframe to embed the payment pages as an overlay to your online shop. When
the Lightbox Mode is invoked the merchant’s online shop is darkened out and the payment page appears as a
floating element on top.

Explanation:

Parameters Description
script src The script URL from Datatrans:
Test: https://pilot.datatrans.biz/upp/payment/js/datatrans-1.0.2.js
Live: https://payment.datatrans.biz/upp/payment/js/datatrans-1.0.2.js
id set to paymentForm
data-amount As long as it’s about guarantee this value must always be “100”. If it is a
payment it is the AmountOrganisationPrePayment converted to cents or
smallest available unit of the currency!!!
data-merchant-id Value from GetOrganisationInformation function. (E.g.: <MerchantID
Type="Datatrans">1000011667</MerchantID>)

Careful: on the test environment the MerchantID must be used, even if


GetOrganisationInformation returns a different number sometimes.
data-sign Value from GetOrganisationInformation function (E.g.: <MerchantID
Type="Datatrans"
sign=”34432524434325432532432”>1000011667</MerchantID>)

When you get empty sign from GetOrganisationInformation function then the
customer has not generated this value for his datatrans merchant, in this case
you don’t have to send this parameter to datatrans when you confirm.

Booking Process 199 of 241


DESKLINE 3.0 STANDARD INTERFACE

data-use-alias Required to be set to true. If send Datatrans redirects also an alias of the credit
card, with this information the service provider can get credit card information
in case of noshow
data-reqtype Always “NOA”!
data-upp-c-c-validation- Parameter to hide price to the guest. Recommended in case of guarantee only,
only we suggest to us it any time.
data-language 2 char language code.
data-notification-target Always “interface”!
data-success-url !Important: fixed values, do not change!
data-error-url Test: http://interfacetest.deskline.net/DSI/Payment/StatusPage.aspx
data-cancel-url Live: https://interface.deskline.net/DSI/Payment/StatusPage.aspx
data-linkkey Optional, see chapter “Commit a booking” for details.
data-loadingimage While Datatrans checks the credit card a new site is displayed inside the browser
(Deskline 3.0 Standard Interface Payment Status Page) but usually this happens
so fast, that the visitor will not see this page. However, just in case, a loading
icon can be displayed and can be provided in form of this parameter.
data-loadingtext While Datatrans checks the credit card a new site is displayed inside the browser
(Deskline 3.0 Standard Interface Payment Status Page) but usually this happens
so fast, that the visitor will not see this page. However, just in case, a loading
text can be displayed (under the icon) and can be provided in form of this
parameter.
data-websiteurl The target URL of the website/portal that displayed the payment form in the
first place. This is where we will redirect all parameters and values that we got
from datatrans either with a success status or with an error message!
data-paymentmethod Credit card or payment type based on Datatrans documentation:
http://pilot.datatrans.biz/showcase/doc/Technical_Implementation_Guide.pdf

For example:
VIS,ECA for credit cardVISA
ELV Deutsches Elektronisches Lastschrift Verfahren
DIB Sofortueberweisung
DEA iDeal

data-currency 3 letter currency code (EUR, CHF, …) Always take the settler currency!!!
data-refno Reference number to the credit card. A value returned inside the shopping cart
XML. Based on this value the customer (tourism destination) will be able to login
to Datatrans and get the credit card number in case it is needed.
data-desklineuserid ID of the user that must be created before committing the booking.
data-shoppingcart ID of the shopping cart.
data-securevalue This value is returned inside the shopping cart xml and is used for additional
checks about data consistency.
data-theme- how the datatrans webapplication should look
configuration e.g. "{'brandColor': '#76A741','textColor': 'white','brandButton': 'true',
'logoType':'none'}"
data-upp-start-target “_top” if return URLs should be opened full screen. This is necessary for
organisations which use ACS which not allow to open 3d-secure in lightbox. We
suggest to use this Parameter any way.
script type <script type="text/javascript">
$("#paymentButton").click(function () {
Datatrans.startPayment({'form': '#paymentForm'}); });
</script>

Booking Process 200 of 241


DESKLINE 3.0 STANDARD INTERFACE

Datatrans Showcase:

https://www.datatrans.ch/showcase/authorisation/lightbox-mode

Example:

<script src="https://code.jquery.com/jquery-1.11.2.min.js"></script>
<script src="https://pilot.datatrans.biz/upp/payment/js/datatrans-1.0.2.js"></script>

<form
id="paymentForm"

data-amount="100"
<!-- as long as it's only for guarantee, use value 100 (=1 Euro), means 100 cent or 100 of the smallest
available unit of the currency -->
<!-- if it is payment, use the value AmountOrganisationPrePayment and convert to cents or smallest
available unit of the currency!!!-->

data-use-alias="true"
<!-- to get back alias of credit card in case of noshow. required. -->

data-merchant-id="1000011667"
<!-- different per destination/settler, value from GetOrganisationInformation-function -->

data-sign="1000011667"
<!-- different per destination/settler, value from GetOrganisationInformation-function -->

data-reqtype="NOA"
<!-- required for datatrans! fixed value! -->

data-upp-c-c-validation-only="yes"
<!—Parameter to hidde price to guest! Usefull for creditcard guarantee, we suggest to use it for all
request -->

data-language="en"
<!-- language code -->

data-notification-target="interface"
data-cancel-url="https://interfacetest.deskline.net/DSI/Payment/StatusPage.aspx"
data-error-url="https://interfacetest.deskline.net/DSI/Payment/StatusPage.aspx"
data-success-url="https://interfacetest.deskline.net/DSI/Payment/StatusPage.aspx"
<!-- important, fixed value, do not change! -->
<!-- important: different per environment (test/live)! -->

data-linkkey="test"
<!-- optional LinkKey, see booking commit for explanation -->

data-
loadingimage="http://interfacetest.deskline.net/Pages/DSI/DT_Payment/loading.gif"
data-loadingtext="hold on a second, saving the booking."
<!-- optional image-url and text to be displayed on the intermediate status page (almost never shown) –
>

data-
websiteurl="http://interfacetest.deskline.net/Pages/DSI/RequestHandlerPage.aspx"
<!-- destination-URL of the website where we redirect in any case (error/success) with all the parameters
and values -->

data-paymentmethod="ECA,VIS"
<!—PaymentMethod for Creditcard-->

Booking Process 201 of 241


DESKLINE 3.0 STANDARD INTERFACE

data-paymentmethod="ELV"
<!—PaymentMethod for ELV-->

data-paymentmethod="DIB"
<!—PaymentMethod for Sofortueberweisung-->

data-paymentmethod="DEA"
<!—PaymentMethod for iDeal-->

data-currency="EUR"
<!-- 3 letter currency code always use settler currency not guest currency -->

data-refno="TOSC43532"
<!-- returned in shopping cart xml -->

data-desklineuserid="41943986-536D-43B9-A4FE-F901E4677947"
<!-- desklineuser id, required -->

data-shoppingcart="35ac9bc7-7186-4104-90fe-e789f0c07d8c"
<!-- shopping cart id, required -->

data-securevalue="b712dea9e0e3dbd0beb680f53a75fe90"
<!-- secure value, from interface shopping cart. required. -->

data-upp-start-target="_top"
<!—optional paramter. Used for open 3d-secure page in new page -->

data-theme-configuration="{'brandColor': '#76A741','textColor':
'white','brandButton': 'true', 'logoType':'none'}"
>
<!—how the datatrans webapplication should look-->

<button id="paymentButton">Test</button>
</form>

<script type="text/javascript">
$("#paymentButton").click(function () { Datatrans.startPayment({'form':
'#paymentForm'}); });
</script>

What happens after the values are posted to Datatrans?

While Datatrans checks the payment data a new site is displayed inside the browser (Deskline 3.0 Standard
Interface Payment Status Page) but usually this happens so fast, that the visitor will not see this page. Just in
case though there are two parameters that can be used to display a waiting message (LoadingImage,
LoadingText) to the guest. As soon as Datatrans returns a status (success/error/cancel) we either commit the
booking (in case of the success message) or just redirect to the WebsiteURL parameter with the error message.

These parameters are forwarded to the WebsiteURL link, they also include all parameters sent from the
originating website and from Datatrans and can be extended with parameters and values from Deskline:

Parameter Name Description


acqAuthorizationCode From Datatrans
amount Amount checked, see above, in case of guarantee this will always be “1” else it is the
amount which has to be prepaid to the organization n cents or smallest available
unit of currency

Booking Process 202 of 241


DESKLINE 3.0 STANDARD INTERFACE

authorizationCode From Datatrans


BookingNumber Booking Number in Deskline 3.0 if the booking was successfully committed
currency 3 letter currency code
Expm Expiry month (Format: MM)
Expy Expiry year (Format: YY)
language Language code
linkkey LinkKey used to commit the booking.
mode e.g. lightbox
loadingimage Original LoadingImage URL that was sent from the portal/website.
loadingtext Original LoadingText value that was sent from the portal/website.
merchantid merchantId used
sign Sign used
notificationtarget Always “interface”
pmethod Value from “paymentmethod” parameter (type of credit card, sofortueberweisung,
iDeal or ELV).
Refno Original value from Refno
reqtype Always “NOA”!
responseCode From Datatrans
responseMessage From Datatrans
errorMessage From Datatrans when status = “error”
errorCode From Datatrans, error code.
errorDetail From Datatrans, more information about the error.
acqAuthorizationCode From Datatrans
securevalue Original value from SecureValue
shoppingcart Original value from ShoppingCart
status success / cancel / error – from Datatrans. If this is “success” we commit the booking.
testOnly From Datatrans
TransactionID Transaction (Booking) ID in Deskline 3.0 if the booking was successfully committed
uppMsgType From Datatrans
uppTransactionId From Datatrans
userId |desklineuserid Deskline 3.0 User Id
websiteuRL Original value from WebsiteURL
DSIErrorMessage In case of errors during the committing of the booking the booking number will be 0
and the DSIErrorMessage will have a descriptive text.
usealias Yes, if value was yes in the payment request (required to be set to yes), no, if it was
no. Parameter not in rediredt information if parameter not send to Datatrans at all
maskedCC Masked credit card number e.g. 490000xxxxxx0003. Only in redirect if useAlias was
set to yes
aliasCC Alias of the credit card, important in case of noshow. Only in redirect if useAlias was
set to yes
bankaccount In case of ELV payment bank account number is in the redirect.
bankrouting In case of ELV bank routing is in the redirect.

What happens after a successful payment to Datatrans, but saving of transaction in Deskline fails?

Booking Process 203 of 241


DESKLINE 3.0 STANDARD INTERFACE

After forwarding the credit card or bank account data to Datatrans, Datatrans returns a status. If the status is
success, the reservation will be committed. It is possible that the commitment of the reservation fails (no
availabilities, parameters not proper (no guestid) or something else). All payments done via credit card,
Sofortueberweisung, iDeal or ELV to Datatrans, will not automatically charge the credit card/bank account. First
only the check is done, that it would be possible to charge the card with the amount send. When the
transaction is successfully committed in Deskline, Deskline changes the Datatrans authorization into a real
payment. So if transaction fails in Deskline, the credit card/bank account will not be charged with the
forwarded amount.

Recommendation:

During developing/testing we found it very useful to use a very simple page as the destination URL (parameter
WebsiteURL). This page displayed all the names and values of parameters that were sent to it:

This is helpful when you start debugging what kind of values you receive in order to display the appropriate
message to the guest.

Booking Process 204 of 241


DESKLINE 3.0 STANDARD INTERFACE

C HECK STATUS OF SHOPPING CART


Check a shopping cart if it is already commited or not. This is method to know the status of a shopping cart if
anything happens on internet connection or in case of credit card guarantee, credit card, sofortueberweisung,
iDeal or ELV payment and the redirect of Datatrans may not be catched.

Request
More
Can be
Request field Description empty?*
than one
possible?

Originator The code of the point of sale requesting the data.


Provided by feratel.
Company The code of the company requesting the data.
Provided by feratel.
CheckShoppingCartStatus Id Id of the shopping cart to check.

<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://interface.deskline.net/DSI/XSD">
<Request Company="xxx" Originator="FERATEL" Language="en">
<CheckShoppingCartStatus Id="a98f83d9-f87e-41e0-b730-c52beb23a7fd" />
</Request>
</FeratelDsiRQ>

Response
More than
Can be
Response field Description empty?*
one
possible?

ShoppingCartStatus Element which includes the requested status data


Id Id of the shopping cart which was checked (provided in
the request)
Status Status information for the shopping cart, three different
status possible:

Committed: Shopping cart is already committed, so


booking was successful and according TransaktionID is
present in the response
Uncommitted: Shopping cart is not yet committed and
TransaktionID is zero GUID. Shopping cart can still be
committed because it is not yet expired (a shopping cart
expires after 2 hours)
Expired: Shopping cart was not committed and
TransaktionID is zero GUID. Shopping cart can no longer
be committed because it is expired (a shopping cart
expires after 2 hours)
TransactionID Transaction id according to the shopping cart if it was
committees. If Status is Uncommitted or Expired
TransactionID is zero GUID

Booking Process 205 of 241


DESKLINE 3.0 STANDARD INTERFACE

Example

<?xml version="1.0" encoding="UTF-8"?>


<FeratelDsiRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" Status="0" Message="OK"
xmlns="http://interface.deskline.net/DSI/XSD">
<Result Index="1">
<ShoppingCartStatus Id="7D9979B2-2FDF-4A5B-806F-DBEC32D747E6" Status="Committed"
TransactionID="574f9864-abe4-4486-8efe-07f4e22801ba" />
</Result>
</FeratelDsiRS>

READING A BOOKING
It is also possible to read an existing booking based on the transaction ID and the guest ID. The booking number
can’t be used since bookings from a global POS can be stored on more than one database and therefore are not
unique.

Request
More than
Can be
Request field Description empty?*
one
possible?

Originator The code of the point of sale requesting the data. Provided by
feratel.
Company The code of the company requesting the data. Provided by
feratel.
ShowBooking Tag used to read a booking.
Id ID of the previously saved booking (not shopping cart ID).
UserId The ID of the user connected with this transaction.
IncludePriceDetails Optional setting to get more price information for better
settlement if set to true. Default setting is false.
IncludePaymentDetails Optional setting to get more information about payment for
creating own booking confirmation. Default setting is false
IncludeCancellationDetails Optional setting to get more information about cancellation
rules of the booked accommodations

<?xml version="1.0" encoding="utf-8"?>


<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://interface.deskline.net/DSI/XSD">
<Request Company="FERATEL" Originator="FERATEL" Language="en">
<ShowBooking Id="D48A6886-7871-4C4A-BE3C-F4E7738E917A" UserId="B74E43F6-
1D03-40BF-85F4-7E02325AAAA6" IncludePriceDetails="true" IncludePaymentDetails="true"
IncludeCancellationDetails="true" />
</Request>
</FeratelDsiRQ>

Response:

See chapter “Commit”.

Booking Process 206 of 241


DESKLINE 3.0 STANDARD INTERFACE

READING A TRANSACTION/BOOKING LIST


It is possible to read out all existing bookings based on Originator and SalesChannelId. Reading out bookings is
restricted to a time period defined in the request.

Request
More than
Can be
Request field Description empty?*
one
possible?

Originator The code of the point of sale requesting the data. Provided by
feratel.
Company The code of the company requesting the data. Provided by
feratel.
ReadTransactions Tag used to read a transaction list.
SalesChannelId The same Sales Channel ID that is used when performing a
search and/or a booking.
DateType DateType can be CreateDate or LastChangeDate. And defines
the use of the period set in From and To.
From Defines the date from which on the transactions should be
listed
To Defines the date to which the transactions should be listed
Note: This is very performance intensive request, so please do
not call huge periods, restrict your calls e.g. to one month
Type Optional filter if only Reservations or Cancellations should be
listed. Type can be ‘Reservation’, ‘Cancellation’ and ‘All’. Is All
per default
DbCode Optional filter if transactions of a specific database should be
listed.
SettlerCode Optional filter if transactions of a specific guest settler should
be listed.
IncludePriceDetails Optional setting to get more price information for better
settlement if set to true. Default setting is false.
IncludePaymentDetails Optional setting to get more information about payment for
creating own booking confirmation. Default setting is false
IncludeCancellationDetails Optional setting to get more information about cancellation
rules of the

Request example:

<?xml version="1.0" encoding="utf-8"?>


<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://interface.deskline.net/DSI/XSD">
<Request Company="FERATEL" Originator="FERATEL" Language="en">
<ReadTransactions SalesChannelId="BB556229-E7B1-4F21-9C6A-2BEA7120BF5A" DateType="CreateDate"
From="2013-01-31" To="2013-02-01" IncludePriceDetails="true" IncludePaymentDetails="true"
IncludeCancellationDetails="true" />
</Request>
</FeratelDsiRQ>

Booking Process 207 of 241


DESKLINE 3.0 STANDARD INTERFACE

Response:
More
Can be
Response field Description empty?*
than one
possible?

Transaction
Id Internal transaction id
CreateDateTime Date and Time when the transaction was created
LastChangeDateTime Date and Time when the transaction was changed the last
time
SettlerCode Code of the guest settler responsible for handling the
booking.
Number Booking confirmation number written on the guest
confirmation
Type Reservation, Cancellation or BookOnRequest (in case of
BookOnRequest also attribute ValidUntil is shown,
successful booking requests turn into Reservation)
SalesChannelId Sales Channel that was used for the search and for adding
items.
CurrencyCode Currency of the booking (settler currency) and all prices
listed in the shopping cart are in this currency
CurrencyFactor Element GuestCurrency shows the requested Currency of
the shopping cart and the factor provided can be used to
display the result in the guest currency to the guest. The
prices should be divided by the factor to get the right
result in guest currency.
ToscLinkKey LinkKey of Link with which the booking was done, if
booking was done via interface LinkKey is automatically set
to Code of Originator. LinkKey can also be defined
individually when a booking is done.
BookingOptions Details about the payment calculation.
BasketCalculation
BasketSummary
CancellationInsurance Amount If cancellation insurance was used, the amount is returned
here.
CancellationInsurance VATAmount, 0 if included.
VATAmount
BookingFee Amount If a booking fee must be paid, the amount is returned here.
BookingFee VATAmount VATAmount, 0 if included.
PrePayment Amount Amount for the pre-payment necessary for the booking.
PrePayment VAT VATAmount, 0 if included.
PrePayment DueDate Due-date for pre-payment.
FinalPayment Amount Amount for the final payment necessary for the booking.
FinalPayment VAT VATAmount, 0 if included.
FinalPayment DueDate Due-date for final payment.
SPPayment Amount Total amount of service-provider items.
TotalPayment Amount Total booking amount.
TotalPayment VAT VATAmount, 0 if included.
Details Details of the items inside the booking
Weight Weight is used for items like brochures.
GroupNumber Items of the same service provider are inside of one group
with same number.

Booking Process 208 of 241


DESKLINE 3.0 STANDARD INTERFACE

Important: Items of one package are inside one group


number, the summarizing item is of type Package and the
others are presented in their own Detail element with
same group number but with their own type.
Type Type of the product (Accommodation/AdditionalService).
Order Order inside the booking.
DateFrom Day of arrival.
DateTo Day of departure.
TimeFrom Start time, will be of use for additional services.
TimeTo End time, will be of use for additional services.
UnitNumber Number of units
AdultNumber Number of adults
ChildrenNumber Number of children
ChildrenAges Ages of children
ServiceProviderId Service Provider ID
ServiceProviderName Service Provider Name
ServiceId Service ID
ProductId Product ID
ProductName Product Name
Price Total price for this item.
MealType Meal type included
VatAmount VATAmount, 0 if included.
PaymentType Enumeration: ServiceProviderPayment,
OrganisationPayment, SplitPayment
PriceDetails Only included if IncludePriceDetails in Request was set to
true
MealCode Same information as in MealType above
TotalPrice Total price for this item
TotalAdultPrice Total adult price for this item.
TotalAdultMeal Total price of meals for adults for this item.
TotalAdultVT Total amount of visitor tax for adults for this item.
TotalChildrenPrice Total price for children for this item.
TotalChildrenMeal Total price for meals for children.
TotalChildrenVT Total amount of visitor tax for children for this item.
TotalBedlinen Total amount for bed linen for this item.
TotalFinalCleaning Total amount for final cleaning for this item.
TotalExtras Total amount of all additional extras (except bedlinen and
final cleaning) listed in extras including special discounts
and surcharges.
PayNights Amount of nights that have to be paid; can be different
from the length of the stay (“stay 7 pay 6” calculations for
example).
Guest The element for the guest address connected to the
reservation.
Id Id of the guest address (that is used to commit a booking
or return a guest address)
Company Company name from the guest address
LastName Last name from the guest address

Booking Process 209 of 241


DESKLINE 3.0 STANDARD INTERFACE

LastName Last name from the guest address


SalutationId Salutation ID (see KeyValues Salutations)
Title Salutation string
Salutation Generated string based on salutation ID and name
Birthday Date of birth from the guest address
Address Address line 1
AltAddress Address line 2
Phone Phone number from the guest address
Fax Fax number from the guest address
Mobile Mobile phone number from the guest address
Email Email from the guest address
Country Country code (see KeyValues GuestCountries)
ZipCode Zip code from the guest address
City City from the guest address
Language Language assigned to the guest
Reusable Does the guest want to receive the newsletter of the
destination / Does the guest allow that his contact data is
used for marketing purposes by the destination?
CancellationInformation Only included if IncludeCancellationDetails in Request was
set to true
FreeCancellation Enumeration true/false. If true means at the moment free
cancellation but there is might a due date
DateUntil Date until when cancellation is free, if there is no settings
because cancellation is not free at all, Date is system
neutral date "1980-01-01"
TimeUntil Time until when cancellation is free corresponding to
DateUntil
CalculationBase In case of 0 the base for cancellation fees is the whole stay.
If >0 the amount of first days as base for cancellation fee.
E.g. cancellation fee is 10% of whole stay or 50% of the
first 2 days.
Percentage Percentage value for cancellation fee.
Amount Calculated amount of cancellation fee after due date.
CurrencyCode International 3 character currency code
PaymentDetails Only included if IncludePaymentDetails in Request was set
to true
@TransactionGuaranteePaymentMethod Shows the guarantee type of the payment
PrePayment Shows details about the prepayment setting of one
accommodation
@Amount Amount of prepayment
@DueDate DueDate of prepayment
@Recipient Information about to which person or organization the
payment belongs
FinalPayment Shows details aobut the final payment setting of one
accommodation
@Amount Amount of final payment
@DueDate DueDate of final payment
@Recipient Information about to which person or organization the
payment belongs

Booking Process 210 of 241


DESKLINE 3.0 STANDARD INTERFACE

C ANCELING A BOOKING
It is also possible to make a full cancellation for a booking, but based on the parameters and settings,
cancellations are not possible under all conditions. For example a data owner can also prohibit a point of sale
to cancel bookings.

Request
More than
Can be
Request field Description empty?*
one
possible?

Originator The code of the point of sale requesting the data. Provided by
feratel.
Company The code of the company requesting the data. Provided by
feratel.
CancelBooking Tag used to cancel a booking.
Id ID of the previously saved booking (not shopping cart ID).
UserId The ID of the user connected with this transaction.

<?xml version="1.0" encoding="utf-8"?>


<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://interface.deskline.net/DSI/XSD">
<Request Company="FERATEL" Originator="FERATEL" Language="en">
<CancelBooking Id="D48A6886-7871-4C4A-BE3C-F4E7738E917A" UserId="B74E43F6-
1D03-40BF-85F4-7E02325AAAA6" />
</Request>
</FeratelDsiRQ>

Response:

<?xml version="1.0"?>
<FeratelDsiRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" Status="0" Message="OK"
xmlns="http://interface.deskline.net/DSI/XSD">
<Result Index="1">
<CanceledBooking>
<Id>D48A6886-7871-4C4A-BE3C-F4E7738E917A</Id>
<Status>Canceled</Status>
</CanceledBooking>
</Result>
</FeratelDsiRS>

Booking Process 211 of 241


DESKLINE 3.0 STANDARD INTERFACE

G ET SETTLER INFORMATION
Sometimes it is necessary to display information about the organization that is managing the bookings (i.e. the
tourism destination), especially when it comes to payment processing. There is one call to the interface that,
based on the settler code inside a shopping cart, will return the settler information.

Request
More
Can be
Request field Description empty?*
than one
possible?

Originator The code of the point of sale requesting the data. Provided by
feratel.
Company The code of the company requesting the data. Provided by
feratel.
Language Language to be used when returning the information (GTC,
CancellationConditions, DataPrivacyText)
GetOrganisationInformation Tag used to get the settler information.
Code Code of the settler in question, as returned inside the
shopping cart.
ShowPaymentInformation Optional Parameter which can be true or false (default is
false). If true also the element PaymentInformation is in the
response. Important to know how bookings can be done. If
true SalesChannelId has to be provided as well
ShowInsuranceAndFeeInformation Optional Parameter which can be true or false (default is false)
to know the settings for cancellation insurance and booking
fee of a specific settler
SalesChannelId Guid of Sales Channel, which will be used for booking. If
ShowPaymentInformation is true, SalesChannelID is required!

<?xml version="1.0" encoding="utf-8"?>


<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://interface.deskline.net/DSI/XSD">
<Request Company="FERATEL" Originator="FERATEL" Language="en">
<GetOrganisationInformation Code="FERATEL" ShowPaymentInformation="true" SalesChannelId="BB556229-E7B1-4F21-9C6A-
2BEA7120BF5A" ShowInsuranceAndFeeInformation="true" />
</Request>
</FeratelDsiRQ>

Response:
More
Can be
Request field Description empty?*
than one
possible?

Name Name of the settler


Country Country code
Address Address line 1
AltAddress Address line 2
ZipCode Zip code
City City name
Phone Phone number
Fax Fax number
EMail E-Mail address
Url Homepage

Booking Process 212 of 241


DESKLINE 3.0 STANDARD INTERFACE

CreditCards Active credit card types for this settler


Merchant ID Merchant ID, used for credit card or bank account
authorization with Datatrans.
Merchant  @Type Right now the merchant ID is used only for the Type Datatrans.
Merchant  @Sign Sign value, used for credit card or bank account authorization
with Datatrans.
GTC General Trade Conditions for this settler in requested
language.
CancellationConditions Cancellation Conditions for this settler in requested language.
DataPrivacyText Data Privacy Text for this settler in requested language.
CancellationProtectionText Cancellation Protection Text for this settler in requested
language.
Currency Currency Code of the settling organization
PaymentInformation Only included in the response if requested
PossiblePaymentMethods Includes Information when and which payment method is
possible
InvoicePossibleDays The amount of days before arrival date until which the
payment with invoice is allowed
Invoice Can be true or false. Is true if payment via invoice is supported
CreditCard Can be true or false. Is true if payment via credit card is
supported
ELV Can be true or false. Is true if payment via bank account is
supported
Sofortueberweisung Can be true or false. Is true if payment via Sofortueberweisung
is supported
iDeal Can be true or false. Is true if payment via iDeal is supported
ServiceProviderPayment If active, payment to service provider is possible. If
GuaranteeRequested is true, there should be done a
guarantee (mostly with credit card, see chapter Credit Card
Guarantee with DataTrans)
Guarantee Type If a guarantee is requested there have to be at least one entry
of this kind. Type can only be CreditCard.
SplitPayment If active, split payment is possible. Means that part of the
amount has to be paid to the organization and other part to
service provider
OrganisationPayment If active, payment to organization is possible.
InsuranceAndFeeInformation Subelements provides information about Cancellation
insurance, booking and insurance fees
CancellationInsurances Cancellation insurance settings depend on the product type
CancellationInsurance booked. Attribute ProductType can be HotelRoom, Apartment,
Camping and Package. Same enumeration like in basic data for
products.
CancellationInsuranceDetail Cancellation insurance settings can be done for different
ranges of the total amount of bookings (AmountFrom and
AmountTo). Whether they are set as a fixed value or a
percentage value shown in attribute CalculationRule and Price
shows the height of the fee.
CancellationFees Cancellation fee settings can be done for different ranges of
CancellationFeeDetail the total amount of bookings (AmountFrom and AmountTo).
Whether they are set as a fixed value or a percentage value
shown in attribute CalculationRule and Price shows the height
of the fee. Cancellation fee also depends on the days before
arrival the cancellation takes place.

Booking Process 213 of 241


DESKLINE 3.0 STANDARD INTERFACE

BookingFees Booking fee settings can be done for different ranges of the
BookingFeeDetail total amount of bookings (AmountFrom and AmountTo).
Whether they are set as a fixed value or a percentage value
shown in attribute CalculationRule and Price shows the height
of the fee.

<?xml version="1.0" encoding="UTF-8"?>


<FeratelDsiRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
Status="0" Message="OK" xmlns="http://interface.deskline.net/DSI/XSD">
<Result Index="1">
<OrganisationInformation>
<ContactData>
<Name>Feratel Demo Destination</Name>
<Country>AT</Country>
<Address>Moritschstraße 2/IV</Address>
<AltAddress />
<ZipCode>9500</ZipCode>
<City>Villach</City>
<Phone>+43 4242 216565</Phone>
<Fax>0043424221656565</Fax>
<EMail>[email protected]</EMail>
<Url>http://www.feratel.com</Url>
</ContactData>
<CreditCards>
<CreditCard Id="9ecae3a0-87c0-463a-b3e0-d1c6412d3057">VI</CreditCard>
</CreditCards>
<MerchantID Type="Datatrans">1000011667</MerchantID>
<GTC>gtc text</GTC>
<CancellationConditions>cancellation conditions text</CancellationConditions>
<DataPrivacyText>privacy text</DataPrivacyText>
<VisitorTaxInformation>Kurbeitrag (Kurtaxe)</VisitorTaxInformation>
<CancellationProtectionText>
&lt;iframe style="border: 0px none; overflow: hidden; width: 543px; height: 1210px;" scrolling="no"
src="https://www.reiseversicherung.de/de/produktinformationen/produktbeschreibungen/201406/kf/de/tid-
storno.html"&gt;&lt;/iframe&gt;
</CancellationProtectionText>
<Currency>EUR</Currency>
<PaymentInformation>
<PossiblePaymentMethods InvoicePossibleDays="7" Invoice="true" CreditCard="true" ELV="false" />
<ServiceProviderPayment Active="true" GuaranteeRequested="true">
<Guarantee Type="CreditCard" />
</ServiceProviderPayment>
<SplitPayment Active="true" />
<OrganisationPayment Active="true" />
</PaymentInformation>
<InsuranceAndFeeInformation>
<CancellationInsurances>
<CancellationInsurance ProductType="HotelRoom">
<CancellationInsuranceDetail AmountFrom="0" AmountTo="50000" CalculationRule="Percentage" Price="15" />
</CancellationInsurance>
<CancellationInsurance ProductType="Apartment">
<CancellationInsuranceDetail AmountFrom="0" AmountTo="50000" CalculationRule="Percentage" Price="10" />
</CancellationInsurance>
<CancellationInsurance ProductType="Package">
<CancellationInsuranceDetail AmountFrom="0" AmountTo="50000" CalculationRule="Fixed" Price="7" />
</CancellationInsurance>
<CancellationInsurance ProductType="Camping">
<CancellationInsuranceDetail AmountFrom="0" AmountTo="50000" CalculationRule="Fixed" Price="5" />
</CancellationInsurance>
</CancellationInsurances>
<CancellationFees>
<CancellationFeeDetail AmountFrom="0" AmountTo="50000" CalculationRule="Percentage" Price="90" DaysUntilArrival="1"
/>
<CancellationFeeDetail AmountFrom="0" AmountTo="50000" CalculationRule="Percentage" Price="60"
DaysUntilArrival="10" />
<CancellationFeeDetail AmountFrom="0" AmountTo="50000" CalculationRule="Percentage" Price="20"

Booking Process 214 of 241


DESKLINE 3.0 STANDARD INTERFACE

DaysUntilArrival="50" />
</CancellationFees>
<BookingFees>
<BookingFeeDetail AmountFrom="0" AmountTo="99999999" CalculationRule="Fixed" Price="10" />
</BookingFees>
</InsuranceAndFeeInformation>
</OrganisationInformation>
</Result>
</FeratelDsiRS>

Booking Process 215 of 241


DESKLINE 3.0 STANDARD INTERFACE

SAVING REQUESTS
It is also possible to save a request instead of making a booking. There are three types of requests in Deskline
3.0:

 Offer Request: The guest will ask the tourist office to make an offer for the search parameters of the
guest. The tourist office will receive this request and can make a search in the back-office and will
send an offer to the guest.
The offer request can also be limited to one hotel or even one product only by the guest, making it a
specific request instead of a general one, in this case is it necessary that we get from you your
sessionid so we can calculate the conversion.
 Package Request: The guest will ask the tourist office to make an offer for the selected package with
the search parameters of the guest. The tourist office will receive this request and can make a search
in the back-office and will send an offer to the guest.
 Group Request: The guest has to enter Date From, Date To, Max Num of Adults, Max. Num of Children
as well as meal (if whised) and his address data. This data will be send as new transaction called group
request to our system. The tourist office will receive this request and can make a search in the back-
office and will send an offer to the guest.
 Request Pool: The guest will put a request to the request pool where the service providers will have
access to the request and then contact the guest directly or make an offer directly. Only service
providers that fulfill some customer-defined criteria will be able to see the request. (E.g. so that no
apartment house can see the request when the guest specifically asked for hotel rooms)

Saving requests is possible with the access rights for the booking interface and also require a guest address like
mentioned above.

To save a request, this is the XML definition:

Request

More than one


Request field Description Can be empty?*
possible?

Originator The code of the point of sale requesting the data. Provided
by feratel.
Company The code of the company requesting the data. Provided by
feratel.
Range Has to be TO or DI.
Item Id List all of the towns or districts that the guest activated in
the search form. It is mandatory to provide at least one
town-id. If the guest wants offers for one hotel only, use
the town-id of this service provider based on the basic data.
RequestDetails General information about the request
SessionID If you send us the offerrequest for one hotel you have also
to send us the session id, so we can save the click in a
correct way and make correct calculation of the conversion
Type Enumeration: OfferRequest, RequestPool, PackageRequest,
GroupRequest
UserId ID of the guest connected with this request
GuestToPOSComment The guest can add a comment to his request
LinkKey A linkkey can be send to have more possibilities in statistics

Saving Requests 216 of 241


DESKLINE 3.0 STANDARD INTERFACE

OfferRequestSettings Only used when the request type is OfferRequest


ServiceProvider Id ID of the service provider
Product Id ID of the product
PackageId Only used when the request type is PackageRequest. ID of
the package
RequestPoolSettings Only used when the request type is RequestPool
MaxTickets Define the upper limit how many service providers can
make an offer, e.g. 20, so only 20 service providers are
allowed to respond to this request.
ContactBy Method how the guest wants to be contacted by the service
providers. Enumeration: Email, Phone, Fax
SearchLines
SearchParameters Every SearchParameters element can have a different
occupancy and different facility requirements. Only one
element possible at the moment.
Index Search parameter index will be reflected in the response.
Once more than one SearchParameters element is possible
the index is necessary to relate response to request.
SalesChannel The GUID of the SalesChannel for the products. Assigned by
feratel.
Units Amount of required units (0 if unknown)
For GroupRequest the value should be fixed to 0 aswell.
Adults Amount of Adults (per unit)
From Date of arrival
To Date of departure
Nights Length of stay. It is possible to search for 3 nights in a 5 day
timeframe. In this case, one product may be in the
response more than once but with different possible arrival
dates.
Duration Only used when the request type is PackageRequest.
Duration for the selected Package
MultilineSearchCondition If there are two or three search lines the first and the
second search line has to include the attribute
MultilineSearchCondition which can be “Or”, “And” or
“None”. If it is none the next search lines will be ignored
ServiceProvider ID To search inside one service provider only, the Deskline 3.0
GUID can be provided in the request. Passing the ID to one
hotel will guarantee the best performance available.
ServiceProvider Code To search inside one service provider only, the Deskline
object code can be provided in the request. When passing a
code, still a search is done for the provided range because
it’s possible that the code is not unique. Slower than
passing the ID!
ServiceProvider Name To search inside one service provider only, the full name of
the service provider can be provided in the request. When
passing a name, still a search is done for the provided range
because it’s possible that the name is not unique. Slower
than passing the ID!
Note: ID/Code/Name is either/or: if an ID is provided, Code/Name will not be checked
and so on.
PreSelected- <PreSelectedServiceProviderIDs> can be used to search
ServiceProviderIDs inside more than one service provider based on the SP-ID.
This can also be used for targeted searches if more than
one hotel should be checked.
Saving Requests 217 of 241
DESKLINE 3.0 STANDARD INTERFACE

Service Container Element for service filters inside the service


provider element.
LastAvailability- Integer value for the number of days that the service
ChangeDays provider must have last changed the availabilities. For
example to make a search and only return the service
providers that last changed their availabilities within 7 days.
MinRooms Integer value for the number of rooms a service should
have at least.
MinSleepingRooms ="Mi Integer value for the number of sleeping rooms a service
should have at least.
MinRoomSize Integer value for the size of a service in square meter
should have at least.
ServiceFacility Information of required service facilities. All selected
facilities must match with the service. Refer to the list of
Key Values for the GUIDs.
ServiceClassification Information of required service classifications. All selected
classifications must match with the service. Refer to the list
of Key Values for the GUIDs.
Product Container Element for product filters inside the service
provider element.
Product ID To search inside one specific product, the Deskline 3.0
product GUID can be provided in the request in addition to
the service provider ID.
AccommodationType Enumeration of HotelRoom, Apartment, Camping
ProductType Enumeration of Accommodation, AdditionalService or
Package
SearchCode Searchcode of the product as given in the BasicData
response.
BasePriceOnly True/false, set to true to only get a base price for each
product returned or to false to get a calculated total price.
The total price calculation decreases performance so it
must not be used without using paging and it should not be
used during a wide area search, but rather for example in a
search for a single item.

The base price is the regular price for a bed as defined by


the service provider (per night / per unit / ...) and does not
include any calculations regarding meals, surcharges,
discounts, children prices etc. whatsoever. Only the total
price calculation will return the total price with all
calculations necessary.
HolidayThemes Used to query for holiday themes like “wedding”, “sports”,
and so on. Refer to the list of Key Values for the GUIDs.
Children Ages of children, comma separated if more than one child is
requested. Is regarded as per unit. This attribute is optional
if there are children in the request the Element must not be
send in the request
Meal Type of meal requested.
BookOnly Indicator if only bookable or all products should be found.
AccommodationFacility Information of required service provider facilities. All
selected facilities must match with the service provider.
Refer to the list of Key Values for the GUIDs.
Category Used to query only hotels or pensions for example. Refer to
the list of Key Values for the GUIDs.
Stars Used to query only 3-star hotels for example. Refer to the

Saving Requests 218 of 241


DESKLINE 3.0 STANDARD INTERFACE

list of Key Values for the GUIDs.


MarketingGroup Used to query service providers that are part of one of the
required marketing groups. Refer to the list of Key Values
for the GUIDs.
Chain Used to query service providers that are part of a specific
chain like Best Western. Refer to the list of Key Values for
the GUIDs
Classification Used to query for flowers or similar classification
information. Refer to the list of Key Values for the GUIDs.

Offer Request Example:

<?xml version="1.0"?>
<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://interface.deskline.net/DSI/XSD">
<Request Originator="FERATEL" Company="" Language="en">
<Range Code="TO">
<!-- all towns or district that should be valid for the request must be passed here, using range
region will not work, only TO/DI -->
<Item Id="3310C506-A478-4BE8-AF74-DF697C0738FB" />
</Range>

<RequestDetails>
<Type>OfferRequest|RequestPool</Type>
<UserId>86B9C1AA-3572-435D-9F3C-024C9F90B4C7</UserId>
<GuestToPOSComment>my dog is a doberman, but he is friendly when he is not
hungry.</GuestToPOSComment>

<!-- only used for type=offer requests: -->


<OfferRequestSettings>
<ServiceProvider Id="F7E27F9D-596F-4793-961C-BDB445776D2C">
<!-- optional -->
<Product Id="F7E27F9D-596F-4793-961C-BDB445776D2B" />
<!-- optional -->
</ServiceProvider>
</OfferRequestSettings>

</RequestDetails>

<SearchLines>
<SearchParameters Index="1" SalesChannel="BB556229-E7B1-4F21-9C6A-2BEA7120BF5A"
Units="2" Adults="2" From="2010-04-20" To="2010-04-25" Nights="5">
</SearchParameters>
</SearchLines>
</Request>
</FeratelDsiRQ>

Package Request Example:

<?xml version="1.0"?>
<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://interface.deskline.net/DSI/XSD">
<Request Originator="FERATEL" Company="SIMTEST" Language="en">
<Range Code="TO">
<Item Id="3310C506-A478-4BE8-AF74-DF697C0738FB" />
</Range>
<RequestDetails>
<Type>PackageRequest</Type>
<UserId>…</UserId>

Saving Requests 219 of 241


DESKLINE 3.0 STANDARD INTERFACE

<GuestToPOSComment>
my dog is a doberman, but he is friendly when he is not
hungry.
</GuestToPOSComment>
<PackageId>F7E27F9D-596F-4793-961C-BDB445776D2C</PackageId>
</RequestDetails>
<SearchLines>
<SearchParameters Index="1" SalesChannel="BB556229-E7B1-4F21-9C6A-2BEA7120BF5A"
Units="2" Adults="2" From="2016-04-20" To="2016-04-25" Duration="6">
</SearchParameters>
</SearchLines>
</Request>
</FeratelDsiRQ>

Group Request Example:

<?xml version="1.0"?>
<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://interface.deskline.net/DSI/XSD">
<Request Originator="FERATEL" Company="" Language="en">
<Range Code="TO">
<!-- all towns or district that should be valid for the request must be passed here, using range
region will not work, only TO/DI -->
<Item Id="3310C506-A478-4BE8-AF74-DF697C0738FB" />
</Range>
<RequestDetails>
<Type>GroupRequest</Type>
<UserId>41943986-536D-43B9-A4FE-F901E4677947</UserId>
<GuestToPOSComment>
my dog is a doberman, but he is friendly when he is not
hungry.
</GuestToPOSComment>
</RequestDetails>
<SearchLines>
<SearchParameters Index="1" SalesChannel="BB556229-E7B1-4F21-9C6A-2BEA7120BF5A" Adults="20" From="2017-07-20"
To="2017-07-25" Nights="5" Units="0">
</SearchParameters>
</SearchLines>
</Request>
</FeratelDsiRQ>

Request Pool Example:

<?xml version="1.0"?>
<FeratelDsiRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://interface.deskline.net/DSI/XSD">
<Request Originator="FERATEL" Company="" Language="en">
<Range Code="TO">
<!-- all towns or district that should be valid for the request must be passed here, using range
region will not work, only TO/DI -->
<Item Id="3310C506-A478-4BE8-AF74-DF697C0738FB" />
</Range>

<RequestDetails>
<Type>RequestPool</Type>
<UserId>86B9C1AA-3572-435D-9F3C-024C9F90B4C7</UserId>
<GuestToPOSComment>my dog is a doberman, but he is friendly when he is not
hungry.</GuestToPOSComment>

<!-- only used for type=request pool: -->

Saving Requests 220 of 241


DESKLINE 3.0 STANDARD INTERFACE

<RequestPoolSettings>
<MaxTickets>20</MaxTickets>
<ContactBy>EMail</ContactBy>
</RequestPoolSettings>

</RequestDetails>

<SearchLines>
<SearchParameters Index="1" SalesChannel="BB556229-E7B1-4F21-9C6A-2BEA7120BF5A"
Units="2" Adults="2" From="2010-04-20" To="2010-04-25" Nights="5">

<ServiceProvider>
<Product AccommodationType="Apartment|HotelRoom|Camping" />
</ServiceProvider>

<Children>5,9</Children>
<Meal>HB</Meal>
<MaxPrice>120</MaxPrice>
<AccommodationFacility>
<Item Id="F7E27F9D-596F-4793-961C-BDB445776D2A" />
<!-- whirlpool -->
</AccommodationFacility>
<ServiceFacility>
<Item Id="13C2AEA1-9BA5-40FE-B1B5-2E07B616B84A" />
<!-- Bathrobe -->
</ServiceFacility>
<Category>
<Item Id="AB4F2086-F06D-4DAC-8B99-09EDA5577C67" />
<!-- Hotel -->
</Category>
<Stars>
<Item Id="3C26E83D-BF2B-42E8-BC1A-C059E78E4BC4" />
<!-- 5 star dehoga -->
</Stars>
<Chain>
<Item Id="C5572A2A-4C87-4FFA-B314-BA2A850AD771" />
<!-- best western -->
</Chain>
<MarketingGroup>
<Item Id="8BAB3BAF-4221-4484-8A2B-83A99C51C5F1" />
<!-- urlaub am bauernhof -->
</MarketingGroup>
<Classification>
<Item Id="89C1A7D7-0222-4DEE-AA35-D6A01496B0BC" />
<!-- 3 edelweiß -->
</Classification>
</SearchParameters>
</SearchLines>
</Request>
</FeratelDsiRQ>

Saving Requests 221 of 241


DESKLINE 3.0 STANDARD INTERFACE

Response: On success: Transaction numbers for reference.

Note: if a request is saved to more than one local database, then there will be several transaction numbers in
the response.

<?xml version="1.0"?>
<FeratelDsiRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
Status="0" Message="OK" xmlns:debug="http://interface.deskline.net/DSI/XSD">
<Result Index="0" TotalObjects="1">
<Requests>
<Item DBCode="FRT" Number="886" />
</Requests>
</Result>
</FeratelDsiRS>

Saving Requests 222 of 241


DESKLINE 3.0 STANDARD INTERFACE

DIFFERENT USAGE CASES


It is possible that not all functions of the DSI are used at the same time. There are different approaches on how
the DSI can be implemented, allowing a maximum of flexibility:

1. Basic Data only + search + booking with links

Creating an external database and filling it with all the Deskline 3.0 Basic Data is the first step. The
service providers can then be presented in a unique layout outside of our regular web application. To
search for availabilities and make bookings can be done in a separate link – the already existing
Deskline 3.0 links.

It’s also possible to create a link to a service provider only by the knowing the ID of the service
provider. The Deskline 3.0 link will always show the latest version with all the functions available from
the link interface.

2. Basic Data and Search with DSI + Booking with links

Not only the Basic Data, but also a search can be done with the DSI. So it’s possible to create the
unique layout not only for the list but also for the search result. Then a link can be created to book a
selected service provider through the Deskline 3.0 link interface.

3. Full implementation without links

If it’s not wanted to make a booking through the Deskline 3.0 link interface, but rather on the same
site and the same unique layout, a booking can also be created with the DSI.

Examples for booking links can be send on demand.

Different Usage Cases 223 of 241


DESKLINE 3.0 STANDARD INTERFACE

TYPE LIST
Types are used a few times in the XML files. The full and definite list is available in the XSD files but here are
examples for these enumerations:

 Facility type:
 Accommodation service provider
 Additional service provider
 Service accommodation
 Additional service
 Event
 Document type:
 ServiceProvider
 Package
 ProductGroup
 Product
 Service
 ShopItem
 ShopItemVariation
 EventGroup
 EventHeader
 Infrastructure
 ServiceProviderLogo
 Document class:
 Image (jpg, png, gif...)
 Document (doc, xls, ppt, pdf...)
 Video (avi, mpg, mov...)
 Audio (mp3, wav...)
 Service provider type:
 Accommodation
 AdditionalService
 Agency
 Product type:
 Accommodation
 AdditionalService
 Package ("House-Package")
 Accommodation Type:
 HotelRoom
 Apartment
 Camping
 Meal types:
 NO: no meal
 BB: Bed-Breakfast
 HB: Half board
 34: 3/4 board
 FB: Full board
 AI: All inclusive
 Extras:
 BL: Bed linen
 FC: Final cleaning
 Price Calculation Rule:
 PerPerson
 PerUnit
 Total

Type List 224 of 241


DESKLINE 3.0 STANDARD INTERFACE

 SortOrder:
 Random
 Bookable
 BookableDesc
 Rating
 RatingDesc
 Name
 NameDesc
 Town
 TownDesc
 Price
 PriceDesc
 Stars
 StarsDesc
 TotalPrice
 TotalPriceDesc
 ServiceProviderPriority
 ServiceProviderPriorityDesc

Type List 225 of 241


DESKLINE 3.0 STANDARD INTERFACE

XSD FILES , TARGET URL/WSDL


The latest versions are always here:

 http://interface.deskline.net/XSD/DSI/DSI_Request.xsd
 http://interface.deskline.net/XSD/DSI/DSI_Response.xsd

Request and Response XSD files reference the following XSD files:

 http://interface.deskline.net/XSD/DSI/DSI_SimpleTypes.xsd
 http://interface.deskline.net/XSD/DSI/DSI_ComplexTypes.xsd
 http://interface.deskline.net/XSD/DSI/DSI_AttributeGroups.xsd
 http://interface.deskline.net/XSD/DSI/DSI_ShoppingCart.xsd
 http://interface.deskline.net/XSD/DSI/DSI_Booking.xsd
 http://interface.deskline.net/XSD/DSI/DSI_Guest.xsd
 http://interface.deskline.net/XSD/DSI/DSI_DynamicService.xsd
 http://interface.deskline.net/XSD/DSI/DSI_OrganisationData.xsd
 http://interface.deskline.net/XSD/DSI/DSI_CheckEffect.xsd
 http://interface.deskline.net/XSD/DSI/DSI_ImportBasicDataSTU.xsd

Target URL:

 Key Values: http://interface.deskline.net/DSI/KeyValue.asmx


 Basic Data: http://interface.deskline.net/DSI/BasicData.asmx
 Search: http://interface.deskline.net/DSI/Search.asmx
 Shopping Cart Manipulation: http://interface.deskline.net/DSI/ShoppingCart.asmx
 Guest Address Manipulation: http://interface.deskline.net/DSI/GuestUser.asmx
 Saving Requests: http://interface.deskline.net/DSI/SaveRequest.asmx

WSDL:

 http://interface.deskline.net/DSI/KeyValue.asmx?WSDL
 http://interface.deskline.net/DSI/BasicData.asmx?WSDL
 http://interface.deskline.net/DSI/Search.asmx?WSDL
 http://interface.deskline.net/DSI/ShoppingCart.asmx?WSDL
 http://interface.deskline.net/DSI/GuestUser.asmx?WSDL
 http://interface.deskline.net/DSI/SaveRequest.asmx?WSDL

XSD Files, Target Url/Wsdl 226 of 241


DESKLINE 3.0 STANDARD INTERFACE

GLOSSARY
Term Definition
A service provider can have one or more than one category. For example: hotel,
Category
inn, apartment, youth hostel, and so on.
Additional classification information besides the stars can be flowers, suns,
Classification
crystals and so on. Flowers for example are used for farm classifications.
There are different kinds of descriptions: service provider description, service
Description provider conditions, service description, product description. All these
descriptions can be entered in different languages for different time spans.
Documents can be images, videos, audio or regular files. Mostly, documents are
Documents
used for images and logos, but can contain more information.
Facilities can be assigned to a service provider or a service. In Deskline 3.0 they
are managed in different groups (location, wellness, equipment, and so on) and
Facility
can have a value as well (e.g. “meeting rooms: 4”). The translations are part of
the key values function.
Global Unique Identifier, 38 characters.
GUID
Example: 51A9A999-1AE7-4C89-978F-6E3E6813513A
Holiday Themes are assignments to products or events or other items. For
Holiday Theme example, once a product that is assigned to “Summer” is selected, customers
could display a list of appropriate shop items or infrastructure items and so on.
Marketing groups are used to group a set of service providers or to show the
visitor in which marketing groups a service provider is part of. These groups can
Marketing Group be used as a filter in lists or in the search and also there can be special links that
show all service providers of a specific marketing group. Examples: Farm
holidays, Mountain bike hotels, …
The result of a search is a list of products that can or cannot be booked. Each
Product product consists of its own prices, sales rules, arrival/departure conditions,
descriptions, documents and occupancy settings.
Users are allowed to rate service providers. The questions are pre-defined and
the visitor can also state if the hotel is a recommendation or not and add a
comment to his rating. Ratings are a closed system, meaning that the guest
Rating
automatically receives a rating-invitation-mail some time after the departure
date of the booking. The rating module is not automatically active for every
customer.
In Deskline 3.0 requests are requests from guests who want to stay in a tourism
destination and want to have some offers for their stay. These requests are
Request
stored in the database and the request pool allows for service providers to
directly send their offers to the guests in question.
A service is the base for every product, consisting of general settings, facilities,
Service descriptions and documents. This level is not transferred in the DSI but the
necessary service information is send along with the product details.
A service provider is either an accommodation service provider (hotels,
Service Provider
apartments, …) or an additional service provider (e.g. ski rental) or an agency.
*, **, ***, ****… stars can be awarded to every service provider but only one
Stars
value can be assigned.

Glossary 227 of 241


DESKLINE 3.0 STANDARD INTERFACE

CHANGE L OG
This document will be changed constantly with new functions / elements / attributes / values that are used
within the interfaces. These changes will be documented here.

Version Description of changes done


1.0.1  First draft
1.0.2  Second draft, more concrete idea about BasicData, finished with SP-level
Documents and Descriptions, Search completed, KeyValues Request done,
Response in progress. Extended the documentation with list of fields and
information if they can be missing or not.
1.0.3  Finalized Key Values and changed the types how translations are sent to a
more reusable approach – TranslatableList.
1.0.4  Added AccommodationType and ProductType in the search request and
response.
 Finished the test environment and added the link to the WSDL.
 Added the ServiceProvider element in the search request to be able to
search inside one service provider based on either ID, code or name.
 Added Product element inside this ServiceProvider element to be able to
search for a specific product as well.
 Added the search for one item to the example files.
1.0.5  Extended the documentation and added information if an element can be
used more than once or not.
 Extended the documentation for Rating Information in the search result.
Added MealCode to the search result, useful if a search was made without
a specific meal.
 Added Address types “Landlord” and “Owner” to the BasicData Response.
 Added Price Range (min/max values for all assigned price templates) and
Calculation Rule information to the product layer in the BasicData
Response.
1.0.6  Added SortOrder to the search request (Random, Prices, ..).
 Enhanced the price range with occupancy to allow more detailed
information per product.
1.0.7  Updated the XML examples and the XSD chapter to also have the links to
the XSD files that are referenced inside Request & Response XSD.
 Corrected the search for facilities information (wrong example).
 Corrected an inconsistency in the enumeration example for ProductType
and AccommodationType.
 Introduced the “Known Issues” chapter.
1.0.8  Resolved the random sorting. Sorting is done by object not by product so
there will only be one <ServiceProvider>-Tag with one or more products
for each object.
1.0.9  Changed the BasicData request Element SPType
(<SPType>Accommodation</SPType>) to ServiceProvider
(<ServiceProvider Type="Accommodation" />). Now it is the same type
that is used in the search request. With this change it supports the
Attribute Code, Name and Id which allows getting all the data for one
selected service provider.
 Change in the Key Values response: Classification / Category / Stars /
Marketing Groups / Holiday Themes / Facilities / Chains / Service
Classification now have the Attribute Active (true/false).
1.0.10  Added field <LastAvailabilityChange> on Service-Level
 Fixed the data-format of the response for prices (“50,00”  “50.00”) in
the Basic-Data Product-Element.
1.0.11  Added the parameter BasePriceOnly in the search. This is used to define if

Change Log 228 of 241


DESKLINE 3.0 STANDARD INTERFACE

the total price should be calculated or not. Total price calculation


decreases performance so it must not be used for a wide area search, only
calculate prices when searching inside one service provider.
1.0.12  Added the Attribute ServiceProvider Status for BasicData requests. It is
now an enumeration (All/Active/Inactive).
 Added the Element Active in the BasicData details. Can be true or false.
 Introduced the <PreSelectedServiceProviderIDs> on the search function to
be able to search inside more than one service provider based on their ID.
Used for total price calculation with – for example – the first page of a
wide area search result.
1.0.13  Introduced the <PreSelectedServiceProviderIDs> on the basic data
function to be able to select more than one specific service provider
based on their ID.
1.0.14  Added the Attribute “Extension” to the <Document> Elements (e.g. jpg,
gif, ..)
 Added the type ServiceProviderLogo for Service Provider Documents if the
service provider uploaded a logo for a property.
 Added the Element <ServiceCodes> in the KeyValues function.
 Added the Element <Code> inside the <Service> <Details> which refers to
the <ServiceCodes> from the KeyValues. Used to identify single rooms,
double rooms, … by type instead of occupancy.
 Added the chapter “Changing from Deskline 2.0 to Deskline 3.0” for
partners that will change from SCSI to DSI.
 Extended the information about the use for Range Code + ID in the
requests.
 Added <CreditCards> Element in ServiceProvider Details to provide the
accepted credit cards per Service Provider.
 Added <GridSquare> and <PlanNumber> in ServiceProvider Details. These
values were in the documentation before but not part of the response.
Now they are added.
 Fixed a bug where a selection for a single town returned service providers
of the whole Data Owner instead of the town.
 Added the rating answers per hotel in the BasicData response. The
questions and their IDs are not part of the interface as of now, they must
be sent as a list on demand.
1.0.15  Fixed a bug where not all Service Provider Addresses were returned in
(2010-03-09) some cases.
 Fixed a bug in KeyValues function for the Facilities.
 Added DatabaseCode and SettlerCode to the search result in preparation
for the booking function.
 Facilities in KeyValues can now read facilities for the type “Event”.
1.0.16  Introduced a new attribute Company on the Request element (for every
(2010-04-15) function). This helps us to identify the company that is requesting data in
addition to the already mandatory code of the POS. (One POS can allow
access for several companies, thus the extension). The company code is
provided by feratel.
 Performance improvements for the search.
 Added an additional attribute in the SearchLines:
SearchType="OneProductPerHotel" to only get one product per service
provider.
 Tip for performance improvements when searching inside one specific
hotel only: if you pass the ID to the search function instead of the code or
name then the search will perform much faster.
 Search: maximum PageSize value is 300.
 Search: maximum duration to be searched for is 60 nights.

Change Log 229 of 241


DESKLINE 3.0 STANDARD INTERFACE

 Extended the Basic Data workflow chapter and added more detailed
descriptions in some parts of the documentation.
 Added Salutations and GuestCountries in the KeyValues function –
necessary to get mandatory information for storing a guest address.
 Added <Availabilities> per Service. Only returned when the Service
Provider ID is passed in the filter!
 Added the attribute Types in KeyValues <FacilityGroups> and <Facilities>
so now it is possible to filter these items based on the project needs.
Allows to filter for Service Provider, Service or Event items.
 Added information in the Basic Data response for various elements such
as categories, facilities: If there are any IDs present that are not provided
in the Key Values function it is because of items that were created by the
customers themselves and therefore are not global and not available in
the Key Values.
 Corrected some Element-names inside the Basic Data details response
documentation to fit to the actual XML response.
 Added the attribute ChangeDate where applicable for Items like
ServiceProvider, Service, Product, Document, Address, Description, Link
and also in the items of the KeyValues function.
 KeyValues element Countries was renamed to GuestCountries (it was not
used up to now). Countries are now another level of regional data along
with Regions/Towns/District for companies that request data from more
than one country.
 KeyValues received a new attribute GetLocalValues. Necessity of this
depends on the project to be realized (contact feratel!). Most of the
projects will have to use global data for the KeyValues but some parts like
RatingQuestions and RatingVisitors only work with local values.
1.0.17  Added information in the description of the search result TotalPrice. It’s
(2010-04-26) possible in some cases that the TotalPrice is 0, these search results should
not be displayed to the guest.
 Added the element DBCode for Service Provider Details. This code is also
returned inside the search result but it will be necessary if you want to
create a direct link to a service provider.
 Added the chapters Guest Address Management, Saving Requests and
Booking. This is the first version of the booking, only supporting direct
payment to the service provider, further options and features will follow
in the next versions.
1.0.18  Hotfix update: when using a search with AccommodationType it was
(2010-05-05) possible in some cases that the amount of search results was different in
the modes SearchType=Standard and SearchType=OneProductPerHotel.
1.0.19  Corrected the response example for Saving Requests in the
(2010-06-22) documentation.
 Corrected the description for basic data languages – they are mandatory
and not optional.
 Corrected the description for ProductType/AccommodationType in the
search request.
 Added the chapter Basic Data Events.
 Added the chapter Basic Data Infrastructure.
 Added the chapter Basic Data for Shop Items (Brochures and Articles).
 Added the elements ShopItemGroups, InfrastructureTypes,
InfrastructureTopics, SerialEvents to the KeyValues.
 Added the flag Active in basic data response for Services and Products as
well.
 Extended the Basic Data request for Service Providers so it is possible to
filter active/inactive also in Services and Products (default: active) and to

Change Log 230 of 241


DESKLINE 3.0 STANDARD INTERFACE

be able to filter products based on AccommodationType and ProductType.


It is also possible to filter only service providers that would generally be
bookable. See more information in the basic data request.
 Added the flag Bookable to Service Provider Details.
 Added new address type Keyholder for Service Providers.
 Added ValidDates for Details in products of the type package. A package
can be either valid always or only in specific periods.
 Extended the chapter Basic Data for Service Providers with an explanation
about how service providers, services and products are connected.
1.0.20  Extended the documentation about Service/Product filter as introduced in
(2010-06-30) the 1.0.19 update.
 Added Service-ID and Product-ID as a filter for Basic Data requests.
 Added Attribute SalesChannelId in the Filter element for Basic Data
requests. Usage may be mandatory depending on the project.
 Added the price details per product as the first step, arrival/departure
templates and sales-rules templates will follow.
 Changed the response for events/infrastructure to be prepared for future
cases where event-items or infrastructure-items can be assigned to more
than one town. This is not the case right now in Deskline 3.0 but this way
the structure is already prepared to avoid having to change it afterwards.
1.0.21  Fixed a bug for parameter SortOrder in search function.
(2010-08-27)  Fixed the Key Values function so that the range from the request will be
checked and will return only appropriate regions/towns/districts.
 Fixed a cache-related bug for some searches; for example in some cases
when using paging.
 Fixed a bug for <Price> response in Basic Data when using different prices
for different sales channels.
 Fixed a bug in Basic Data filter & response with packages.
 Fixed a bug in Search for Product ID and Product Type with packages.
 Added optional attributes Start/End for product Basic Data Element Price
to be able to control the period for the min/max values returned.
 Altered the response for Shop Items of type “Brochure” (changed Names
to Element Language).
 Added the element DatabaseCode for Shop Item Details.
 Added the elements AmountSaved and IsBestPrice for the search response
when using the total price calculation.
 Added the optional attribute LinkKey for committing bookings.
 Added the arrival/departure details per product.
 Added the sales rule templates per product.
 Added additional service providers.
 Added additional services and additional products.
 Added the chapter Questionnaire.
 Added the information on how to add brochures to the shopping cart.
 Added the information on how to cancel a booking.
 Enhanced the documentation index to also include the first level of
chapters inside a chapter.
1.0.22  Fixed the response for ArrivalDepartureTemplates, the <Periods> element
(2010-09-14) was missing from the output.
 Added the missing information about Dates, StartTimes and Durations for
AdditionalServices.
 Added HolidayThemes filter to the search function inside the product
element.
 “Moved” the ServiceFacility filter for the search function inside the service
element. The ServiceFacility element inside the SearchParameters is still
working to stay compatible.

Change Log 231 of 241


DESKLINE 3.0 STANDARD INTERFACE

 Added the search for ServiceClassification in the service element for the
search function.
 Added the LastAvailabilityChangeDays attribute in the service element for
the search function.
 Added StandardMealCode for basic data response in Prices element.
 Added bank account details per service provider details. Only necessary
when using the booking function to display the information to the guest
on the confirmation page.
 Added the service provider CurrencyCode to the service provider details
element.
 Added the optional attribute GetSettlementAddresses (true/false) to
service provider addresses element. The default value is false, therefore
settlement addresses are only returned when requested!
 Added BankCodes to the KeyValues (only returned when using
GetLocalValues).
 Added a new description type for service providers: SEOKeywords.
 Search results with SortOrder=Random are now part of the cache as well,
therefore paging with random sorting is possible.
1.0.23  Enhanced/updated the basic data synchronization workflow chapter.
(2010-11-02)  Added CustomAttributes for Service Providers (Type Accommodation) to
the KeyValues and BasicData.
 Added the chapter “Get Settler Information” for the booking process.
 Added the ID for Addresses in Basic Data (Service Provider, Events and
Infrastructure) response.
 Added the chapter “Reading a booking” – the function is present since
update 1.0.21 but the documentation was missing.
 Added the function to store an offer request for one specific hotel based
on Service Provider ID.
 Added the chapter “Basic Data: Deleted Items” where we can return a list
of deleted IDs. Has to be activated on demand.
 Added the chapter “Search for Additional Services”.
 Added the chapter “Adding Additional Services to a Shopping Cart”.
 Important update for companies requesting availabilities: some customers
allow the storage of different availabilities per sales channel. The product
availabilities are used for this and therefore the Availability-element on
product level was extended with the attribute OwnAvailability.
 Updated the booking information for “BookOnRequest”-Items. Before it
said only one BookOnRequest item is possible inside one booking. This
was changed to “only BookOnRequest items of the same service provider”
are possible.
 Updated the shopping cart manipulation information. When removing
items from one shopping cart it is vital to create a new shopping cart once
all items were removed.
 Added HotSpotTypes description to the documentation.
 Added the element HotSpots to the KeyValues and BasicData for Service
Providers.
1.0.24  By mistake, the Title Element in Addresses was always empty/missing, but
(2010-12-14) it was already present in the XSD. This was fixed.
 Various XSD fixes.
 New Attributes RefNo and SecureValue in Shopping Cart response. These
values are here in preparation for the credit card guarantee/payment
process.
1.0.25  Added the chapter “Credit Card Guarantee With Datatrans” – it is now
(2011-01-17) possible to use a solution with a payment provider to at least save
bookings with using a credit card guarantee. Saving the booking without

Change Log 232 of 241


DESKLINE 3.0 STANDARD INTERFACE

any payment is still the only way to book on the interface.


 Fixed a bug for event visibility, “Local” was value “String” by mistake (in
XSD, request, response).
 Extended the booking info about the possible payment solutions (only “no
payment” – payment directly at the service provider – is supported as of
now).
 Changed the contact address for the product manager responsible for this
interface.
1.0.26  Added chapters “search destination package” and “search destination
(2011-02-22) package details”
 Added description of multiline search in chapter search for availabilities
 Added check on availability if product is added to shopping cart.
Response: "Availability is not enough."
 Search for availabilities: possibility to search for minimal number of rooms
and sleeping rooms and minimal size of service in square meter
 Added element LinkKey to request import
 Added gaps to basic data request and response
 Added and changed xsd file urls in chapter “XSD Files, Target Url/Wsdl”
 Fixed: Visibility of event item changed String to Local
 Fixed: Range filter at basic date for infrastructure
 Fixed: changed data type of availabilities in basic data response to integer
to produce valid xml
 Fixed: Return only arrival and departure templates assigned between start
and end date of basic data request
1.0.27  Added all necessary information concerning currencies: no changes in
(2011-04-13) Basic Data, Search with specific currency possible, else default currency of
originator is taken, all prices in the response are converted to the
requested currency. Shopping cart is always displayed in the settler
currency; if requested currency is different a currency factor to convert by
division is provided. Booking information is also always in settler currency
and currency factor for conversion is provided
 Provided solution to search in a specific distance to a hotspot
 Added opening hours (part of details) and hotspots (on request only) in
response of infrastructure basic data
 Added Price information to response of package detail search
 Added Extras information in response of shopping cart
 Added additional filter for basic data request on events if they are Top
Events or not
 Added TypeId to the response of hotspot key value request to provide the
information which hotspot is related to which hotspot type
 Fixed: Return only sales rules templates assigned between start and end
date of basic data request
 Fixed: Sort order bookable is now sorted bookable first then bookable on
request and the not bookable
 Fixed: Key Value Request on Bank Codes, now BIC is also included in the
response
 Corrected wrong enumeration about Accommodation Type in
documentation
1.0.28  New: Check for Changed Service Providers
(2011-05-23)  Added possibility to include also DataOwner in basic data of service
provider
 Added the Attribute Service and Product Status for BasicData requests. It
is now an enumeration (All/Active/Inactive).
 Added additional element FoodAndBeverage in basic data of an
infrastructure if it is of type food and beverage

Change Log 233 of 241


DESKLINE 3.0 STANDARD INTERFACE

 Added Currency information in chapter Guest Address Manipulation


 Added Currency in the response of GetOrganisationInformation
1.0.29  New: Reading a list of all reservations/transactions possible
(2011-07-13)  New: Search for Last Minute offers only
 New: Get Payment Information of a settler
 New: Basic Data for Destination Packages
 Performance improvements in all kind of requests (since 1. June)
 Improved: A shopping cart cannot be committed twice. If shopping cart
has already been committed the interface answers with an according
message and the transaction id.
 Fixed: Booking with MealCode 34 was not possible
1.0.30  New: Improvements in Get Payment Information of a settler
(2011-08-09)  Added service provider name in result of search for additional services
 Fixed: Guest data was mixed up in response of ReadTransactions
 Fixed: Services and products were listed twice in response of basic data
for service providers
1.0.31  New: All possible payment types and payment methods are supported.
(2011-08-30) Split and Organisation payment is possible as well as payment methods
credit card and invoice.
 Improved: Availabilities in Basic Data Request, DateFrom turns into
optional and will be ignored. Every time all requested availabilities will be
included in the response, except of value zero. ChangeDate will be
provided in the response as well.
 Add attribute SubType in Key Value response of infrastructure topics to be
able to separate
 Add Basic Data for Sections and Products of Destination Packages
1.0.32  Improved: OfferRequest and RequestPool for unknown number of units
(2011-10-06) possible. E.g. Units=”0” Adults=”25”
 Improved: Added information about expiration of a BookingOnRequest in
ShoppingCart
 Improved: Added information if price splitting is used in search result
 Fixed: Filtering of RequestPools and OfferRequests on
AccommodationType now works
 Fixed: Imported guests are set to active
 Fixed: Sending guest and provider confirmations depending on the
company settings
1.0.33  New: Event search
(2011-11-02)  Improved: Added data owner information to package basic data details
 Fixed: Per default only active additional services are included in the basic
data response
 Fixed: When calling changed basic data of PriceDetails,
ArrivalDepartureTemplates and SalesRuleTemplates changes in period
were now also affected
 Fixed: Although communication to guest is set to false batch printing in
case of an InfoRequest is not prohibited
1.0.34  Improved: Basic data for events and infrastructures can now be called for
(2011-12-20) one single item using the Id
 Improved: If a request pool is only inserted for a collection of districts,
also the towns are set, so filtering in backoffice system is possible more
correctly
 Fixed: TotalObjects included in search result, when BasePriceOnly is true
1.0.35  New: Another SearchType “EachProductSeparated” is available.
(2012-01-12) EachProductSeparated means if a service provider has more than one
product available they will be listed separately in the response, also
TotalObjects is based on products found and not service providers found,

Change Log 234 of 241


DESKLINE 3.0 STANDARD INTERFACE

so paging can be done on product level as well. May be useful for


products of type Package.
 New: CustomAttributes are now available in basic data for events and
infrastructure
 Improved: In Search for Availabilities LastAvailabilityChangeDays can be
set to zero and customer settings then will be taken automatically
 Improved: Reusable and Rating in guest insert and update can now be
defined separately.
1.0.36  New: Search for accommodations now also provides sort order by total
(2012-02-03) price and stars classification
 New: Search for accommodation now can be done within a specific radius
 New: Call for changed and single KeyValues is now possible
 Added: Some of the KeyValues in response now have additional attributes
Status (active or not) and Global (comes from Meta Server or local
customer database)
 Added: In response of basic data for price details of products the attribute
OrgPaymentRequired was added, which marks the product that it can be
booked only with PaymentType OrganisationPayment
 Added: KeyValues for CustomAttributes now also includes those of type
Event and Infrastructure
 Added: Basic data for documents now also include the attribute size (in
kB)
 Fixed: If request pool or offer request is send without number of nights,
the number will be set automatically to the difference between DateFrom
and DateTo
1.0.37  Added: Possibility to request basic data (service provider, event and
(2012-03-08) infrastructure) of a certain marketing group
 Added: Filter for requesting events and infrastructures for specific
systems (e.g. only those to be shown in internet)
 Added: Possibility to include also DataOwner in basic data of
infrastructures
 Improved: All addresses are part of response of basic data request if the
parent (service provider, event and infrastructure) has changed. So also
changes in the relation between address and parent can be recognized
1.0.38  New: Update of payment method of a shopping cart is now possible
(2012-03-26)  New: Get information about booking and cancellation fees and insurance
of a settler (GetOrganisationInformation)
 New: Provided method for precalculation of booking fee and cancellation
insurance of a specific shopping cart
 Improved: Multithreading in Search when more than one database is
affected (performance improvement)
 Added: Search with parameter MinPrice is now possible
 Fixed: Ratings were assigned to more than one service provider in
response of basic data
1.0.39  New: MetaRating mapping codes, average and count available in basic
(2012-04-23) data for service provider (cooperation partners HotelNavigator and
TrustYou). This is an additional module so data is only provided if
customer has contract with meta rating company
 New: Fallback languages are provided via KeyValue Request
 New: Links can be now exactly categorized. Which types are in use can be
called via KeyValue Request and in Links provided via BasicData, the type
is an additional attribute
 New: Method to check if shopping cart is already committed or not
 Improved: In case of guarantee or payment with Datatrans send
additional parameter useAlias=”yes”. Redirect then includes the alias of

Change Log 235 of 241


DESKLINE 3.0 STANDARD INTERFACE

the credit card which makes it possible to call real credit card data (in the
web based tool for service providers, not additional feature on interfaces)
in case of noshow for the service provider affected.
1.0.40  Improved: It is now possible to add multiple items of the same product in
(2012-05-02) shopping cart with one request
 Improved: In shopping cart only those possible payment methods are
listed which fit with the items inside
 Changed: In package detail search element SalesChannelID now has to be
provided.
 Added: In response of basic data for price details of additional services the
attribute OrgPaymentRequired was added, which marks the product that
it can be booked only with PaymentType OrganisationPayment
1.0.41  New: Availabilities of additional services can now also be called
(2012-05-23)  Added: Additional address type for events “Venue” is now also provided,
which is the address where the event really takes place
1.0.42  Added: Possibility to call local KeyValues only
(2012-06-26)  Added: In basic data for additional services attribute NeedAcco is added,
to show if the service can only be booked in combination with an
accommodation
 Added: Search with service code is now possible
1.0.43  New: Possibility to book shop articles
(2012-07-11)  New: Search for accommodations now also provides sort order priority
 New: Customers now have the possibility to set a minimum count of
ratings which has to be reached, unless ratings shouldn’t be shown. If this
count is not reached search function for accommodations automatically
returns zero values.
1.0.44  New: Call of closed periods in basic data for service provider
(2012-07-23)  New: Filter in search for accommodation and additional service to get only
bookable without bookable on request
 Improved: Translations of links can now also be called
 Fixed: Changes in geo coordinates are now also considered when changed
data of service provider, infrastructure or event is requested
1.0.45  New: Handicap Facilities in KeyValues and BasicData.
(2012-08-22)  New: Logical operator AND between marketing groups now possible in
single line search for availabilities
 New: Top event filter in search for events
 Improved: Get local values for infrastructure types in KeyValues
 Fixed: All basic data of destination packages are now provided
 Fixed: Salutation of guests if full name has to be substituted are now
created properly
1.0.46  New: General Therms and Conditions of Service Providers can now be
(2012-09-25) called in basic data interface
 New: Search availabilities with filter on handicapped criteria
 Improved: Added ChangeDate in parent elements (Facilities,
HandicapFacilities, CustomAttributes, HotSpots, SalesRulesTemplate) of
basic data response were missing to improve the support of delta
synchronizations
 Improved: Added attribute order in basic data response for Links
 Improved: Regular expression of EmailType has changed to be able to
insert email addresses with domains up to 15 characters long
 Changed: Count in response of rating average has changed type from
short to integer
 Fixed: Double Services in basic data response due to double assignment of
classifications no longer appear
 Fixed: Packages of other customer organizations are no longer included in

Change Log 236 of 241


DESKLINE 3.0 STANDARD INTERFACE

basic data response if access rights are not present


 Fixed: If customer organization has setting that request pool confirmation
should not be send, it will not be send
 Fixed: MetaRatings are no longer included in response if RatingAverage is
requested
1.0.47  New: Booking of destination packages is now possible
(2012-10-30)  Fixed: Package date filter in basic data request now filters on valid periods
of packages not on package change date
 Fixed: Search for availabilities in combination with SearchType
EachProductSeparated and filter on service provider name now provides
correct number of TotalObjects
1.0.48  New: Payment with ELV is now possible
(2012-11-27)  New: Infrastructure main topic can be requested if maintained
 Improved: Durations of additional services in shopping cart and booking
confirmation are now improved
 Improved: Shopping cart with payment method CreditCard for none
Datatrans customers is now possible to create, shopping cart then has to
be committed via link system
 Fixed: If Gaps are called products of type Package are now included in
response as well
 Fixed: HandicapFacilities for infrastructures can now be called
1.0.49  New: Search for Split offers only
(2012-12-18)  Improved: Committing one and the same shopping cart via Datatrans only
possible once
 Improved/Fixed: Caching for search result paging
 Fixed: SortOrder TotalPrice now also works in case of search with children
1.0.50  Important Information: Datatrans requires guarantee amount of 1 Euro or
(2013-02-04) 1 Swiss Franc instead of 1 Cent/Rappen, so please set amount in case of
credit card guarantee to 100! Thank you!
 New: New response type in search for availabilities, which includes
additional information and functionality.
 Improved: Added information about price details in read transaction list
to support better settlement
 Fixed: Package prices no longer in result if they don’t fit the package
settings for duration and occupancy
1.0.51  New: Basic data for package container
(2013-03-04)  New: Search for accommodations now have filter to search within one
package container
 Improved: Include package category information in package details for
destination packages and package containers
1.0.52  New: Check for changed events
(2013-03-19)  New: Check for changed infrastructures
 Improved: Call for deleted items with DateTimeFrom
 Fixed: Visibility levels in events have now correct value
1.0.53  New: On demand data for availability calendar
(2013-05-08)  New: Comment for handicap facilities
1.0.54  New: Price element in details of article variation
(2013-06-25)  Improved: Event search result is also chronological ordered by start time
not only start day
1.0.55  New: Basic data for cancellation and payment condition templates
(2013-10-07)  New: Added cancellation information in expanded search result.
 New: Request to get cancellation information for a specific product, date
and occupancy.
 New: Adapted booking process to new individual payment settings per
product. Added attribute PaymentMethod to shopping cart in service

Change Log 237 of 241


DESKLINE 3.0 STANDARD INTERFACE

provider prepayment section. Request to change optional guarantee


settings.
 New: Adaption to all data base changes done in
ArrivalDepartureTemplates and SalesRulesTemplates. Template with
same Id can be assigned to multiple products now.
 New: Basic data extension for additional service and products. Added
Documents, Descriptions, Links and SalesRulesTemplates
 New: PackageOnly in product details of tape additional service to show if
a product is just for use inside packages or not
 New: HandicapClassifications available in basic data
 Improved: GuestCountry no longer required when inserting a guest
address
 Improved: Read transaction list no also provides transactions of type
BookOnRequest and the datetime until when it is valid
 Fixed: Documents of additional services in response again
 Fixed: Delete first inserted destination from shopping cart now working
 Fixed: Surcharges and discounts in price template now correct on base of
all settings
 Fixed: ShowShoppingCart now always gives results with already given
guest currency in Currency element
1.0.56  New: Total price filters in search for availabilities
(2013-12-02)  Fixed: DateFrom in ChangedEvents request now filters for correct change
date
 Fixed: Additional services departure date in case of duration type days is
no longer set one day too long
1.0.57  New: Request to get payment information for a specific product, date and
(2014-03-04) occupancy.
 New: Individual cancellation conditions on service provider level can now
have several fee entries depending on the days between cancellation and
arrival. These changes affect basic data response for
CancellationPaymentInfo and CancellationPaymentTemplates, search for
availabilities with ResponseType=”Expanded” and response of
GetCancellationInformation.
 Improved: Added DialCode to response of key values for GuestCountries
 Fixed: Inactive objects have been included in the result of basic data
although not requested.
1.0.58  New: Possible to provide list of infrastructure and event ids in Basic Data
(2014-06-03)  New: New package description type available (Content description)
 New: Added CreateDate in Ratings to provide information when rating
was done also after it has changed
 New: Translations of service provider name now available
 New: Translation of location name in key values now available
 Fixed: Separated check for changed data of ratings and meta ratings.
1.0.59  New: Information of visitor tax costs are now included in key values and
(2015-02-24) basic data for service providers
 New: Attribute DaysBookingStops in Basic Data for destination packages
 Improved: Additional service search can now be done with filter on
service id
 Improved: Result of additional service search now shows availabilities
 Improved: It is no longer allowed to put destination packages into
shopping cart when OrganisationPayment is not supported.
 Improved: Availability check when put accommodation product into
shopping cart is now independent from occupancy
 Improved: + sign is now allowed in email addresses
 Fixed: Additional Service Search now delivers correct information about

Change Log 238 of 241


DESKLINE 3.0 STANDARD INTERFACE

bookable not for each arrival date separately


 Fixed: Now correct duration values in basic data for additional services are
shown.
 Fixed: GetPaymentInformation now return right value for SplitPayment
 Fixed: Correct section dates of destination packages now shown in
shopping cart.
 Fixed: Package Containers no longer in response of basic data request for
destination packages.
1.0.60  New: Description of SEPA payment via Datatrans added.
(2015-04-22)  New: SortOrder Distance and DistanceDesc added.
 Improved: Objects without rating are always listed on the end, no matter
if SortOrder Rating or RatingDesc.
 Fixed: In certain cases expanded event search does not returned entered
descriptions.
1.0.61  New: New connected entry option AdditionalService
(2015-07-10)  Improved: Check for correct format of date From and To by Save Request
 Fixed: Bug by creating shopping cart for Destination Packages
 Fixed: Bug by creating shopping cart with method NoPayment
1.0.62  New: Information about QualityScore, CheckForActiveAv and BestPrice
(2015-08-07) are available via the BasicData Interface (Element: QualityDetails)
 New: Possibility to save Package Requests for the back office system
 New: Information about ServiceName in BasicData request for
AdditionalServices
 Fixed: Change in URL for brochures and article
 Fixed: Bug by GetAvailabilityMethod with Attribute ProductID
1.0.63  New: PaymentMethodes to Datatrans (LightboxMode and RedirectMode)
(2015-09-29) HiddenMode no longer be available after 01.01.2016
 New: Information about HousePackageMasters are available via the
BasicData Interface (Element: HousePackageMasters)
 New: VisitorTax text from organization in the GetSettlerInformation
Request
 Improved: Now we give back the organizations texts which are valid for
today
 Improved: Result for GetCancellation Information Request
 Fixed: Saving of the accommodation type in DSI Save Request Interface
1.0.64  New: PackageDescription Short and Long for HousePackageMaster
(2015-11-24)  Improved: Change in Click Count for necessary guest SessionID
 Fixed: Bug by communication for credit card bookings
 Fixed: Bug in shoppingcart for correct response of FinalPayment
1.0.65  New: PaymentMethod Sofortueberweisung and iDeal
(2015-12-16)  Fixed: Bug in GetCancellationInformation
1.0.66  New: Information about SpecialPrice and BestPrice in expanded search
(2016-03-10) response
 Improved: correct saving of fellow travelers with
UpdateShoppingCartExternal request
 Improved: saving of cancelation amount in shoppingcart for completing
the booking in TOSC
 Improved: Add ShowPrice and AddPrice Attribute to package search
response
 Improved: DSI Search ResponseType Expanded - we give back the
cancellation information in the same way like in
GetCancellationInformation Request
 Fixed: Check for 2 hours old shopping cart is implemented again
 Fixed: In special cases we show the final amount for SplitPayment as
PrePayment to ServiceProvider
Change Log 239 of 241
DESKLINE 3.0 STANDARD INTERFACE

 Fixed: Bug by creating and adding OrganisationPackages to shopping cart


with children
 Fixed: Bug in DSI Basic Data – in special cases we gave back the same
product twice
 Fixed: further check to prevent the creating of an shopping cart with
inactive product
 Fixed: Bug in ShowPrice and AddPrice Attribut in package BasicData
response
1.0.67  New: Special price type in BasicData Response
(2016-06-28)  New: Detail information about payment and cancellation in ShowBooking
and ReadTransaction Request
 New: Attribute for final payment invoice days before arrival
 New: PackageDescription Short and Long for HousePackageContainer
 New: Filter element for HousePackageMasters
 New: Expanded PaymentInformation in search for availabilities
 Improved: GetCancealltionInformation response when object uses
organsiation settings
 Improved: Show DataOwner attribute for events
 Improved: Booking of additional service with price 0 if the additional
service is marked as free additional service
 Improved: Its no longer mandatory to send Insured persones for ERV AT
 Fixed: Currency value in GetCancellationInformation response
 Fixed: Corrected total price in search result in case of surcharge/discount
of revenue manager in combination with special price
 Fixed: Bug BasicData request for CancellationPaymentTemplates
 Fixed: Wrong translation for product names in PackageDetailSearch
 Fixed: Bug in BasicData request for PackageContainer filters

1.0.68  New: Description Type Price Info in Ifrastructur Basic Data Response
(2016-09-28)  New: Attribute FreeBookable in Additional Service Response
 New: Info about CreditCard Guarantee for IncludePaymentDetails in
ShowBooking and ReadTransaction Response
 New: possibility to use Datatrans Sign value
 New: Datatrans Sign Value in OrganisationInformation Response
 New: Timestamp in DSI ShoppingCart Response
 Improved: Basic Data for Events Date From Date To Filter
 Improved: Check for ChangeDate of GeoCoordinates
 Improved: Fallback logic for paymentsettings from organization
 Improved: Search Filter for ServiceProvider Name in DSI Search
 Fixed: Bug in CancellationInfo in ShowBooking and ReadTransaction
Response
 Fixed: Bug in Basic Data Response UseOwnCancellationSettings
 Fixed: Bug in prepaymentamount ShoppingCart Response for ERV
payment
1.0.69  New: Basic Data Request for Events can be requested 3 months back
(2016-12-13)  New: Download URL for Documents changed to resc.deskline.net
 New: CancellationProtectionText in GetOrganisationInformation Response
 Improved: Performance of Check for Changed Basic Data Request
 Improved: Timestamp in DSI shoppingcart shows Create Date
 Fixed: Date Format in ShowBooking / Read Transaction
 Fixed: Bug in Add to Shoppingcart of Additional Services
 Fixed: Bug in BasicData Response for Events, Events without Period was
Change Log 240 of 241
DESKLINE 3.0 STANDARD INTERFACE

not shown
 Fixed: Booking of cancellation insurance with destination Packages
1.0.70  New: Package Type HousePackageMastersSelfAssign
(2017-02-28)  New: Optional Filter Attribute DBCode for BasicData
 New: Markup for descriptions
 Improved: Basic Data Request Element Prices /PriceDetails also checks
calendar assignments
 Fixed: Bug in GetPaymentInformation Request
1.0.70.1  Fixed: Bug in BasicData Request for DestinationPackages
(Hotfix)  New: Parameter for Datatrans Payment data-upp-start-target
3.172.1.1 Hotfix  Changed: Naming of Versions. The declaration of the version is now the
(2017-04-20) same as we have also in other feratel products
 New: DSI Search Filter by Content Score
 New: Optional Attribute CheckMinAmount for MetaRatings
 Improved: Filter for Events in the past for 3 months removed
3.172.1.2 Hotfix  Fixed: BasicData Response for Additional Services
(2017-05-23)  Fixed: Problem when AddServices Shopingcart is opened in TOSC4
3.173.0.0  New: DSI Search Request – Search Request with Type Expanded and one
(2017-06-20) specified Serviceprovider includes in Response also Revenue Information
 New: Landlord Picture and Description via Basic Data Request
 New: New Type GroupRequest (SavingRequests)
 New: New Description Type EventHeaderShort in BasicDataResponse
 Fixed: in some cases GetPaymentInformation Response provides no active
Paymenttypes

Change Log 241 of 241

You might also like