GTA Static Data 2 3

System Scope Document for: -
Client Based XML Interface Static Data

Version: 2.3.
30-Sep-05 67096449.doc
Version 2.3. Page 1 of 91
Contents
1. Introduction 5 1.1 Overview............................................................................................................5 1.2 Purpose of this document..................................................................................5 1.3 The API Architecture document.........................................................................5 2. Static Data 6 2.1 Overview............................................................................................................6 2.2 Codes recognised by the API............................................................................6 3. Search Currency 7 3.1 Overview............................................................................................................7 3.2 Example XML Search Currency request...........................................................7 3.3 Example XML Search Currency response.........................................................7 4. Search Country 9 4.1 Overview............................................................................................................9 4.2 Example XML Search Country request.............................................................9 4.3 Example XML Search Country response.........................................................10 5. Search City 11 5.1 Overview..........................................................................................................11 5.2 Example XML Search City request..................................................................11 5.3 Example XML Search City response...............................................................12 6. Search Area 13 6.1 Overview..........................................................................................................13 6.2 Example XML Search Area request................................................................13 6.3 Example XML Search Area response..............................................................13 7. Search Cities in Area 15 7.1 Overview..........................................................................................................15 7.2 Example XML Search Cities in Area request...................................................15 7.3 Example XML Search Cities in Area response................................................15 8. Search Item 17 8.1 Overview..........................................................................................................17 8.2 Example XML Search Item request.................................................................17 8.3 Example XML Search Item response..............................................................18 9. Search Item Information 20 9.1 Overview..........................................................................................................20 9.2 Example XML Search Item Information request..............................................20 9.3 Example XML Search Item Information response...........................................22 9.4 Apartment Information Search Response........................................................24 9.5 Hotel Information Search Response................................................................27 9.6 Sightseeing Information Search Response.....................................................31 9.7 Transfer Information response parameters.....................................................35 10. Search Location 38 10.1 Overview........................................................................................................38 10.2 Example XML Search Location request........................................................38 10.3 Example XML Search Location response......................................................39
30-Sep-05 67096449.doc Version 2.3. Page 2 of 91
11. Search Room Type 40 11.1 Overview........................................................................................................40 11.2 Example XML Search Room Type request...................................................40 11.3 Example XML Search Room Type response.................................................41 12. Search Facility 42 12.1 Overview........................................................................................................42 12.2 Example XML Search Facility request...........................................................42 12.3 Example XML Search Facility response........................................................43 13. Search Special Event 44 13.1 Overview........................................................................................................44 13.2 The XML Example XML Search Special Event request................................44 13.3 Example XML Search Special Event response.............................................44 14. Search Meal Type 46 14.1 Overview........................................................................................................46 14.2 Example XML Search Meal Type request.....................................................46 14.3 Example XML Search Meal Type response..................................................47 15. Search Breakfast Type 48 15.1 Overview........................................................................................................48 15.2 Example XML Search Breakfast Type request..............................................48 15.3 Example XML Search Breakfast Type response...........................................49 16. Search Link 50 16.1 Overview........................................................................................................50 16.2 Example XML Search Link request...............................................................50 16.3 Example XML Search Link response.............................................................51 17. Search Remark 54 17.1 Overview........................................................................................................54 17.2 Example XML Search Remark request.........................................................54 17.3 Example XML Search Remark response.......................................................55 18. Search Essential Information 56
19. Search Transfer List 57 19.1 Overview........................................................................................................57 19.2 Example XML Search Transfer List request..................................................57 19.3 Example XML Search Transfer List response...............................................58 20. Search Airport 59 20.1 Overview........................................................................................................59 20.2 Example XML Search Airport request...........................................................59 20.3 Example XML Search Airport response.........................................................59 21. Search Station 61 21.1 Overview........................................................................................................61 21.2 Example XML Search Station request...........................................................61 21.3 Example XML Search Station response........................................................61 22. Search AOT Number 63 22.1 Overview........................................................................................................63 22.2 Example XML Search AOT Number request.................................................63
22.3 Example XML Search AOT Number response..............................................64 23. Search Special Offer 66 23.1 Overview........................................................................................................66 23.2 Example XML Search Special Offer Request................................................66 23.3 Example XML Search Special Offer response.............................................67 24. Search Car Suppliers 25. Search Car Locations 26. Search Car Location Information 70 71 72
27. Search Recommended Item 73 27.1 Overview........................................................................................................73 27.2 Example XML Search Recommended Item request.....................................73 27.3 Example XML Search Recommended Item response...................................74 28. Search Car Supplier Information 29. Search Car Supplier Link Information 30. ACRISS CODE 76 77 78
31. Search Sightseeing Type 79 31.1 Overview........................................................................................................79 31.2 Example XML Search Sightseeing Type Request.........................................79 31.3 Example XML Search Sightseeing Type response.......................................79 32. Search Sightseeing Category 81 32.1 Overview........................................................................................................81 32.2 Example XML Search Sightseeing Category request...................................81 32.3 Example XML Search Sightseeing Category response.................................81 33. Search Hotel Group 83 33.1 Overview....................................................................................................83 33.2 Example XML Search Hotel Group request..............................................83 33.3 Example XML Search Hotel Group response................................................84 34. Item Information Download 86 34.1 Overview........................................................................................................86 34.2 Example XML Item Information Download request.......................................86
30-Sep-05 67096449.doc
1. Introduction
1.1 Overview
It is intended to make the GTA search and booking facilities available to registered clients through an XML based interface. To achieve this an Application Programming Interface (API) will be provided to allow various types of client systems to integrate with the GTA system using a set of published XML messages defined using the XML Schema standards.
1.2 Purpose of this document

The purpose of this document is to outline the static data that will be made available through the API.
1.3 The API Architecture document

Please refer to the API Architecture document for details on common XML message processing including message authentication and message modes.
30-Sep-05 67096449.doc
2. Static Data
2.1 Overview
Some data changes infrequently and can therefore be cached locally by the API Client in order to meet the required traffic-to-book ratio. The following types of static data will be needed to make other types of XML request (e.g. a Hotel Information request):
Static Data Type Countries Cities Hotels
Examples Australia or Romania. London or Boston Olympia or Marriott
It is expected that client systems will retrieve all static data, cache it locally and refresh it regularly.
2.2 Codes recognised by the API

Many of the parameters required within XML requests made to the API will initially be unknown to the clients systems. To overcome this issue, the API will make available various static data requests through which the corresponding codes will be supplied. For example if a client requests a city search (for a particular country), they will be returned a list of city codes along with their respective city names. When required, it will be these city codes that must be used as part of any future XML request such as a hotel search for a city.
30-Sep-05 67096449.doc
3. Search Currency
3.1 Overview
The Search Currency provides the client with static data relating to currencies held within the GTA system. The API will provide a currency name along with the unique ISO code to identify the currency.
3.2 Example XML Search Currency request

The XML message below gives a sample of the expected elements needed by the API to execute a Search Currency Request.
<?xml version="1.0" encoding="UTF-8"?> <Request> <Source> <RequestorID Client="123456" EMailAddress="clientName@client.co.uk" Password="clientPassword" /> <RequestorPreferences> <RequestMode>SYNCHRONOUS</RequestMode> </RequestorPreferences> </Source> <RequestDetails> <SearchCurrencyRequest> <CurrencyName><![CDATA[A]]></CurrencyName> </SearchCurrencyRequest> </RequestDetails> </Request>
3.2.1 Source parameters

Please refer to the API Architecture document.
3.2.2 Search Currency attributes/parameters

A Search Currency request can contain optional attributes/parameters to filter the currencies returned. However, if none are specified a request for all currencies will be executed. The request can contain the following optional attributes/parameters: Parameter CurrencyName CurrencyCode
ISO 3166 format, 2 letter
Description If specified all currencies containing the given characters will be returned. Note: Currency Name searches are not case sensitive. If specified the currency details for the single code will be returned.
3.3 Example XML Search Currency response

The XML message below gives a sample of that given by the API in response to a Currency Search Request.
30-Sep-05 67096449.doc
<?xml version="1.0" encoding="UTF-8"?> <Response ResponseReference="200002"> <ResponseDetails Language="en"> <SearchCurrencyResponse> <CurrencyDetails> <Currency Code="ARS"><![CDATA[Argentine Peso]]></Currency> <Currency Code="AUD"><![CDATA[Australian Dollar]]></Currency> </CurrencyDetails> </SearchCurrencyResponse> </ResponseDetails> </Response>
3.3.1 Search Currency response parameters

A Search Currency response will return the following for each currency found for the request parameters: Parameter Currency Description The currency name. In the language requested (if available). Attribute Description Code The ISO code for the currency.
30-Sep-05 67096449.doc
4. Search Country
4.1 Overview
The Search Country provides the client with static data relating to countries held within the GTA system. The API will provide a country name along with the unique code used by GTA to identify the country.
4.2 Example XML Search Country request

The XML message below gives a sample of the expected elements needed by the API to execute a Search Country Request.
<?xml version="1.0" encoding="UTF-8"?> <Request> <Source> <RequestorID Client="123456" EMailAddress="clientName@client.co.uk" Password="clientPassword" /> <RequestorPreferences Language="en"> <RequestMode>SYNCHRONOUS</RequestMode> </RequestorPreferences> </Source> <RequestDetails> <SearchCountryRequest> <CountryName><![CDATA[GREE]]></CountryName> </SearchCountryRequest> </RequestDetails> </Request>

4.2.2 Search Country attributes/parameters

A Search Country request can contain optional attributes/parameters to filter the countries returned. However, if none are specified a request for all countries will be executed. The request can contain the following optional attributes/parameters: Attribute ISO Description Used to determine if ISO Codes will be processed. If true or not specified, CountryCode attribute below and the Code returned in the response parameters must be ISO 3166 format, 2 letters. If false the GTA coding will be used. Description If specified all countries containing the given characters will be returned. Note: Country Names are not case sensitive.
Parameter CountryName
CountryCode
30-Sep-05 67096449.doc
If specified the country details for the single code will be

returned.
4.3 Example XML Search Country response

The XML message below gives a sample of that given by the API in response to a Search Country Request.
<?xml version="1.0" encoding="UTF-8"?> <Response ResponseReference="200003"> <ResponseDetails Language="en"> <SearchCountryResponse> <CountryDetails> <Country Code="GR"><![CDATA[Greece]]></Country> <Country Code="GZ"><![CDATA[Greenland]]></Country> </CountryDetails> </SearchCountryResponse> </ResponseDetails> </Response>
4.3.1 Search Country response parameters

A Search Country response will return the following for each country found for the request parameters: Parameter Country Description The country name. In the language requested (if available). Attribute Description Code Either the country ISO Code or unique code held by GTA
30-Sep-05 67096449.doc
5. Search City
5.1 Overview
The Search City provides the client with static data relating to cities held within the GTA system. The API will provide a city name along with the unique code used by GTA to identify the city.
5.2 Example XML Search City request

The XML message below gives a sample of the expected elements needed by the API to execute a Search City Request.
<?xml version="1.0" encoding="UTF-8"?> <Request> <Source> <RequestorID Client="123456" EMailAddress="clientName@client.co.uk" Password="clientPassword" /> <RequestorPreferences Language="en"> <RequestMode>SYNCHRONOUS</RequestMode> </RequestorPreferences> </Source> <RequestDetails> <SearchCityRequest CountryCode="GR"> <CityName><![CDATA[AM]]></CityName> </SearchCityRequest> </RequestDetails> </Request>

5.2.2 Search City attributes

A Search City request can contain optional attributes/parameters to filter the cities returned. The following lists the attributes/parameters that can be specified: Attribute ISO Description Used to determine if ISO Codes will be processed. If true or not specified, CountryCode attribute below and the CountryCode returned in the response parameters must be ISO 3166 format, 2 letters. If false the GTA coding will be used. Mandatory. Used to return all cities within the specified country. Description Optional. If specified all cities containing the given characters will be returned. Note: City Names are not case sensitive. Optional. If specified the city details for the single code will be returned. N.b. city codes always use GTA coding.
CountryCode
Parameter CityName CityCode
30-Sep-05 67096449.doc
5.3 Example XML Search City response

The XML message below gives a sample of that given by the API in response to a Search City Request.
<?xml version="1.0" encoding="UTF-8"?> <Response ResponseReference="200004"> <ResponseDetails Language="en"> <SearchCityResponse CountryCode="GR"> <CityDetails> <City Code="AMKI"><![CDATA[Ambelakia]]></City> <City Code="AMFI"><![CDATA[Amfissa]]></City> <City Code="AMOG"><![CDATA[Amorgos]]></City> <City Code="AMPH"><![CDATA[Amphipolis]]></City> </CityDetails> </SearchCityResponse> </ResponseDetails> </Response>
5.3.1 Search City response attributes and parameters

The following attributes can form part of the <SearchCityResponse> parameter: Attribute ISO CountryCode Description Echoed backed if entered in the request. As entered in the request.
The response will then return the following for each city found for the request parameters: Parameter City Description The city name. In the language requested (if available). Attribute Description Code The unique code held by GTA
30-Sep-05 67096449.doc
6. Search Area
6.1 Overview
All requests will need to be sent in a SYNCHRONOUS mode; any requests sent in an ASYNCHRONOUS mode will return an error. The Search Area provides the client with static data relating to areas held within the GTA system. The API will provide an area name along with the unique code used by GTA to identify the area.
6.2 Example XML Search Area request

The XML message below gives a sample of the expected elements needed by the API to execute a Search Area Request.
<?xml version="1.0" encoding="UTF-8"?> <Request> <Source> <RequestorID Client="123456" EMailAddress="clientName@client.co.uk" Password="clientPassword" /> <RequestorPreferences Language="en"> <RequestMode>SYNCHRONOUS</RequestMode> </RequestorPreferences> </Source> <RequestDetails> <SearchAreaRequest> <AreaName><![CDATA[BE]]></AreaName> </SearchAreaRequest> </RequestDetails> </Request>

6.2.2 Search Area parameters

A Search Area request can contain optional parameters to filter the areas returned: Parameter AreaName AreaCode Description Optional. If specified all areas containing the given characters will be returned. Note: Area Names are not case sensitive. Optional. If specified the area details for the single code will be returned. N.b. area codes always use GTA coding.
6.3 Example XML Search Area response

The XML message below gives a sample of that given by the API in response to a Search Area Request.
30-Sep-05 67096449.doc
<?xml version="1.0" encoding="UTF-8"?> <Response ResponseReference="200004"> <ResponseDetails Language="en"> <SearchAreaResponse> <AreaDetails> <Area Code="ABZ"><![CDATA[Aberdeen & Region]]></Area> <Area Code="BEL"><![CDATA[Belfast & Region]]></Area> </AreaDetails> </SearchAreaResponse> </ResponseDetails> </Response>
6.3.1 Search Area response parameters

A Search Area response will return the following for each area found for the request parameters: Parameter Area Description The area name. In the language requested (if available). Attribute Description Code The unique code held by GTA
30-Sep-05 67096449.doc
7. Search Cities in Area

7.1 Overview
The Search Cities in Area provides the client with static data relating to cities within an area held within the GTA system. The API will provide a list of cities and their corresponding names for the area code provided.
7.2 Example XML Search Cities in Area request

The XML message below gives a sample of the expected elements needed by the API to execute a Search Cities in Area Request.
<?xml version="1.0" encoding="UTF-8"?> <Request> <Source> <RequestorID Client="123456" EMailAddress="clientName@client.co.uk" Password="clientPassword" /> <RequestorPreferences Language="en"> <RequestMode>SYNCHRONOUS</RequestMode> </RequestorPreferences> </Source> <RequestDetails> <SearchCitiesInAreaRequest AreaCode="AMS"> <CityName><![CDATA[DAM]]></CityName> </SearchCitiesInAreaRequest> </RequestDetails> </Request>

7.2.2 Search City attributes

A Search Cities in Area request can contain optional attributes/parameters to filter the city list returned. The following lists the attributes/parameters that can be specified: Attribute AreaCode Parameter CityName CityCode Description Mandatory. Used to return all cities within the specified area. Description Optional. If specified all cities containing the given characters will be returned. Note: City Names are not case sensitive. Optional. If specified the city details for the single code will be returned. N.b. city codes always use GTA coding.
7.3 Example XML Search Cities in Area response

The XML message below gives a sample of that given by the API in response to a Search Cities in Area Request.
30-Sep-05 67096449.doc
<?xml version="1.0" encoding="UTF-8"?> <Response ResponseReference="200004"> <ResponseDetails Language="en"> <SearchCitiesInAreaResponse AreaCode="AMS"> <CityDetails> <City Code="AMS"><![CDATA[Amsterdam]]></City> <City Code="RTM"><![CDATA[Rotterdam]]></City> </CityDetails> </SearchCitiesInAreaResponse> </ResponseDetails> </Response>
7.3.1 Search Cities in Area response parameters

The following attributes can form part of the <SearchCitiesInAreaResponse> parameter: Attribute AreaCode Description As entered in the request.
The response will then return the following for each city found for the request parameters: Parameter City Description The city name. In the language requested (if available). Attribute Description Code The unique code held by GTA
30-Sep-05 67096449.doc
8. Search Item
8.1 Overview
All requests will need to be sent in a SYNCHRONOUS mode; any requests send in an ASYNCHRONOUS mode will return an error. The Search Item provides the client with static data relating to apartment, hotel and sightseeing items held within the GTA system. The API will provide an item description along with the unique code used by GTA to identify the item.
8.2 Example XML Search Item request

The XML message below gives a sample of the expected elements needed by the API to execute a Search Item Request for hotels.
<?xml version="1.0" encoding="UTF-8"?> <Request> <Source> <RequestorID Client="123456" EMailAddress="clientName@client.co.uk" Password="clientPassword" /> <RequestorPreferences Language="en"> <RequestMode>SYNCHRONOUS</RequestMode> </RequestorPreferences> </Source> <RequestDetails> <SearchItemRequest ItemType="hotel"> <ItemDestination DestinationType="city" DestinationCode="AMS" /> <ItemName>AP</ItemName> </SearchItemRequest> </RequestDetails> </Request>

8.2.2 Search Item attributes/parameters

A Search Item request can contain optional attributes/parameters to filter the items returned. The following lists the attributes/parameters that can be specified: Attribute ItemType Description Mandatory. Identifies the type of item being processed. Must be one of apartment, hotel or sightseeing or transfer Description Mandatory. Used to return all items within the specified destination type (area or city) and destination code. Optional. Used to return all items within the specified location code. Optional. If specified all items containing the given characters will be returned. Note: Item names are not case sensitive. Optional. If specified the details for the single code will be returned.
Parameters ItemDestination LocationCode ItemName ItemCode

30-Sep-05 67096449.doc
8.3 Example XML Search Item response

The XML message below gives a sample of that given by the API in response to a Search Item Request.
<?xml version="1.0" encoding="UTF-8"?> <Response ResponseReference="200005"> <ResponseDetails Language="en"> <SearchItemResponse ItemType="hotel"> <ItemDetails> <ItemDetail> <City Code="AMS"><![CDATA[Amsterdam]]></City> <Item Code="APP"><![CDATA[Apple Inn]]></Item> <LocationDetails> <Location Code="G2"><![CDATA[Central]]></Location> </LocationDetails> </ItemDetail> <ItemDetail> <City Code="AMS"><![CDATA[Amsterdam]]></City> <Item Code="MER3"><![CDATA[Meridien Apollo]]></Item> <LocationDetails> <Location Code="G2"><![CDATA[Central]]></Location> </LocationDetails> </ItemDetail> </ItemDetails> </SearchItemResponse> </ResponseDetails> </Response>
8.3.1 Search Item response parameters

Attribute ItemType Description Identifies the type of item being processed. Will be apartment, hotel , sightseeing or transfer.
A Search Item response will return the following for each item found for the request parameters: Parameter City Description The city name. In the language requested (if available). Attribute Description Code The unique city code held by GTA The item name. Attribute Description Code The unique item code held by GTA A list of locations held for the item (see below).
Item
LocationDetails
8.3.2 LocationDetails parameters

Location The location name. In the language requested (if available). Attribute Description Code The unique location code held by GTA
30-Sep-05 67096449.doc
30-Sep-05 67096449.doc
9. Search Item Information

9.1 Overview
The Search Item Information provides the client with varying levels of static information relating to apartment, hotel and sightseeing items held within the GTA system. The client will be allowed to request various bundles of pre-defined information by specifying the appropriate parameters.
9.2
Example XML Search Item Information request

The XML message below gives a sample of the expected elements needed by the API to execute a Search Item Information Request for hotels.
<?xml version="1.0" encoding="UTF-8"?> <Request> <Source> <RequestorID Client="123456" EMailAddress="clientName@client.co.uk" Password="clientPassword" /> <RequestorPreferences Language="en"> <RequestMode>ASYNCHRONOUS</RequestMode> </RequestorPreferences> </Source> <RequestDetails> <SearchItemInformationRequest ItemType="hotel"> <ItemDestination DestinationType="city" DestinationCode="AMS" /> <ItemName>APO</ItemName> </SearchItemInformationRequest> </RequestDetails> </Request>

9.2.2 Search Item Information attributes/parameters

A Search Item request can contain optional attributes/parameters to filter the items returned. The following list the attributes/parameters that can be specified: Attribute ItemType Description Mandatory. Identifies the type of item being processed. Must be one of apartment, hotel or sightseeing or transfer. Description Mandatory. Used to return all items within the specified destination type (area or city) and destination code. Optional. Used to return all items within the specified location code. Optional. If specified all items containing the given characters will be returned. Note: Item names are not case sensitive. Mandatory for SYNCHRONOUS requests. Optional for ASYNCHRONOUS requests. If specified the details for the single code will be returned.
Parameters ItemDestination LocationCode ItemName ItemCode
30-Sep-05 67096449.doc
9.2.3 Search Apartment Information sub-parameters

If the item type specified is apartment, then the following optional search parameters can be specified: Parameter StarRating Description Optional. Defines the star rating of the hotel. A match or a minimum value can be specified. Attribute MinimumRating Description If set to true it will return all hotels for the specified star rating and higher. If set to false or omitted will return all hotels for the specified star rating only. Used to return all apartment items that offer the specified facility(s).
FacilityCodes
9.2.4 Search Hotel Information sub-parameters

If the item type specified is hotel, then the following optional search parameters can be specified: Parameter StarRating Description Optional. Defines the star rating of the hotel. A match or a minimum value can be specified. Attribute MinimumRating Description If set to true it will return all hotels for the specified star rating and higher. If set to false or omitted will return all hotels for the specified star rating only. Used to return all hotel items that offer the specified facility(s).
FacilityCodes
9.2.5 Search Sightseeing Information sub-parameters

If the item type specified is sightseeing, then the following optional search parameters can be specified: Parameter TypeCodes TypeCode CategoryCode DateRange Description Optional. Can contain one or several TypeCode elements. Optional. If specified only sightseeing tours that match the selected type code will be returned. Optional. If specified only sightseeing tours that match the selected category code will be returned. The FromDate and ToDate for the sightseeing item.
9.2.6 Search Transfer Information sub-parameters None.
30-Sep-05 67096449.doc
9.3
Example XML Search Item Information response

Note The API will be responsible for the level of information returned to the client. This will be determined as part of the contractual agreement with GTA and subsequently set up as system parameters within the GTA system. The XML message below gives a sample of that given by the API in response to a Search Item Information Response.
<?xml version="1.0" encoding="UTF-8"?> <Response ResponseReference="200005"> <ResponseDetails Language="en"> <SearchItemInformationResponse ItemType="hotel"> <ItemDetails> <ItemDetail> <City Code="AMS"><![CDATA[Amsterdam]]></City> <Item Code="APP"><![CDATA[Apple Inn]]></Item> <LocationDetails> <Location Code="G2"><![CDATA[Central]]> </Location> </LocationDetails> <HotelInformation> <AddressLines> <AddressLine1><![CDATA[KONINGINNEWEG 93]]></AddressLine1> <AddressLine2><![CDATA[1075 CJ AMSTERDAM]]></AddressLine2> <AddressLine3><![CDATA[NETHERLAND]]></AddressLine3> <Telephone><![CDATA[31-20-6627894]]></Telephone> <Fax><![CDATA[31-20-6755235]]></Fax> <EmailAddress><![CDATA[info@apple-inn.nl]]></EmailAddress> <WebSite><!{CDATA[www.apple-inn.nl]]></WebSite> </AddressLines> <StarRating>2</StarRating> <Reports> <Report Type="location"><![CDATA[Located in an exclusive residential area in the south of Amsterdam, 12 minutes walk to the Museumplein and Leidseplein.]]></Report> </Reports> <Facilities> <Facility Code="*LS"><![CDATA[Small sized lobby]]></Facility> <Facility Code="*EC"><![CDATA[Earliest check-in]]></Facility> </Facilities> </HotelInformation> </ItemDetail> <ItemDetail> <City Code="AMS"><![CDATA[Amsterdam]]></City> <Item Code="MER3"><![CDATA[Meridien Apollo]]></Item> <LocationDetails> <Location Code="G2"><![CDATA[Central]]> </Location> </LocationDetails> <HotelInformation> <AddressLines> <AddressLine1><![CDATA[APOLLOLAAN 2]]></AddressLine1> <AddressLine2><![CDATA[NL 1077 AMSTERDAM]]></AddressLine2> <AddressLine3><![CDATA[NETHERLANDS]]></AddressLine3> <Telephone><![CDATA[31-20-6627544]]></Telephone> <Fax><![CDATA[31-20-6754535]]></Fax> <EmailAddress><![CDATA[info@gt.com]]></EmailAddress> <WebSite><!{CDATA[http://www.gt.com/]]></WebSite> </AddressLines> <StarRating>2</StarRating> <Reports> <Report Type="location"><![CDATA[Located in an exclusive residential area in the south of Amsterdam, 12 minutes walk to the Museumplein and Leidseplein.]]> </Report> <Report Type="exterior"><![CDATA[A traditional building, built in 1899.]]> </Report> </Reports> <Facilities> <Facility Code="*LS"><![CDATA[Medium sized lobby]]></Facility> <Facility Code="*EC"><![CDATA[Check-in at 14:00]]></Facility> <Facility Code="*PT"><![CDATA[Porterage 24 hour]]></Facility> <Facility Code="*RS"><![CDATA[Rooms service 24 hour]]></Facility> <Facility Code="*CP"><![CDATA[CarParking]]></Facility> <Facility Code="*SH"><![CDATA[Shop]]></Facility> 30-Sep-05 67096449.doc Version 2.3. Page 22 of 91
<Facility Code="*CR"><![CDATA[Car Rental]]></Facility> <Facility Code="*BS"><![CDATA[Baby sitting]]></Facility> <Facility Code="*LY"><![CDATA[Laundry facilities]]></Facility> <Facility Code="*BQ"><![CDATA[Boutique]]></Facility> </Facilities> </HotelInformation> </ItemDetail> </ItemDetails> </SearchItemInformationResponse> </ResponseDetails> </Response>
9.3.1 Search Item Information response standard attributes/parameters

Attribute ItemType Description Identifies the type of item being processed. Will be apartment, hotel, sightseeing or transfer.
A Search Item Information response will return the following for each item found for the request parameters: Parameter City Description The city name. In the language requested (if available). Attribute Description Code The unique city code held by GTA The item name. Attribute Description Code The unique item code held by GTA A list of locations held for the item (see below).
Item
LocationDetails
The standard item parameters will be followed by the corresponding detailed item information: Item type Apartment Hotel Sightseeing Transfer Parameter ApartmentInformation (see corresponding section) HotelInformation (see corresponding section) SightseeingInformation (see corresponding section) TransferInformation (see corresponding section)
9.3.2 LocationDetails parameters

Location The location name. In the language requested (if available). Attribute Description Code The unique location code held by GTA
30-Sep-05 67096449.doc
9.4
Apartment Information Search Response
9.4.1 Address Lines

The Address Details will be held within the <AddressLines> parameter and can contain up to six lines of detail. The following gives a sample of the XML to be returned.
<AddressLines> <AddressLine1><![CDATA[129-131 BLD HAUSSMANN]]></AddressLine1> <AddressLine2><![CDATA[F-75008X]]></AddressLine2> <AddressLine3><![CDATA[PARIS]]></AddressLine3> <AddressLine4><![CDATA[FRANCE]]></AddressLine4> <Telephone><![CDATA[32-1-6627894]]></Telephone> <Fax><![CDATA[33-1-6755235]]></Fax> <EmailAddress><![CDATA[info@hotel.com]]></EmailAddress> <WebSite><![CDATA[www.abc-hotel.com]]></WebSite> </AddressLines>
Parameter AddressLine1 to 4 Telephone Fax EmailAddress WebSite
Description The address line(s). The telephone number of the apartment. The fax number of the apartment. The email address of the apartment The website of the apartment
9.4.2 Star Rating

The apartment star rating will be held within the <StarRating> parameter. The following gives a sample of the XML to be returned.
<StarRating>2</StarRating>
9.4.3 Category
The apartment category will be held within the <Category> parameter. The following gives a sample of the XML to be returned.
<Category><![CDATA[Grade 4 Apartment]]> </Category>
9.4.4 Area Details

The following area details could be included within the Apartment Area Details: Distance to Airport(s) Distance to Metro Distance to the beach Distance to Station Distance to Bus Stop Distance to Fair Site The Area Details will be held within the <AreaDetails> parameter and each occurrence of area detail to be reported will be held within its own <AreaDetail> parameter. The following gives a sample of the XML to be returned.
<AreaDetails> <AreaDetail><![CDATA[Location: Central]]></AreaDetail> <AreaDetail><![CDATA[25 kms to the airport (london heathrow)]]></AreaDetail> <AreaDetail><![CDATA[60 kms to the airport (london Gatwick)]]></AreaDetail> <AreaDetail><![CDATA[4 minute walk to the nearest metro station (greenpark)]]></AreaDetail> <AreaDetail><![CDATA[2 km to the nearest station (Victoria)]]></AreaDetail> <AreaDetail><![CDATA[1 minute walk to the nearest bus stop)]]></AreaDetail> </AreaDetails>
9.4.5 Apartment Units

The Apartment Units will be held within the <ApartmentUnits> parameter and each occurrence of an accommodation type will be held within its own <ApartmentUnit> parameter. The following gives a sample of the XML to be returned.
<ApartmentUnits> <ApartmentUnit Code="SB" Sleeps="2"> <ApartmentUnitName><![CDATA[Studio - Standard]]></ApartmentUnitName> <ApartmentUnitRooms> <UnitRoom Code="DB" Quantity="1"><![CDATA[Double]]></UnitRoom> </ApartmentUnitRooms> <ApartmentUnitFacilities> <Facility Code="*AC"><![CDATA[Air conditioning]]></Facility> <Facility Code="*TV"><![CDATA[TV]]></Facility> <Facility Code="*LD"><![CDATA[Laundry]]></Facility> </ApartmentUnitFacilities> </ApartmentUnit> </ApartmentUnits>
Atribute Code Sleeps Parameter ApartmentUnitName ApartmentUnitRooms ApartmentUnitFacilities
Description The unique apartment unit code held by GTA The maximum occupancy. Description The apartment unit name. In the language requested (if available). The room make up for the apartment unit. The facilities available for the apartment unit.
9.4.6 Reports
The following report types could be included within the Apartment Reports: Location Exterior Lobby Accom General Key Drop Direction The Report Details will be held within the <Reports> parameter and each occurrence of a report will be held within its own <Report> parameter. The following gives a sample of the XML to be returned.
<Reports> <Report Type="location"><![CDATA[The hotel is located in a lively and elegant area on the famous Boulevard Haussman, home to the famous department stores and close to the Opera and Champs Elysees. It is 2 minutes walk from the nearest metro station.]]></Report> <Report Type="exterior"><![CDATA[The building is a large, traditional Parisian town house, in keeping with the architecture of the surrounding area.]]></Report> <Report Type="lobby"><![CDATA[The lobby is bright and cheerful, with modern decoration, attractive wood panelled walls and colourful plants.]]></Report> <Report Type="accom"><![CDATA[The apartments and studios are in good condition. They are 30-Sep-05 67096449.doc Version 2.3. Page 25 of 91
bright, and tastefully decorated in classic style. The kitchenettes are modern and well equipped with oven, microwave and a dishwasher. A homely feel has been created with comfortable furniture, attractive drapes and paintings on the walls.]]></Report> <Report Type="general"><![CDATA[This is a 4 star residence and a good first class property. The apartments are very pleasant and offer a comfortable stay in a good location in Paris.(]]></Report> </Reports>
Attribute Type
Description The type of Apartment Report.
The KeyDrop report should not be displayed within the apartment information, but only on the voucher as the phone number advised should not be used by for any other purpose.
9.4.7 Facilities
The Apartment Facilities will be held within the <Facilities> parameter and each occurrence of a apartment facility will be held within its own <Facility> parameter. The following gives a sample of the XML to be returned.
<Facilities> <Facility Code="*LS"><![CDATA[Medium sized lobby]]></Facility> <Facility Code="*CP"><![CDATA[CarParking]]></Facility> <Facility Code="*SH"><![CDATA[Shop]]></Facility> <Facility Code="*LY"><![CDATA[Laundry facilities]]></Facility> <Facility Code="*BQ"><![CDATA[Boutique]]></Facility> </Facilities>
Attribute Code
Description The facility code held by GTA.
9.4.8 Links
The Apartment Links will be held within the <Links> parameter which can contain subparameters for map and image links. The following gives a sample of the XML to be returned. See Search Link for details.
<Links> <MapLinks> <MapLink><![CDATA[http://maps-dynamic.imageserver.com/maps.asp? SITEID=8&CTY=AMS&PANITM=ACC&COID=2&CAT=HOT ]]></MapLink> </MapLinks> <ImageLinks> <ImageLink Height="214" Width="360"> <Text><![CDATA[Exterior]]></Text> <ThumbNail><![CDATA[ http://images.is.com/HH/.jpg]]></ThumbNail> <Image><![CDATA[ http://images.is.com/HH/Nonchain/amsapp01.jpg]]> </Image> </ImageLink> </ImageLinks> <Links>
9.4.9 Important Notes

Any important notes will be held within the <ImportantNotes> parameter and each occurrence of an important note will be held within its own <ImportantNote> parameter. The following gives a sample of the XML to be returned.
<ImportantNotes> <ImportantNote><![CDATA[ Check In Days - Saturday/Sunday]]></ImportantNote> <ImportantNote><![CDATA[ Check Out Days - Monday]]></ImportantNote> <ImportantNote><![CDATA[ Car essential]]></ImportantNote> </ImportantNotes> 30-Sep-05 67096449.doc Version 2.3. Page 26 of 91
9.5
Hotel Information Search Response
9.5.1 Address Lines

The Address Details will be held within the <AddressLines> parameter and can contain up to six lines of detail. The following gives a sample of the XML to be returned.
<AddressLines> <AddressLine1><![CDATA[KONINGINNEWEG 93]]></AddressLine1> <AddressLine2><![CDATA[1075 CJ]]></AddressLine2> <AddressLine3><![CDATA[AMSTERDAM]]></AddressLine3> <AddressLine4><![CDATA[NETHERLAND]]></AddressLine4> <Telephone><![CDATA[32-20-6627894]]></Telephone> <Fax><![CDATA[32-20-6755235]]></Fax>
<EmailAddress><![CDATA[info@hotel.com]]></EmailAddress> <WebSite><![CDATA[www.abc-hotel.com]]></WebSite>
</AddressLines>
Parameter AddressLine1 to 4 Telephone Fax EmailAddress WebSite
Description The address line(s). The telephone number of the hotel. The fax number of the hotel. The email address of the hotel The website of the hotel
9.5.2 Star Rating

The hotel star rating will be held within the <StarRating> parameter. The following gives a sample of the XML to be returned.
<StarRating>2</StarRating>
9.5.3 Category
The hotel category will be held within the <Category> parameter. The following gives a sample of the XML to be returned.
<Category><![CDATA[3 Star, Superior Tourist Class Modern Hotel]]> </Category>
9.5.4 Area Details

The following area details could be included within the Hotel Area Details: Distance to Airport(s) Distance to Metro Distance to Station Distance to Bus Stop Distance to Fair Site The Area Details will be held within the <AreaDetails> parameter and each occurrence of area detail to be reported will be held within its own <AreaDetail> parameter. The following gives a sample of the XML to be returned.
30-Sep-05 67096449.doc
<AreaDetails> <AreaDetail><![CDATA[3 kms to city centre]]></AreaDetail> <AreaDetail><![CDATA[13 kms to the nearest airport (amsterdam)]]></AreaDetail> <AreaDetail><![CDATA[1 minute walk to the nearest metro station (rai)]]></AreaDetail> <AreaDetail><![CDATA[2 km to the nearest station (world trade centre)]]></AreaDetail> <AreaDetail><![CDATA[5 minute walk to the nearest bus stop]]></AreaDetail> <AreaDetail><![CDATA[2 km to the nearest fair site (rai)]]></AreaDetail> </AreaDetails>
9.5.5 Reports
The following report types could be included within the Hotel Reports: Location Rooms Restaurant Exterior Lobby General Apartments Inclusive Please Note The Report Details will be held within the <Reports> parameter and each occurrence of a report will be held within its own <Report> parameter. The following gives a sample of the XML to be returned.
<Reports> <Report Type="location"> <![CDATA[Located in an exclusive residential area in the south of Amsterdam, 12 minutes walk to the Museumplein and Leidseplein.]]> </Report> <Report Type="exterior"> <![CDATA[A traditional building, built in 1899.]]> </Report> </Reports>
Attribute Type
Description The type of Hotel Report.
9.5.6 Room Categories

The Room Categories will be held within the <RoomCategories> parameter and each occurrence of a hotel room category will be held within its own <RoomCategory> parameter. The following gives a sample of the XML to be returned.
<RoomCategories> <RoomCategory Id = "002:HIL1"> <Description><![CDATA[Standard]]></Description> <RoomDescription>The medium sized bedrooms are typical Hilton style with two double beds in each twin room. All the rooms were renovated in 2001 with modern furnishings in Italian style and strong, contrasting colours. The white tiled bathrooms are also in very good condition and the rooms offer all the facilities and the high standards that one would expect from a 5 star Hilton hotel.</RoomDescription> </RoomCategory> <RoomCategory Id = "002:HILTON:HL:04988:XXX:XXX:A02"> <Description><![CDATA[King Junior Suite]]></Description> </RoomCategory>
<RoomCategory Id = "002:HILTON:HL:04988:XXX:XXX:A10"> <Description><![CDATA[Standard Double]]></Description> </RoomCategory> <RoomCategory Id = "002:HILTON:HL:04988:XXX:XXX:A09"> <Description><![CDATA[Executive King]]></Description> <RoomDescription>The very large Executive King bedrooms are very comfortably furnished. There is a mini-audio system in each room. The bathrooms are fitted to a very high standard.</RoomDescription> </RoomCategory> <RoomCategory Id = "002:HILTON:HL:04988:XXX:XXX:A03"> <Description><![CDATA[Presidential Suite]]></Description> </RoomCategory> </RoomCategories>
Parameter RoomCategories RoomCategory Parameter Description RoomDescription
Description A collection of one or more RoomCategory parameters. Specifies the room category details. Attribute Description Id Specifies the category ID. Description Short description of the room category. Describes the room category. May not be returned for all categories.
The <RoomCategories> parameter is dependent on the clients Participation Level: Participation Level None Parameter is not returned Participation Level 1 Parameter is returned Participation Level 2 Parameter is returned
9.5.7 Room Types

The Room Types will be held within the <RoomTypes> parameter and each occurrence of a hotel room type will be held within its own <RoomType> parameter. The following gives a sample of the XML to be returned.
<RoomTypes RoomCount="212"> <RoomType Code="SB"><![CDATA[Single room]]></RoomType> <RoomType Code="DB"><![CDATA[Double room]]></RoomType> <RoomType Code="TB"><![CDATA[Twin room]]></RoomType> </RoomTypes>
Attribute Code
Description The room type code held by GTA.
9.5.8 Facilities
The Hotel Facilities will be held within the <Facilities> parameter and each occurrence of a hotel facility will be held within its own <Facility> parameter. The following gives a sample of the XML to be returned.
<Facilities> <Facility Code="*LS"><![CDATA[Medium sized lobby]]></Facility> <Facility Code="*EC"><![CDATA[Earliest check-in at 14:00]]></Facility> <Facility Code="*PT"><![CDATA[Porterage 24 hour]]></Facility> <Facility Code="*RS"><![CDATA[Rooms service 24 hour]]></Facility> <Facility Code="*CP"><![CDATA[CarParking]]></Facility> 30-Sep-05 67096449.doc Version 2.3. Page 29 of 91
<Facility Code="*SH"><![CDATA[Shop]]></Facility> <Facility Code="*CR"><![CDATA[Car Rental]]></Facility> <Facility Code="*BS"><![CDATA[Baby sitting]]></Facility> <Facility Code="*LY"><![CDATA[Laundry facilities]]></Facility> <Facility Code="*BQ"><![CDATA[Boutique]]></Facility> </Facilities>
Attribute Code
9.5.9 Room Facilities

The Hotel Room Facilities will be held within the <RoomFacilities> parameter and each occurrence of a hotel room facility will be held within its own <Facility> parameter. The following gives a sample of the XML to be returned.
<RoomFacilities> <Facility Code="*T1"><![CDATA[Television]]></Facility> <Facility Code="*M1"><![CDATA[In-house movie]]></Facility> <Facility Code="*D1"><![CDATA[Direct dial phone]]></Facility> <Facility Code="*H1"><![CDATA[Hairdryer]]></Facility> <Facility Code="*V1"><![CDATA[Voltage 220v]]></Facility> </RoomFacilities>
Attribute Code
9.5.10 Links
The Hotel Links will be held within the <Links> parameter which can contain subparameters for map and image links. The following gives a sample of the XML to be returned. See Search Link for details.
<Links> <MapLinks> <MapLink><![CDATA[http://maps-dynamic.imageserver.com/maps.asp? SITEID=8&CTY=AMS&PANITM=ACC&COID=2&CAT=HOT ]]></MapLink> </MapLinks> <ImageLinks> <ImageLink Height="214" Width="360"> <Text><![CDATA[Exterior]]></Text> <ThumbNail><![CDATA[ http://is.com/HH/Nonchainth/amsapp01.jpg]]> </ThumbNail> <Image><![CDATA[ http://is.com/HH/Nonchain/amsapp01.jpg]]></Image> </ImageLink> </ImageLinks> <RichMediaLinks> <RichMediaLink>http://vfmii.com/ids=77381</RichMediaLink> </RichMediaLinks> <Links>
9.5.11 GeoCodes
The GeoCodes will be held within the <GeoCodes> parameter which contains subparameters for <Latitude> and <Longitude>. The following gives a sample of the XML to be returned.
<GeoCodes> <Latitude>40.764300000000000</Latitude> <Longitude>-73.98900000000000</Longitude> </GeoCodes>
30-Sep-05 67096449.doc
9.6
Sightseeing Information Search Response
9.6.1 Tour Summary

The Tour Summary will be held within the <TourSummary> parameter. The following gives a sample of the XML to be returned.
<TourSummary> <![CDATA[A full day excursion through scenic countryside to Mount Fuji and Hakone, returning to Tokyo by bullet train.]]> </TourSummary>
9.6.2 Duration
The duration will be held within the <Duration> parameter. The following gives a sample of the XML to be returned.
<Duration><![CDATA[12 hrs]]></Duration>
9.6.3 SightseeingTypes
The Types will be held within the <SightseeingTypes> parameter and each occurrence of a type will be held within its own <SightseeingType> parameter. The following gives a sample of the XML to be returned.
<SightseeingTypes> <SightseeingType Code="RS"><![CDATA[Sightseeing Tours]]></SightseeingType> <SightseeingType Code="CR"><![CDATA[Sightseeing Cruises]]></SightseeingType> </SightseeingTypes>
Parameter Description SightseeingTypes The collection of <SightseeingType> tags. SightseeingType The sightseeing type, in the language requested (if available). Attribute Description Code The unique sightseeing type code held by GTA.
9.6.4 SightseeingCategories
The Category will be held within the <SightseeingCategories> parameter and each occurrence of a type will be held within its own <SightseeingCategory> parameter. The following gives a sample of the XML to be returned.
<SigthseeingCategories> <SightseeingCategory Code="FA"><![CDATA[Fashion]]></SightseeingCategory> <SightseeingCategory Code="MU"><![CDATA[Music]]></SightseeingCategory> <SightseeingCategory Code="SP"><![CDATA[Sport]]></SightseeingCategory> </SigthseeingCategories>
Parameter Description SightseeingCategories The collection of <SightseeingCategory> tags. SightseeingCategory The sightseeing category, in the language requested (if available). Attribute Description
Code
The unique sightseeing category code held by GTA.
9.6.5 The Tour

The Tour description will be held within the <TheTour> parameter. The following gives a sample of the XML to be returned.
<TheTour><![CDATA[This tour starts with a drive through the scenic countryside to Mt. Fuji. A Western-style lunch is provided half way up the mountain at the Hotel Highland Resort. Then you will be driven on to Hakone and after that you take a cruise on Lake Ashi. We then take the Aerial Cable Way to Mount Komagatake. After a brief stop at Hotel Kowaki, the tour proceeds into Odawara to board a bullet train for Tokyo.]]></TheTour>
9.6.6 Includes
The Includes information will be held within the <Includes> parameter. The following gives a sample of the XML to be returned.
<Includes><![CDATA[Cruise on Sydney Harbour, 3 course 'a la carte dining', sparkling and still wines, beer, tea and coffee.]]></Includes>
9.6.7 Please Note

The Please Note will be held within the <PleaseNote> parameter. The following gives a sample of the XML to be returned.
<PleaseNote><![CDATA[Some walking is involved as half the tour is by luxury coach and the other half on foot.]]></ PleaseNote>
9.6.8 Departure Points

The Departure Points will be held within the <DeparturePoint> parameter. The following gives a sample of the XML to be returned.
<DeparturePoints><![CDATA[Rijksmuseum - Leidseplein - City Hall - Central Station - Anne Frank Hs./ Prinsengracht - Rijksmuseum]]></ DeparturePoints>
9.6.9 Additional Information

If Additional Information exists for the tour it will be held within the <AdditionalInformation> parameter. The following gives a sample of the XML to be returned.
<AdditionalInformation><![CDATA[Pick up from hotels can be arranged with the supplier directly. This tour is operated in air conditioned vehicles.]]></AdditionalInformation>
9.6.10 Tour Operations

The tour operating details will be held within the <TourOperations> parameter and each occurrence of a tour operation to be reported will be held within its own < TourOperation> parameter. The following gives a sample of the XML to be returned.
30-Sep-05 67096449.doc
<TourOperations> <TourOperation> <TourLanguages> <TourLanguage Code="E" LanguageListode="XE"><![CDATA[English]]> </TourLanguage> <TourLanguage Code="G" LanguageListode="XE"><![CDATA[German]]> </TourLanguage> <TourLanguage Code="K" LanguageListode="XE"><![CDATA[Korean]]> </TourLanguage> <TourLanguage Code="M" LanguageListode="XE"><![CDATA[Mandarin]]> </TourLanguage> <TourLanguage Code="S" LanguageListode="XE"><![CDATA[Spanish]]> </TourLanguage> </TourLanguages> <Commentary><![CDATA[Audio]]></Commentary> <DateRange> <FromDate>2003-01-01</FromDate> <ToDate>2003-12-31</ToDate> </DateRange> <Frequency><![CDATA[Daily]]></Frequency> <Departures> <Departure> <Time>09.00</Time> <DeparturePoint Code="XXX"> <![CDATA[Hamamatsucho Bus Terminal]]> </DeparturePoint> <AddressLines> <AddressLine1><![CDATA[Dorland House]]></AddressLine1> <AddressLine2><![CDATA[14-20 Lower Regent Street]]></AddressLine2> <AddressLine3><![CDATA[London]]></AddressLine3> <AddressLine4><![CDATA[SW1Y 4PH]]></AddressLine4> </AddressLines> <Telephone><![CDATA[44-7976-1191]]></Telephone> </Departure> </Departures> <OverrideText> <TourSummary><![CDATA[A full day excursion through scenic countryside to Mount Fuji and Hakone, returning to Tokyo by express train.]]> </TourSummary> <TheTour><![CDATA[This tour starts with a drive through the scenic countryside to Mt. Fuji. A Western-style lunch is provided half way up the mountain at the Hotel Highland Resort. Then you will be driven on to Hakone and after that you take a ruise on Lake Ashi. We then take the Aerial Cable Way to Mount Komagatake. After a brief stop at Hotel Kowaki, the tour proceeds into Odawara to board an express train for Tokyo.]]> </TheTour> <Includes><![CDATA[Cruise on Sydney Harbour, buffet lunch, sparkling and still wines, beer, tea and coffee.]]> </Includes> <PleaseNote><![CDATA[Some walking is involved and during the rainy season a rain coat and umbrella are required.]]> </PleaseNote> <DeparturePoints><![CDATA[Rijksmuseum - Leidseplein - City Hall Central Station - Rijksmuseum]]> </ DeparturePoints> <AdditionalInformation><![CDATA[Pick up from hotels is not available for this period. This tour is operated in air conditioned vehicles.]]> </AdditionalInformation> </OverrideText> </TourOperation> </TourOperations>
Parameter TourLanguages Commentary DateRange Frequency Departures OverrideText 9.6.10.1 Departures
Description A list of languages in which the tour operates. The description of the commentary. The FromDate and ToDate for the event. The frequency of the tour. The list of departures available held within a separate <Departure>. See below for further details The override text (if it exists) for the applicable date range. See below for further details.
The Departures Details will be held within the <Departure> parameters with the following choice of sub-parameters:
Parameter Time FirstService LastService Intervals DeparturePoint Description AddressLines Telephone 9.6.10.1.1 AddressLines
Description The departure time or list of departure times. The time of the first departure. The time of the last departure. At what time interval the tour runs. Attribute Description Code The GTA departure point code. Description of the departure point. See below for details The telephone number of the supplier.
The Address Details will be held within the <AddressLines> parameter and can contain up to 4 lines of detail. The following gives a sample of the XML to be returned.
<AddressLines> <AddressLine1><![CDATA[Dorland House]]></AddressLine1> <AddressLine2><![CDATA[14-20 Lower Regent Street]]></AddressLine2> <AddressLine3><![CDATA[London]]></AddressLine3> <AddressLine4><![CDATA[SW1Y 4PH]]></AddressLine4> </AddressLines>
Parameter AddressLine1 to 4 9.6.10.2 Override Text
Description The address line(s).
If any override text exists for the tour this will be held within the <OverrideText> parameter which contains sub-parameters for the individual tour information parameters (please also see sections 9.6.1, 9.6.5, 9.6.6, 9.6.7, 9.6.8 and 9.6.9). The following gives a sample of the XML to be returned.
<OverrideText> <TourSummary><![CDATA[A full day excursion through scenic countryside to Mount Fuji and Hakone, returning to Tokyo by express train.]]></TourSummary> <TheTour><![CDATA[This tour starts with a drive through the scenic countryside to Mt. Fuji. A Western-style lunch is provided half way up the mountain at the Hotel Highland Resort. Then you will be driven on to Hakone and after that you take a cruise on Lake Ashi. We then take the Aerial Cable Way to Mount Komagatake. After a brief stop at Hotel Kowaki, the tour proceeds into Odawara to board an express train for Tokyo.]]></TheTour> <Includes><![CDATA[Cruise on Sydney Harbour, buffet lunch, sparkling and still wines, beer, tea and coffee.]]></Includes> <PleaseNote><![CDATA[Some walking is involved and during the rainy season a rain coat and umbrella are required.]]></PleaseNote> <DeparturePoints><![CDATA[Rijksmuseum - Leidseplein - City Hall - Central Station Rijksmuseum]]></ DeparturePoints> <AdditionalInformation><![CDATA[Pick up from hotels is not available for this period. This tour is operated in air conditioned vehicles.]]></AdditionalInformation> </OverrideText>
9.6.11 Closed Dates

If Closed Dates exist for the tour these will be held within the <ClosedDates> parameter which contains sub-parameters for the individual dates this tour is not operating on. The following gives a sample of the XML to be returned.
<ClosedDates> <ClosedDate>2004-12-25</ClosedDate> <ClosedDate>2004-12-26</ClosedDate> <ClosedDate>2005-01-01</ClosedDate> </ClosedDates> 30-Sep-05 67096449.doc Version 2.3. Page 34 of 91
9.6.12 Link
The Sightseeing Links will be held within the <Links> parameter which can contain subparameters for image and flash links. The following gives a sample of the XML to be returned. See Search Link for details.
<Links> <ImageLinks> <ImageLink Height="270" Width="360"> <ThumbNail><![CDATA[http://images.gta-travel.com/LONBATE01GTA012.GTA01.jpg]]> </ThumbNail> <Image><![CDATA[http://images.gta-travel.com/RS/Images/GB/LONBATE01GTA012.GTA01.jpg]]> </Image> </ImageLink> </ImageLinks> <FlashLinks> <FlashLink><![CDATA[http://images.gta-travel.com/LONBATE01-GTA013.swf]]> </FlashLink> </FlashLinks> </Links>
9.7
Transfer Information response parameters
9.7.1 PickUpDetails parameters
Elements PickUp
Description The pick up name in the language requested (if available). Attribute Code Description The GTA pick up code.
Elements City, Area or Airport
Description Depending on the type of pick up, a city, area or airport name will be output in the language requested (if available). Attribute Code Description The GTA code associated with the name.
Elements PickUpPoints
Description A list of PickUpPoint held for the item.
9.7.1.1
PickUpPoints parameters
PickUpPoint
The pick up name in the language requested (if available). Attribute Code City Description The GTA pick up code. The city code where the PickUpPoint is
30-Sep-05 67096449.doc
located.
9.7.2 DropOffDetails parameters
Elements DropOff
Description The drop off name in the language requested (if available). Attribute Code Description The GTA drop off code.
Elements City, Area or Airport
Description Depending on the type of drop off, a city, area or airport name will be output in the language requested (if available). Attribute Code Description The GTA code associated with the name.
9.7.3 Approximate Transfer Time

The approximate transfer time will be held within the <ApproximateTransferTime> parameter. The following gives a sample of the XML to be returned.
<ApproximateTransferTime><![CDATA[1 hour 30 Minutes ]]></ApproximateTransferTime>
9.7.4 Links
The Transfer Links (i.e. Sightseeing Ideas) will be held within the <Links> parameter which can contain sub-parameters for flash links. The following gives a sample of the XML to be returned. See Search Link for details.
<Links> <FlashLinks> <FlashLink><![CDATA[ http://maps.mapserver.com/TN/GB/EDIAFSLDH2.swf]]> </FlashLink> <FlashLink><![CDATA[ http://maps.mapserver.com/TN/GB/EDIAFSLDH3.swf]]> </FlashLink> </FlashLinks> </Links>
9.7.5
Description
The transfer description will be held within the <Description> parameter. The following gives a sample of the XML to be returned.
<Description><![CDATA[Transfer from Edinburgh Airport to hotel with driver speaking the local language.]]></Description>
30-Sep-05 67096449.doc
9.7.6 Meeting Point

The meeting point information will be held within the <MeetingPoint> parameter. The following gives a sample of the XML to be returned.
<MeetingPoint><![CDATA[In the arrivals hall]]></MeetingPoint>
9.7.7
Transfer Conditions
The transfer conditions will be held within the <TransferConditions> parameter and each occurrence of a transfer condition to be reported will be held within its own <TransferCondition> parameter. The following gives a sample of the XML to be returned.
<TransferConditions> <TransferCondition><![CDATA[Tips are not included, these are at your discretion.]]> </TransferCondition> <TransferCondition><![CDATA[Waiting time is 1 hour after the actual arrival time. After this time the vehicle will be released.]] </TransferCondition> </TransferConditions>
9.7.8 Transfer Type

The transfer type will be held within the <TransferType> parameter. The following gives a sample of the XML to be returned.
<TransferType Code=PT><![CDATA[Private Transfer]]></TransferType>
30-Sep-05 67096449.doc
10. Search Location

10.1 Overview
The Search Location provides the client with static data relating to locations held within the GTA system. The API will provide a location name and city code along with the unique code used by GTA to identify the location.
10.2 Example XML Search Location request

The XML message below gives a sample of the expected elements needed by the API to execute a Search Location Request.
<?xml version="1.0" encoding="UTF-8"?> <Request> <Source> <RequestorID Client="123456" EMailAddress="clientName@client.co.uk" Password="clientPassword" /> <RequestorPreferences Language="en"> <RequestMode>SYNCHRONOUS</RequestMode> </RequestorPreferences> </Source> <RequestDetails> <SearchLocationRequest CityCode="HKG" /> </RequestDetails> </Request>

10.2.2 Search Location attributes/parameters

A Search Location request can contain optional attributes/parameters to filter the locations returned. The following lists the attributes/parameters that can be specified: Attribute CityCode Description Optional. Used to return all locations within the specified city or if not specified the generic locations alone will be returned (e.g. city, airport, etc.) N.B. if a city is specified, the generic locations will be returned along with any specific to that city which obviates the need to issue a separate request for the generic locations. Description Optional. If specified all locations containing the given characters will be returned. Note: Location Names are not case sensitive. Optional. If specified the location details for the single code will be returned.
Parameter LocationName LocationCode
30-Sep-05 67096449.doc
10.3 Example XML Search Location response

The XML message below gives a sample of that given by the API in response to a Search Location Request.
<?xml version="1.0" encoding="UTF-8"?> <Response ResponseReference="200015"> <ResponseDetails Language="en"> <SearchLocationResponse CityCode="HKG" > <LocationDetails> <Location Code="01"><![CDATA[Causeway Bay]]></Location> <Location Code="02"><![CDATA[North Point]]></Location> <Location Code="03"><![CDATA[Wanchai]]></Location> <Location Code="04"><![CDATA[Central/Admiralty]]></Location> <Location Code="05"><![CDATA[Sheug Wan/San Wan]]></Location> </LocationDetails> </SearchLocationResponse> </ResponseDetails> </Response>
10.3.1 Search Location response parameters

A Search Location response will return the following for each location found for the request parameters: Parameter Location Description The location name. In the language requested (if available). Attribute Description Code The unique location code held by GTA
30-Sep-05 67096449.doc
11. Search Room Type

11.1 Overview
The Search Room Types provides the client with static data relating to room types held within the GTA system. The API will provide a room type name along with the unique code used by GTA to identify the room type.
11.2 Example XML Search Room Type request

The XML message below gives a sample of the expected elements needed by the API to execute a Search Room Type Request.
<?xml version="1.0" encoding="UTF-8"?> <Request> <Source> <RequestorID Client="123456" EMailAddress="clientName@client.co.uk" Password="clientPassword" /> <RequestorPreferences Language="en"> <RequestMode>SYNCHRONOUS</RequestMode> </RequestorPreferences> </Source> <RequestDetails> <SearchRoomTypeRequest /> </RequestDetails> </Request>

11.2.2 Search Room Type parameters

A Search Room Type request can contain optional parameters to filter the countries returned. The following lists the parameters that can be specified: Parameters RoomTypeName RoomTypeCode Description Optional. If specified all room types containing the given characters will be returned. Note: Room Type Names are not case sensitive. Optional. If specified the room type details for the single code will be returned.
30-Sep-05 67096449.doc
11.3 Example XML Search Room Type response

The XML message below gives a sample of that given by the API in response to a Search Room Type Request.
<?xml version="1.0" encoding="UTF-8"?> <Response ResponseReference="200002"> <ResponseDetails Language="en"> <SearchRoomTypeResponse> <RoomTypeDetails> <RoomType Code="DB"><![CDATA[Double]]></RoomType> <RoomType Code="Q"><![CDATA[Quad]]></RoomType> <RoomType Code="SB"><![CDATA[Single]]></RoomType> <RoomType Code="TR"><![CDATA[Triple]]></RoomType> <RoomType Code="TS"><![CDATA[Twin for sole use]]></RoomType> <RoomType Code="TB"><![CDATA[Twin]]></RoomType> </RoomTypeDetails> </SearchRoomTypeResponse> </ResponseDetails> </Response>
11.3.1 Search Room Type response parameters

A Search Room Type response will return the following for each room type found for the request parameters: Parameter RoomType Description The room type name. In the language requested (if available). Attribute Description Code The unique room type code held by GTA
30-Sep-05 67096449.doc
12. Search Facility

12.1 Overview
The Search Facility provides the client with static data relating to facilities held within the GTA system. The API will provide a facility name along with the unique code used by GTA to identify the facility.
12.2 Example XML Search Facility request

The XML message below gives a sample of the expected elements needed by the API to execute a Search Facility Request.
<?xml version="1.0" encoding="UTF-8"?> <Request> <Source> <RequestorID Client="123456" EMailAddress="clientName@client.co.uk" Password="clientPassword" /> <RequestorPreferences Language="en"> <RequestMode>SYNCHRONOUS</RequestMode> </RequestorPreferences> </Source> <RequestDetails> <SearchFacilityRequest FacilityType=hotel> <FacilityName></FacilityName> <FacilityCode></FacilityCode> </SearchFacilityRequest> </RequestDetails> </Request>

12.2.2 Search Facility parameters

A Search Facility request can contain optional parameters to filter the facilities returned. The following lists the parameters that can be specified: Parameters FacilityName FacilityCode Description Optional. If specified all facilities containing the given characters will be returned. Note: Facility Names are not case sensitive. Optional. If specified the facility details for the single code will be returned. Attribute Description FacilityType Optional. Identifies the type of facility being processed. Can be one of hotel, hotelroom, apartment or apartmentunit. If not being specified hotel facilities will be returned.
30-Sep-05 67096449.doc
12.3 Example XML Search Facility response

The XML message below gives a sample of that given by the API in response to a Search Facility Request.
<?xml version="1.0" encoding="UTF-8"?> <Response ResponseReference="200002"> <ResponseDetails Language="en"> <SearchFacilityResponse FacilityType=hotel> <FacilityDetails> <Facility Code="*TE"><![CDATA[Tennis]]></ Facility > <Facility Code="*TA"><![CDATA[Travel agency facilities]]></Facility> <Facility Code="*CR"><![CDATA[Car rental facilities]]></Facility> <Facility Code="*BC"><![CDATA[Business centre]]></Facility> </FacilityDetails> </SearchFacilityResponse> </ResponseDetails> </Response>
12.3.1 Search Facility response parameters

A Search Facility response will return the following for each facility found for the request parameters: Parameter Facility Description The facility name. In the language requested (if available). Attribute Description FacilityType Identifies the type of facility being processed. Will be one of apartment, hotel, apartmentunit or hotelroom. Code The unique facility code held by GTA
30-Sep-05 67096449.doc
13. Search Special Event

13.1 Overview
The Search Special Event provides the client with static data relating to special events held within the GTA system. The API will provide a special event name along with the applicable dates for the event.
13.2 The XML Example XML Search Special Event request

The message below gives a sample of the expected elements needed by the API to execute a Search Special Event Request.
<?xml version="1.0" encoding="UTF-8"?> <Request> <Source> <RequestorID Client="123456" EMailAddress="clientName@client.co.uk" Password="clientPassword" /> <RequestorPreferences Language="en"> <RequestMode>SYNCHRONOUS</RequestMode> </RequestorPreferences> </Source> <RequestDetails> <SearchSpecialEventRequest> <ItemDestination DestinationType="city" DestinationCode="BLQ" /> <DateRange> <FromDate>2004-09-28</FromDate> <ToDate>2004-10-03</ToDate> </DateRange> </SearchSpecialEventRequest> </RequestDetails> </Request>

13.2.2 Search Special Event parameters

A Search Special Event request can contain optional attributes/parameters to filter the events returned. The following lists the attributes/parameters that can be specified: Parameters ItemDestination FromDate ToDate SpecialEventName Description Mandatory. Used to return all events within the specified destination type (area or city) and destination code. Optional. Used to return all events from the specified date. If not specified todays date will be used. Optional. Used to return all events to the specified date. If not specified all events from the FromDate will be returned. Optional. If specified all events containing the given characters will be returned. Note: Special Event Names are not case sensitive.
13.3 Example XML Search Special Event response

The XML message below gives a sample of that given by the API in response to a
Search Special Event Request.

<?xml version="1.0" encoding="UTF-8"?> <Response ResponseReference="200005"> <ResponseDetails Language="en"> <SearchSpecialEventResponse> <SpecialEventDetails> <City Code="BLQ"><![CDATA[Bologna]]></City> <DateRange> <FromDate>2004-09-28</FromDate> <ToDate>2004-10-03</ToDate> </DateRange> <Event><![CDATA[Ceramics Fair]]></Event> </SpecialEventDetail> <SpecialEventDetail> <City Code="BLQ"><![CDATA[Bologna]]></City> <DateRange> <FromDate>2004-09-22</FromDate> <ToDate>2004-10-10</ToDate> </DateRange> <Event><![CDATA[Anitique Fair]]></Event> </SpecialEventDetail> </SpecialEventDetails> </SearchSpecialEventResponse> </ResponseDetails> </Response>
13.3.1 Search Special Event response parameters

A Search Special Event response will return the following for each event found for the request parameters: Parameter City Description The city name. In the language requested (if available). Attribute Description Code The unique city code held by GTA. The FromDate and ToDate for the event. The event description.
DateRange Event
30-Sep-05 67096449.doc
14. Search Meal Type

14.1 Overview
The Search Meal Type provides the client with static data relating to meal types held within the GTA system. The API will provide a meal type name along with the unique code used by GTA to identify the meal type.
14.2 Example XML Search Meal Type request

The XML message below gives a sample of the expected elements needed by the API to execute a Search Meal Type Request.
<?xml version="1.0" encoding="UTF-8"?> <Request> <Source> <RequestorID Client="123456" EMailAddress="clientName@client.co.uk" Password="clientPassword" /> <RequestorPreferences Language="en"> <RequestMode>SYNCHRONOUS</RequestMode> </RequestorPreferences> </Source> <RequestDetails> <SearchMealTypeRequest /> </RequestDetails> </Request>

14.2.2 Search Meal Type parameters

A Search Meal Type request can contain optional parameters to filter the meal types returned. The following lists the parameters that can be specified: Parameters MealTypeName MealTypeCode Description Optional. If specified all meal types containing the given characters will be returned. Note: Meal Type Names are not case sensitive. Optional. If specified the meal type details for the single code will be returned.
30-Sep-05 67096449.doc
14.3 Example XML Search Meal Type response

The XML message below gives a sample of that given by the API in response to a Search Meal Type Request.
<?xml version="1.0" encoding="UTF-8"?> <Response ResponseReference="200002"> <ResponseDetails Language="en"> <SearchMealTypeResponse> <MealTypeDetails> <MealType Code="B"><![CDATA[Breakfast]]></MealType> <MealType Code="D"><![CDATA[Breakfast and dinner]]></MealType> <MealType Code="F"><![CDATA[Breakfast, lunch and dinner]]></MealType> <MealType Code="L"><![CDATA[Breakfast and lunch]]></MealType> </MealTypeDetails> </SearchMealTypeResponse> </ResponseDetails> </Response>
14.3.1 Search Meal Type response parameters

A Search Meal Type response will return the following for each meal type found for the request parameters: Parameter MealType Description The meal name. In the language requested (if available). Attribute Description Code The unique meal type code held by GTA
30-Sep-05 67096449.doc
15. Search Breakfast Type

15.1 Overview
The Search Breakfast Type provides the client with static data relating to breakfast types held within the GTA system. The API will provide a breakfast type name along with the unique code used by GTA to identify the breakfast type.
15.2 Example XML Search Breakfast Type request

The XML message below gives a sample of the expected elements needed by the API to execute a Search Breakfast Type Request.
<?xml version="1.0" encoding="UTF-8"?> <Request> <Source> <RequestorID Client="123456" EMailAddress="clientName@client.co.uk" Password="clientPassword" /> <RequestorPreferences Language="en"> <RequestMode>SYNCHRONOUS</RequestMode> </RequestorPreferences> </Source> <RequestDetails> <SearchBreakfastTypeRequest /> </RequestDetails> </Request>

15.2.2 Search Breakfast Type parameters

A Search Breakfast Type request can contain optional parameters to filter the breakfast types returned. The following lists the parameters that can be specified: Parameters Description BreakfastTypeName Optional. If specified all breakfast types containing the given characters will be returned. Note: Breakfast Type Names are not case sensitive. BreakfastTypeCode Optional. If specified the breakfast type details for the single code will be returned.
30-Sep-05 67096449.doc
15.3 Example XML Search Breakfast Type response

The XML message below gives a sample of that given by the API in response to a Search Breakfast Type Request.
<?xml version="1.0" encoding="UTF-8"?> <Response ResponseReference="200002"> <ResponseDetails Language="en"> <SearchBreakfastTypeResponse> <BreakfastTypeDetails> <BreakfastType Code="A"><![CDATA[American]]></BreakfastType> <BreakfastType Code="B"><![CDATA[Cold buffet]]></BreakfastType> <BreakfastType Code="C"><![CDATA[Continental]]></BreakfastType> <BreakfastType Code="E"><![CDATA[English]]></BreakfastType> </BreakfastTypeDetails> </SearchBreakfastTypeResponse> </ResponseDetails> </Response>
15.3.1 Search Breakfast Type response parameters

A Search Breakfast Type response will return the following for each breakfast type found for the request parameters: Parameter BreakfastType Description The breakfast name. In the language requested (if available). Attribute Description Code The unique breakfast type code held by GTA
30-Sep-05 67096449.doc
16. Search Link

16.1 Overview
The Search Link provides the client with static data relating to links to other information for an item, such as maps and images. The API will provide links held within the GTA system.
16.2 Example XML Search Link request

The XML message below gives a sample of the expected elements needed by the API to execute a Search Link Request for hotels.
<?xml version="1.0" encoding="UTF-8"?> <Request> <Source> <RequestorID Client="123456" EMailAddress="clientName@client.co.uk" Password="clientPassword" /> <RequestorPreferences Language="en"> <RequestMode>SYNCHRONOUS</RequestMode> </RequestorPreferences> </Source> <RequestDetails> <SearchLinkRequest ItemType="hotel" LinkType="image"> <ItemDestination DestinationType="city" DestinationCode="AMS" /> <ItemCode>APP</ItemCode> </SearchLinkRequest> </RequestDetails> </Request>

16.2.2 Search Link attributes/parameters

A Search Item request can contain optional attributes/parameters to filter the links returned. The following lists the attributes/parameters that can be specified: Attribute ItemType LinkType Description Mandatory. Identifies the type of item being processed. Must be one of apartment, hotel or sightseeing or transfer. Optional. Used to specify a single link type group. Must be one of image, map, flash or richmedia Description Mandatory. Used to return all items within the specified destination type (area or city) and destination code. Optional. If specified all items containing the given characters will be returned. Note: Item names are not case sensitive. Optional. If specified the details for the single code will be returned.
Parameters ItemDestination ItemName ItemCode
30-Sep-05 67096449.doc
16.3 Example XML Search Link response

The XML message below gives a sample of that given by the API in response to a Search Link Request.
<?xml version="1.0" encoding="UTF-8"?> <Response ResponseReference="200005"> <ResponseDetails Language="en"> <SearchLinkResponse ItemType="hotel"> <LinkDetails> <LinkDetail> <City Code="AMS"><![CDATA[Amsterdam]]></City> <Item Code="APP"><![CDATA[Apple Inn]]></Item> <Links> <MapLinks> <MapLink><![CDATA[http://maps-dynamic.imageserver.com/maps.asp? SITEID=8&CTY=AMS&PANITM=APP&COID=2&CAT=HOT]]></MapLink> <MapPageLink><![CDATA[http://interface.gta-travel.com/gtaxml/ IMapLink.jsp?prov=3&cty=AMS&itm=APP&typ=HH]]></MapPageLink> </MapLinks> <ImageLinks> <ImageLink Height="214" Width="360"> <Text><![CDATA[Exterior]]></Text> <ThumbNail><![CDATA[ http://images.test.imageserver.com/HH/Nonchainth/amsapp01.jpg]]></Thum bNail> <Image><![CDATA[ http://images.test.imageserver.com/HH/Nonchain/amsapp01.jpg]]></Image> </ImageLink> <ImageLink Height="229" Width="360"> <Text><![CDATA[Restaurant]]></Text> <ThumbNail><![CDATA[ http://images.test.imageserver.com/HH/Nonchainth/amsapp02.jpg]]> </ThumbNail> <Image><![CDATA[ http://images.test.imageserver.com/HH/Nonchain/amsapp02.jpg]]></Image> </ImageLink> <ImageLink Height="231" Width="360"> <Text><![CDATA[Bedroom]]></Text> <ThumbNail><![CDATA[ http://images.test.imageserver.com/HH/Nonchainth/amsapp03.jpg]]></Thum bNail> <Image><![CDATA[ http://images.test.imageserver.com/HH/Nonchain/amsapp03.jpg]]></Image> </ImageLink> </ImageLinks> <RichMediaLinks> <RichMediaLink>http://vfmii.com/exc/aspquery?command=invoke&ipid=BOSBAC1&ids=77381</RichMediaLink> </RichMediaLinks> <Links> </LinkDetail> </LinkDetails> </SearchLinkResponse> </ResponseDetails> </Response>
16.3.1 Search Link response parameters

Attribute ItemType Description Identifies the type of item being processed. Will be apartment, hotel or sightseeing.
A Search Link response will return the following for each item found for the request parameters: Parameter
30-Sep-05 67096449.doc
Description
City
The city name. In the language requested (if available). Attribute Description Code The unique city code held by GTA The item name. Attribute Description Code The unique item code held by GTA The collection of link types for the search.
Item
Links
16.3.2 Links parameters

A Links parameter can contain the following link types: Parameter MapLinks ImageLinks FlashLinks RichMediaLinks Description A collection of map links. A collection of image links. A collection of flash links. A collection of richmedia links.
16.3.3 MapLinks parameters

Parameter MapLink MapPageLink Description The link to a map for the search item. The link to a map for the search item.
N.B.: We currently offer the option to choose a map from two different providers. After 14th May 2008 only the maps provided under the <MapPageLink> parameter will be available.
16.3.4 ImageLinks parameters

Parameter ImageLink Description The link to an image for the search item. Attribute Description Height The image height. Width The image width.
16.3.4.1
Sub-parameters: Parameter Text ThumbNail Image Description The text associated with the image. The link to the thumbnail image. The link to the full image.
16.3.5 FlashLinks parameters
Parameter FlashLink
30-Sep-05 67096449.doc
Description The link to a flash presentation for the search item.

16.3.6 RichMediaLinks parameters

Parameter RichMediaLink Description The link to a richmedia for the search item.
30-Sep-05 67096449.doc
17. Search Remark

17.1 Overview
The Search Remark provides the client with static data relating to pre-coded remark codes held within the GTA system. The API will provide a remark name along with the unique code used by GTA to identify the pre-coded remark.
17.2 Example XML Search Remark request

The XML message below gives a sample of the expected elements needed by the API to execute a Search Remark Request.
<?xml version="1.0" encoding="UTF-8"?> <Request> <Source> <RequestorID Client="123456" EMailAddress="clientName@client.co.uk" Password="clientPassword" /> <RequestorPreferences Language="en"> <RequestMode>SYNCHRONOUS</RequestMode> </RequestorPreferences> </Source> <RequestDetails> <SearchRemarkRequest ItemType="hotel"> <RemarkName>arrival</RemarkName> </SearchRemarkRequest> </RequestDetails> </Request>

17.2.2 Search Remark parameters

A Search Remark request can contain optional parameters to filter the remark codes returned. The following lists the parameters that can be specified: Attribute ItemType Description Mandatory. Identifies the type of item being processed. Must be one of apartment or hotel. Description Optional. If specified all remark names containing the given characters will be returned. Note: Remark Names are not case sensitive. Optional. If specified the remark details for the single code will be returned.
Parameters RemarkName RemarkCode
30-Sep-05 67096449.doc
17.3 Example XML Search Remark response

The XML message below gives a sample of that given by the API in response to a Search Remark Request.
<?xml version="1.0" encoding="UTF-8"?> <Response ResponseReference="200002"> <ResponseDetails Language="en"> <SearchRemarkResponse> <RemarkDetails> <Remark Code="EA"><![CDATA[Please note early arrival]]></Remark> <Remark Code="LA"><![CDATA[Please note late arrival]]></Remark> </RemarkDetails> </SearchRemarkResponse> </ResponseDetails> </Response>
17.3.1 Search Remark response parameters

A Search Remark response will return the following for each remark found for the request parameters: Parameter Remark Description The remark name. In the language requested (if available). Attribute Description Code The unique remark code held by GTA.
30-Sep-05 67096449.doc
18. Search Essential Information

This module is no longer in use and has been removed from the specifications.
30-Sep-05 67096449.doc
19. Search Transfer List

19.1 Overview
The Search Transfer List provides the client with static data relating to variety of list types within the GTA system. The API will provide a description and code each list member for the given list type.
19.2 Example XML Search Transfer List request

The XML message below gives a sample of the expected elements needed by the API to execute a Search Transfer List Request.
<?xml version="1.0" encoding="UTF-8"?> <Request> <Source> <RequestorID Client="123456" EMailAddress="clientName@client.co.uk" Password="clientPassword" /> <RequestorPreferences Language="en"> <RequestMode>SYNCHRONOUS</RequestMode> </RequestorPreferences> </Source> <RequestDetails> <SearchTransferListRequest ListType="TransferLocation"> </SearchTransferListRequest> </RequestDetails> </Request>

19.2.2 Search Transfer List parameters

A Search Transfer List request can contain optional attributes/parameters to filter the events returned. The following lists the attributes/parameters that can be specified: Attribute ListType Description Mandatory. Used to return all descriptions for the specified list type (e.g. TransferLocation). Description Optional. If specified all names containing the given characters will be returned. Note: Names are not case sensitive. Optional. If specified the details for the single code will be returned.
Parameters Description Code
30-Sep-05 67096449.doc
19.3 Example XML Search Transfer List response

The XML message below gives a sample of that given by the API in response to a Search Transfer List Request.
<?xml version="1.0" encoding="UTF-8"?> <Response ResponseReference="200005"> <ResponseDetails Language="en"> <SearchTransferListResponse ListType="location"> <ListDetails> <Description Code="A"><![CDATA[Airport]]></Description> <Description Code="H"><![CDATA[Accommodation]]></Description> <Description Code="P"><![CDATA[Port]]></Description> <Description Code="S"><![CDATA[Station]]></Description> <Description Code="O"><![CDATA[Other]]></Description> </ListDetails> </SearchTransferListResponse> </ResponseDetails> </Response>
19.3.1 Search Transfer List response parameters

A Search Transfer List response will return the following for each item found for the request parameters: Attribute ListType Parameter Description Description The specified list type. Description The list item name. In the language requested (if available). Attribute Description Code The unique code held by GTA
19.3.2 Other Transfer List types

The Transfer List types allowed through the API are user controlled through Control Function maintenance (using Function Group XML_LSTTYP). API types are shown below: Vehicle TransferLocation
30-Sep-05 67096449.doc
20. Search Airport

20.1 Overview
The Search Airport provides the client with static data relating to airports. The API will provide airports held within the GTA system.
20.2 Example XML Search Airport request

The XML message below gives a sample of the expected elements needed by the API to execute a Search Airport Request.
<?xml version="1.0" encoding="UTF-8"?> <Request> <Source> <RequestorID Client="123456" EMailAddress="clientName@client.co.uk" Password="clientPassword" /> <RequestorPreferences Language="en"> <RequestMode>SYNCHRONOUS</RequestMode> </RequestorPreferences> </Source> <RequestDetails> <SearchAirportRequest> <ItemDestination DestinationType="city" DestinationCode="LON" /> <AirportName><![CDATA[at]]></AirportName> </SearchAirportRequest> </RequestDetails> </Request>

20.2.2 Search Airport parameters

A Search Airport request can contain optional attributes/parameters to filter the result returned. The following lists the attributes/parameters that can be specified: Parameters ItemDestination AirportName AirportCode Description Mandatory. Used to return all items within the specified destination type (area or city) and destination code. Optional. If specified all airports containing the given characters will be returned. Note: Airport names are not case sensitive. Optional. If specified the details for the single code will be returned.
20.3 Example XML Search Airport response

The XML message below gives a sample of that given by the API in response to a Search Airport Request.
30-Sep-05 67096449.doc
<?xml version="1.0" encoding="UTF-8"?> <Response ResponseReference="200005"> <ResponseDetails Language="en"> <SearchAirportResponse> <AirportDetails> <AirportDetail> <City Code="LON"><![CDATA[London]]></City> <Airport Code="LGW"><![CDATA[London gatwick]]></Airport> </AirportDetail> <AirportDetail> <City Code="LON"><![CDATA[London]]></City> <Airport Code="LHR"><![CDATA[London heathrow]]></Airport> </AirportDetail> </AirportDetails> </SearchAirportResponse> </ResponseDetails> </Response>
20.3.1 Search Airport response parameters

A Search Airport response will return the following for each item found for the request parameters: Parameter City Description The city name. In the language requested (if available). Attribute Description Code The unique city code held by GTA The airport name. Attribute Description Code The unique item code held by GTA
Airport
30-Sep-05 67096449.doc
21. Search Station

21.1 Overview
The Search Station provides the client with static data relating to stations. The API will provide stations held within the GTA system.
21.2 Example XML Search Station request

The XML message below gives a sample of the expected elements needed by the API to execute a Search Station Request.
<?xml version="1.0" encoding="UTF-8"?> <Request> <Source> <RequestorID Client="123456" EMailAddress="clientName@client.co.uk" Password="clientPassword" /> <RequestorPreferences Language="en"> <RequestMode>SYNCHRONOUS</RequestMode> </RequestorPreferences> </Source> <RequestDetails> <SearchStationRequest> <ItemDestination DestinationType="city" DestinationCode="LON" /> <StationName><![CDATA[liv]]></StationName> </SearchStationRequest> </RequestDetails> </Request>

21.2.2 Search Station parameters

A Search Station request can contain optional attributes/parameters to filter the result returned. The following lists the attributes/parameters that can be specified: Parameters ItemDestination StationName StationCode Description Mandatory. Used to return all items within the specified destination type (area or city) and destination code. Optional. If specified all stations containing the given characters will be returned. Note: Station names are not case sensitive. Optional. If specified the details for the single code will be returned.
21.3 Example XML Search Station response

The XML message below gives a sample of that given by the API in response to a Search Station Request.
30-Sep-05 67096449.doc
<?xml version="1.0" encoding="UTF-8"?> <Response ResponseReference="200005"> <ResponseDetails Language="en"> <SearchStationResponse> <StationDetails> <StationDetail> <City Code="LON"><![CDATA[London]]></City> <Station Code="LIVE01"><![CDATA[Liverpool Street]]></Station> </StationDetail> </StationDetails> </SearchStationResponse> </ResponseDetails> </Response>
21.3.1 Search Station response parameters

A Search Station response will return the following for each item found for the request parameters: Parameter City Description The city name. In the language requested (if available). Attribute Description Code The unique city code held by GTA The station name. Attribute Description Code The unique item code held by GTA
Station
30-Sep-05 67096449.doc
22. Search AOT Number

22.1 Overview
The Search AOT Number request provides the client with static data relating to the AOT numbers the customers can call while travelling and whenever unable to call the client directly. The API will provide a list of countries and their corresponding AOT numbers for the language required.
22.2 Example XML Search AOT Number request

The XML message below gives a sample of the expected elements needed by the API to execute a Search AOT Number Request.
<?xml version="1.0" encoding="UTF-8"?> <Request> <Source> <RequestorID Client="123456" EMailAddress="clientName@client.co.uk" Password="clientPassword" /> <RequestorPreferences Language="en"> <RequestMode>SYNCHRONOUS</RequestMode> </RequestorPreferences> </Source> <RequestDetails> <SearchAOTNumberRequest> <AssistanceLanguage /> <Destination>AU</Destination> <Nationality>GB</Nationality> <ServiceType>hotel</ServiceType> </SearchAOTNumberRequest> </RequestDetails> </Request>

22.2.2 Search AOT Number parameters

A Search AOT Number request can contain optional parameters to filter the list of AOT numbers returned. The following lists the parameters that can be specified: Parameter Description AssistanceLanguage Optional. If specified only AOT Numbers for the specified language will be returned. N.B.: if the language required is not available the result will return for English language support. Destination Optional. If specified only AOT Numbers for the specified destination will be returned. Nationality Mandatory. Only AOT Numbers for the specified passenger ISO 3166 format, 2 letter nationality will be returned. ServiceType Mandatory. Only AOT Numbers for the specified service type will be returned. N.B.: Currently all AOT Numbers are shared for all service types.
30-Sep-05 67096449.doc
22.3 Example XML Search AOT Number response

The XML message below gives a sample of that given by the API in response to a Search AOT Number request.
<?xml version="1.0" encoding="UTF-8"?> <Response ResponseReference=" REF_749-466-288315526413579"> <ResponseDetails Language="en"> <SearchAOTNumberResponse> <ContactDetails> <Destination Code="AU"> <Description><![CDATA[AUSTRALIA]]></Description> <Offices> <Office> <OfficeLocation><![CDATA[Sydney]]></OfficeLocation> <AssistanceLanguages> <AssistanceLanguage> <Language Code="en"><![CDATA[English]]></Language> <OfficeHours>09:00 - 17:30</OfficeHours> <AOTNumbers> <International>61-2-99013316</International> <National>02-99013316</National> <Local>99013316</Local> </AOTNumbers> </AssistanceLanguage> </AssistanceLanguages> </Office> </Offices> </Destination> </ContactDetails> </SearchAOTNumberResponse> </ResponseDetails> </Response>
22.3.1 Search AOT Numbers response parameters

The following parameters can form part of the <SearchAOTNumbersResponse>: Parameter Destination Description The country the passenger is travelling to. Attribute Description Code The unique country code held by GTA
Parameter Description Offices
Description The name of the country the passenger is travelling to. A list of gta offices that can support passengers travelling in the specified country. Offfice The details of the office supporting passengers travelling in the specified country. OfficeLocation The name of the city the office that will answer the AOT call is located in. AssistanceLanguage Specify the list of one or more languages in which assistance can be given under the specified phone number. Langauge Language name in which assistance can be given under the specified phone number. Attribute Description Code The unique language code held by GTA Parameter OfficeHours
30-Sep-05 67096449.doc
Description The local office hours during which the call will be
answered and assistance can be given.
22.3.2 AOTNumbers element

The <AOTNumbers> element will return the following sub-elements: Parameter International National Local OutOfOficce Description The telephone number that should be dialled by the passengers if they are still outside of the country. The telephone number that should be dialled by the passengers if they are in the country but outside of the city our office is located in. The telephone number that should be dialled by the passengers if they are within the same city that our office is located in. The telephone number that should be dialled by the passengers only during emergency and when the office number is not available.
30-Sep-05 67096449.doc
23. Search Special Offer

23.1 Overview
All requests will need to be sent in a SYNCHRONOUS mode; any requests send in an ASYNCHRONOUS mode will return an error. The Search Special Offer provides the client with static data relating to any special offers that might be available for various periods and properties. The API will provide a list of these offers held within the GTA system.
23.2 Example XML Search Special Offer Request

The XML message below gives a sample of the expected elements needed by the API to execute a Search Special Offer Request for hotels.
<?xml version="1.0" encoding="UTF-8"?> <Request> <Source> <RequestorID Client="123456" EMailAddress="clientName@client.co.uk" Password="clientPassword" /> <RequestorPreferences Language="en"> <RequestMode>SYNCHRONOUS</RequestMode> </RequestorPreferences> </Source> <RequestDetails> <SearchSpecialOfferRequest ItemType="hotel" > <PassengerNationality>GB</PassengerNationality> <Offer>FNT</Offer> <City>ROM</City> <Item>AMB</Item> <TravelDates> <FromDate>2006-06-01</FromDate> <ToDate>2006-06-30</ToDate> </TravelDates> <EffectiveDate>2006-05-01</EffectiveDate> </SearchSpecialOfferRequest> </RequestDetails> </Request>

23.2.2 Search Special Offer attributes/parameters

A Search Special Offer request can contain optional attributes/parameters to filter the Special Offers returned. The following lists the attributes/parameters that can be specified: Attribute ItemType Description Mandatory. Identifies the type of item being processed. Currently only hotel is available. Description Mandatory. Used to determine the country of residence of the passenger.
Parameter PassengerNationality
ISO 3166 format, 2 letters 30-Sep-05 67096449.doc
Offer Country
ISO 3166 format, 2 letters
City Item TravelDates
EffectiveDate
Optional. Used to specify the offer code for which the information is required. Mandatory if city parameter is not specified. Used to specify the country for which destination the information is required. Mandatory if country parameter is not specified. Used to specify the GTA city code for the item. Optional. Used to specify the GTA code for the item. Optional. Used to specify the travel dates. FromDate The start date for the range ToDate the end date of the range Optional. Used to specify the effective dates (creation date of the booking).
23.3 Example XML Search Special Offer response

The XML message below gives a sample of that given by the API in response to a Search Special Offers Request.
<?xml version="1.0" encoding="UTF-8"?> <Response ResponseReference="REF_8-1147434504577"> <ResponseDetails Language="en"> <SearchSpecialOfferResponse ItemType="hotel"> <ItemSpecialOffer> <City Code="MIL"><![CDATA[Milan]]></City> <Item Code="ALE"><![CDATA[ALEXANDER]]></Item> <SpecialOffers> <SpecialOffer> <Offer Code="FNT"><![CDATA[Free Night(s)]]></Offer> <TravelDates> <FromDate>2006-05-30</FromDate> <ToDate>2006-08-30</ToDate> </TravelDates> <OfferType>A</OfferType> <EffectiveDates> <FromDate>2006-04-25</FromDate> <ToDate>9999-12-31</ToDate> </EffectiveDates> <StayForNights>3</StayForNights> <PayForNights>2</PayForNights> <DiscountPercentage>0</DiscountPercentage> <MaximumNightsFree>999</MaximumNightsFree> <AllowedArrivalDates>1234567</AllowedArrivalDates> <ValidStayDates>1234567</ValidStayDates> <ApplicableOfferNights>1234567</ApplicableOfferNights> </SpecialOffer> <SpecialOffer> <Offer Code="FNT"><![CDATA[Free Night(s)]]></Offer> <TravelDates> <FromDate>2006-04-10</FromDate> <ToDate>2006-05-30</ToDate> </TravelDates> <OfferType>I</OfferType> <EffectiveDates> <FromDate>2006-04-06</FromDate> <ToDate>9999-12-31</ToDate> </EffectiveDates> <StayForNights>5</StayForNights> <PayForNights>4</PayForNights> <DiscountPercentage>0</DiscountPercentage> <MaximumNightsFree>1</MaximumNightsFree> <AllowedArrivalDates>1234567</AllowedArrivalDates> <ValidStayDates>1234567</ValidStayDates> <ApplicableOfferNights>1234567</ApplicableOfferNights> <ClosedDates> <ClosedDate>2006-07-01</ClosedDate> <ClosedDate>2006-05-30</ClosedDate>
</ClosedDates> </SpecialOffer> </SpecialOffers> </ItemSpecialOffer> </SearchSpecialOfferResponse> </ResponseDetails> </Response>
23.3.1 Search Special Offer response parameters

Attribute ItemType Description Identifies the type of item being processed. Currently only hotel is available.
A Search Special Offer response will return the following for each item found for the request parameters: Parameter ItemSpecialOffer Description ItemSpecialOffersinformation section).
(see
corresponding
23.3.2 Item Special Offer parameters

An Item Special Offer parameter can contain the following parameters: Parameter City Description The city name in the language requested (if available). Attribute Description Code The unique city code held by GTA. The item name. Attribute Description Code The unique item code held by GTA. A list of one or more special offers held for this item (see corresponding section).
Item
SpecialOffers
23.3.3 Special Offer parameters

Parameter Offer Description The offer name in the language requested (if available). Attribute Description Code The unique offer code held by GTA. Description A list of one or more special offers held for this item (see corresponding section).. Specifies the travel dates. FromDate The start date for the range ToDate the end date of the range
Parameter SpecialOffer TravelDates
30-Sep-05 67096449.doc
OfferType
EffectiveDates
StayForNights PayForNights
DiscountPercentage MaximumNightsFree AllowedArrivalDates ValidStayDates ApplicableOfferNights ClosedDates ClosedDate
Specifies the type of the offer A - Offer is based on arrival dates I - Offer is inclusive, entire stay must fall must fall within specified travel dates Specifies the effective dates (creation date of the booking). FromDate The start date for the range ToDate the end date of the range Specifies the minimum number of nights that the customer must stay at the hotel in order for the offer to apply. Specifies the number of nights that will be charged if the customer stays for the minimum number of nights specified within the <StayForNights> element. Specifies the discount (in percentage) that applies if the offer is not for an entirely free night. Specifies the maximum number of nights or instances that the hotel will provide free or at a discount. Specifies the days of the week that the client must arrive in order to receive the offer. Specifies the days of the week that the client can stay at the property in order to receive the offer. Specifies whether all days of the week are applicable for the offer or whether only specific days of the week are applicable for the offer. A list of one or more dates for which the offer is not available. Specifies the dates the offer is not available.
30-Sep-05 67096449.doc
24. Search Car Suppliers

30-Sep-05 67096449.doc
25. Search Car Locations

30-Sep-05 67096449.doc
26. Search Car Location Information

30-Sep-05 67096449.doc
27. Search Recommended Item

27.1 Overview
All requests will need to be sent in a SYNCHRONOUS mode; any requests send in an ASYNCHRONOUS mode will return an error. The Search Recommended Item provides the client with static data relating to any recommended items for various periods and properties. The API will provide a list of these recommended items held within the GTA system.
27.2 Example XML Search Recommended Item request

The XML message below gives a sample of the expected elements needed by the API to execute a Search Recommended Item Request for hotels.
<?xml version="1.0" encoding="UTF-8"?> <Request> <Source> <RequestorID Client="123456" EMailAddress="clientName@client.co.uk" Password="clientPassword" /> <RequestorPreferences Language="en"> <RequestMode>SYNCHRONOUS</RequestMode> </RequestorPreferences> </Source> <RequestDetails> <SearchRecommendedItemRequest ItemType="hotel" > <ItemDestination DestinationType="City" DestinationCode="LON" /> <Nationality>de</Nationality> <TravelDates> <FromDate>2007-03-20</FromDate> <ToDate>2007-03-28</ToDate> </TravelDates> </SearchRecommendedItemRequest > </RequestDetails> </Request>

27.2.2 Search Recommended Item attributes/parameters

A Search Recommended Item request can contain optional attributes/parameters to filter the items returned. The following lists the attributes/parameters that can be specified: Attribute ItemType Description Mandatory. Identifies the type of item being processed. Currently only hotel and sightseeing are available. Description Optional. Used to filter by destination. Attribute Description DestinationType Used to determine if the search is
Parameter ItemDestination
30-Sep-05 67096449.doc
made by city or area DestinationCode Used to determine the unique GTA city or area code. Parameter Nationality
ISO 3166 format, 2 letters
TravelDates 27.2.2.1
Description Optional. Used to determine the country of residence of the passenger. Optional. Used to specify the travel dates (see below for further details).
Travel Dates Parameters
A Travel Date element can contain the following parameters: Parameter FromDate ToDate Description FromDate the start date of the travel date range. ToDate the end date of the travel date range.
27.3 Example XML Search Recommended Item response

The XML message below gives a sample of that given by the API in response to a Search Recommended Item Request.
<?xml version="1.0" encoding="UTF-8"?> <Response ResponseReference="REF_123456-1147434504577"> <ResponseDetails Language="en"> <SearchRecommendedItemResponse> <RecommendedItemDetails> <City Code="LON"><![CDATA[London]]></City> <Item Code="ABB"><![CDATA[Abbey Court]]></Item> <Nationality>**</Nationality> <TravelDates> <FromDate>2007-03-20</FromDate> <ToDate>2007-03-28</ToDate> </TravelDates> </RecommendedItemDetails> </SearchRecommendedItemResponse> </ResponseDetails> </Response>
27.3.1 Search Recommended Item response parameters

A Search Recommended Hotel Item response will return the following for each item found for the request parameters: Parameter Description RecommendedItemDetails A list of one or several recommended item details
27.3.2 Recommended Item Details parameters

A recommended item detail element can contain the following parameters: Parameter City
30-Sep-05 67096449.doc
Description The city name in the language requested (if available). Attribute Description
Code Parameter Item
The unique city code held by GTA.
Description The item name. Attribute Description Code The item code held by GTA.
Parameter Nationality TravelDates 27.3.2.1
Description The code for the passenger nationality the recommended item is valid for. Will default to ** if it is valid for all passenger nationalities. Specifies the travel dates applicable to the recommended item (see below for further details).
Travel Dates Parameters
A Travel Date element can contain the following parameters: Parameter FromDate ToDate Description FromDate the start date of the travel date range. ToDate the end date of the travel date range.
30-Sep-05 67096449.doc
28. Search Car Supplier Information

30-Sep-05 67096449.doc
29. Search Car Supplier Link Information

30-Sep-05 67096449.doc
30. ACRISS CODE

30-Sep-05 67096449.doc
31. Search Sightseeing Type

31.1 Overview
The Search Sightseeing Type request provides the client with static data relating to sightseeing types held within the GTA system. The API will provide a sightseeing type name along with the unique code used by GTA to identify the sightseeing type. All requests will need to be send in a SYNCHRONOUS mode; any requests send in an ASYNCHRONOUS mode will return an error.
31.2 Example XML Search Sightseeing Type Request

The XML message below gives a sample of the expected elements required by the API to execute a Search Sightseeing Type request.
<?xml version="1.0" encoding="UTF-8"?> <Request> <Source> <RequestorID Client="123" EMailAddress="email@client.com" Password="P123"/> <RequestorPreferences Language="en"> <RequestMode>SYNCHRONOUS</RequestMode> </RequestorPreferences> </Source> <RequestDetails> <SearchSightseeingTypeRequest/> </RequestDetails> </Request>

31.2.2 Search Sightseeing Type request parameters

A Search Sightseeing Type request can contain optional parameters to filter the sightseeing types returned. The following lists the parameters that can be specified: Parameters SightseeingTypeName Description Optional. If specified all sightseeing types containing the given characters will be returned, in the language requested (if available). Note: Sightseeing Type Names are not case sensitive. Optional. If specified the sightseeing type details for the single code will be returned, in the language requested (if available).
SightseeingTypeCode
31.3 Example XML Search Sightseeing Type response

The XML message below gives a sample of that given by the API in response to a Search Sightseeing Type request.
30-Sep-05 67096449.doc
<?xml version="1.0" encoding="UTF-8"?> <Response ResponseReference=" REF_123-288315526413579"> <ResponseDetails Language="en"> <SearchSightseeingTypeResponse> <SightseeingTypes> <SightseeingType Code="AR"><![CDATA[Air Sightseeing]]></SightseeingType> <SightseeingType Code="CR"><![CDATA[Sightseeing Cruises]]></SightseeingType> <SightseeingType Code="RS"><![CDATA[Sightseeing Tours]]></SightseeingType> </SightseeingTypes> </SearchSightseeingTypeResponse> </ResponseDetails> </Response>
31.3.1 Search Sightseeing Type response parameters

The following parameters can form part of the <SearchSightseeingTypeResponse>: Parameter SightseeingTypes SightseeingType Description The collection of <SightseeingType> parameters. The sightseeing type, in the language requested (if available). Attribute Description Code The unique sightseeing type code held by GTA.
30-Sep-05 67096449.doc
32. Search Sightseeing Category

32.1 Overview
The Search Sightseeing Category request provides the client with static data relating to sightseeing categories held within the GTA system. The API will provide a sightseeing category name along with the unique code used by GTA to identify the sightseeing category.
32.2 Example XML Search Sightseeing Category request

The XML message below gives a sample of the expected elements required by the API to execute a Search Sightseeing Category request.
<?xml version="1.0" encoding="UTF-8"?> <Request> <Source> <RequestorID Client="123" EMailAddress="email@client.com" Password="P123"/> <RequestorPreferences Language="en"> <RequestMode>SYNCHRONOUS</RequestMode> </RequestorPreferences> </Source> <RequestDetails> <SearchSightseeingCategoryRequest/> </RequestDetails> </Request>

32.2.2 Search Sightseeing Category request parameters

A Search Sightseeing Category request can contain optional parameters to filter the sightseeing categories returned. The following lists the parameters that can be specified: Parameters SightseeingCategoryName Description Optional. If specified all sightseeing categories containing the given characters will be returned, in the language requested (if available). Note: Sightseeing Category Names are not case sensitive. Optional. If specified the sightseeing category details for the single code will be returned, in the language requested (if available).
SightseeingCategoryCode
32.3 Example XML Search Sightseeing Category response

The XML message below gives a sample of that given by the API in response to a Search Sightseeing Category request.
30-Sep-05 67096449.doc
<?xml version="1.0" encoding="UTF-8"?> <Response ResponseReference="REF_123-58569737485548282"> <ResponseDetails Language="en"> <SearchSightseeingCategoryResponse> <SightseeingCategories> <SightseeingCategory Code="FA"><![CDATA[Fashion]]></SightseeingCategory> <SightseeingCategory Code="MU"><![CDATA[Music]]></SightseeingCategory> <SightseeingCategory Code="SP"><![CDATA[Sport]]></SightseeingCategory> </SightseeingCategories> </SearchSightseeingCategoryResponse> </ResponseDetails> </Response>
32.3.1 Search Sightseeing Category response parameters

The following parameters can form part of the <SearchSightseeingCategoryResponse>: Parameter SightseeingCategories SightseeingCategory Description The collection of <SightseeingCategory> parameters. The sightseeing category, in the language requested (if available). Attribute Description Code The unique sightseeing category code held by GTA.
30-Sep-05 67096449.doc
33. Search Hotel Group

33.1 Overview
The Search Hotel Group request provides the client with a file which will group together hotel codes where multiple GTA codes exist for different room categories at the same hotel. All requests will need to be sent in a SYNCHRONOUS mode; any requests send in n ASYNCHRONOUS mode will return an error.
33.2
Example XML Search Hotel Group request
The XML message below gives a sample of the expected elements required by the API to execute a Search Hotel Group request:
<?xml version="1.0" encoding="UTF-8"?> <Request> <Source> <RequestorID Client="123456" EMailAddress="clientName@client.co.uk" Password="clientPassword"/> <RequestorPreferences Language="en"> <RequestMode>SYNCHRONOUS</RequestMode> </RequestorPreferences> </Source> <RequestDetails> <SearchHotelGroupRequest> <ItemDestination DestinationType="city" DestinationCode="lon"/> <ItemName/> </SearchHotelGroupRequest> </RequestDetails> </Request>

33.2.2 Search Hotel Group attributes/parameters

A Search Hotel Group request can contain optional attributes/parameters to filter the items returned. The following list the attributes/parameters that can be specified: Element CountryCode Description Optional. Identifies the country where the hotel is based. This element cannot be used in conjunction with the ItemDestination element. Either the CountryCode or the ItemDestination Code must be entered in the request. Optional. Identifies the destination where the hotel is based. This element cannot be used in conjunction with the CountryCode element. Either the CountryCode or the ItemDestination Code must be entered in the request. Attribute
30-Sep-05 67096449.doc
ItemDestination
Description
DestinationType DestinationCode Element ItemName Description
Mandatory if ItemDestination Identifies the type city or area.
is
entered. entered.
Mandatory if ItemDestination is Identifies the GTA city or area code.
Optional. Identifies the name of the item.
33.3 Example XML Search Hotel Group response

The XML message below gives a sample of that given by the API in response to a Search Hotel Group response.
<?xml version="1.0" encoding="UTF-8"?> <Response ResponseReference= "REF_8-1223996838473"> <ResponseDetails Language="en"> <SearchHotelGroupResponse> <GroupHotelDetails> <GroupDetails> <Country Code=GB><![CDATA[United Kingdom]]></Country> <City Code="LON"><![CDATA[London]]></City> <HotelGroup Code="ATHE">Athenaeum</HotelGroup> <GroupItem PrimaryHotel="true"> <Item Code="ATH1"><![CDATA[ATHENAEUM]]></Item> <RoomCategory>Standard</RoomCategory> </GroupItem> <GroupItem> <Item Code="ATH2"><![CDATA[ATHENAEUM (EXECUTIVE)]]></Item> <RoomCategory>Executive</RoomCategory> </GroupItem> <GroupItem> <Item Code="ATH3"><![CDATA[ATHENAEUM (PARKVIEW)]]></Item> <RoomCategory>Parkview</RoomCategory> </GroupItem> </GroupDetails> <GroupDetails> <Country Code="GB"><![CDATA[United Kingdom]]></Country> <City Code="LON"><![CDATA[London]]></City> <HotelGroup Code="COU">Courthouse</HotelGroup> <GroupItem PrimaryHotel="true"> <Item Code="COU6"><![CDATA[COURTHOUSE KEMPINSKI]]></Item> <RoomCategory>Standard</RoomCategory> </GroupItem> <GroupItem> <Item Code="COUA"><![CDATA[CH KEMPINS(STATE KING)]]></Item> <RoomCategory>State King</RoomCategory> </GroupItem> </GroupDetails> </GroupHotelDetails> </SearchHotelGroupResponse> </ResponseDetails> </Response>
33.3.1 Search Hotel Group response standard attributes/parameters

A Search Hotel Group response will return the following for each item found for the request parameters: Element GroupHotelDetails GroupDetails Country
30-Sep-05 67096449.doc
Description The details of the hotel groups. The details of a specific hotel group. The country where the hotel group is based.
Attribute Code City Attribute Code HotelGroup Attribute Code GroupItem Attribute PrimaryHotel
Description The ISO code of the country. Description The GTA code of the city. Description The GTA code of the hotel group. Description If true it identifies the primary hotel assigned to the group. This should be used to retrieve item information. Description The code of the group hotel.
The city where the hotel is based.
The name of the hotel group.
The details of a specific hotel within the group.
Item
The name of the group hotel. Attribute Code
RoomCategory
The category of the room.
30-Sep-05 67096449.doc
34. Item Information Download
34.1 Overview
The Item Information Download request provides the client with a file containing all our static data. At the moment it will be available for the hotel module only. It is possible to request a file for a complete download of all our static data, a file for incremental updates and a file for yesterdays incremental updates. All requests will need to be sent in a SYNCHRONOUS mode; any requests sent in an ASYNCHRONOUS mode will return an error. An XML response will only be returned if the request generates an error. Otherwise a zip file containing multiple XML files will be returned. Clients will need to check the Content-Type of the HTTP response header: if the Content-Type=text/xml then an error is being returned; if the Content-Type=application/download then a zip file is being returned in the body of the HTTP response. The client will have to read all the bytes of the HTTP response body and process this as a zip file, i.e.: save the received bytes in a file (e.g.: Full Download-March 2009.zip) and then process this file. Alternatively the client can process the bytes as a zip file in memory. If a request for a complete download is sent the response will be broken down into multiple files for each property. If a time out (usually HTTP Status Response: 503) is received the clients coding will have to have been set up to retry at a later time, but not earlier than one hour. 34.1.1 Source parameters Please refer to the API Architecture document.
34.2 Example XML Item Information Download request

It is possible to request a file for a complete download of all our static data, a file for incremental updates and a file for yesterdays incremental updates.
34.2.1 Item Information Download request for complete file

The XML message below gives a sample of the expected elements needed by the API to execute an Item Information Download request to receive the complete file of all our static data.
<?xml version="1.0" encoding="UTF-8"?> <Request> <Source> <RequestorID Client="123456" EMailAddress="clientName@client.co.uk" Password="clientPassword" /> <RequestorPreferences Language="en"> <RequestMode>SYNCHRONOUS</RequestMode> </RequestorPreferences> </Source> <RequestDetails> <ItemInformationDownloadRequest ItemType="hotel"> </ItemInformationDownloadRequest> </RequestDetails> </Request>
Table 1. Item Information Download search request.
30-Sep-05 67096449.doc
34.2.2 Item Information Download request for incremental updates

The XML message below gives a sample of the expected elements needed by the API to execute an Item Information Download request to receive the incremental updates.
<?xml version="1.0" encoding="UTF-8"?> <Request> <Source> <RequestorID Client="123456" EMailAddress="clientName@client.co.uk" Password="clientPassword" /> <RequestorPreferences Language="en"> <RequestMode>SYNCHRONOUS</RequestMode> </RequestorPreferences> </Source> <RequestDetails> <ItemInformationDownloadRequest ItemType="hotel"> <IncrementalDownloads> <FromDate>2008-12-01</FromDate> <ToDate>2008-12-31</ToDate> </IncrementalDownloads> </ItemInformationDownloadRequest> </RequestDetails> </Request>
Table 2. Item Information Download for incremental updates search request.
34.2.3 Item Information Download request for yesterdays incremental updates

The XML message below gives a sample of the expected elements needed by the API to execute an Item Information Download request to receive only yesterdays incremental update.
<?xml version="1.0" encoding="UTF-8"?> <Request> <Source> <RequestorID Client="123456" EMailAddress="clientName@client.co.uk" Password="clientPassword" /> <RequestorPreferences Language="en"> <RequestMode>SYNCHRONOUS</RequestMode> </RequestorPreferences> </Source> <RequestDetails> <ItemInformationDownloadRequest ItemType="hotel"> <IncrementalDownloads> </IncrementalDownloads> </ItemInformationDownloadRequest> </RequestDetails> </Request>
Table3. Item Information Download for yesterdays incremental updates search request.
34.2.4 Item Information Download request attributes/parameters

An Item Information Download request can contain optional attributes/parameters to filter the items returned. The following list the attributes/parameters that can be specified: Attribute ItemType Parameters IncrementalDownloads
30-Sep-05 67096449.doc
Description Mandatory. Identifies the type of item being processed. Currently only hotel is available. Description Optional. Specifies the date range during which the item information was last updated. If
not specified the complete file will be downloaded. FromDate Optional. The start date of the date range. If not present will default to yesterdays date. Cannot be more than yesterdays date -30. Optional. The end date of the date range. If not present will default to yesterdays date. Cannot be more than yesterdays date -30.
ToDate
34.2.5 Example XML Item Information Download response

Note The API will be responsible for the level of information returned to the client. This will be determined as part of the contractual agreement with GTA and subsequently set up as system parameters within the GTA system. Unlike our other XML responses, this response will not contain a ResponseReference attribute. The XML message below gives a sample of that given by the API in response to an Item Information Download Response.
<?xml version="1.0" encoding="UTF-8"?> <Response> <ResponseDetails Language="en"> <SearchItemInformationResponse ItemType="hotel"> <ItemDetails> <ItemDetail> <City Code="PAR"><![CDATA[Paris]]></City> <Item Code="ALB2"><![CDATA[Alba Opera]]></Item> <LocationDetails> <Location Code="G1"><![CDATA[Central]]></Location> <Location Code="09"><![CDATA[09e Arrondissement]]></Location> <Location Code="28"><![CDATA[Pigalle/Montmartre/Sacre Coeur]]></Location> </LocationDetails> <HotelInformation> <AddressLines> <AddressLine1><![CDATA[34 TER RUE DE LA TOUR D AUVERGNE]]></AddressLine1> <AddressLine2><![CDATA[75009 PARIS]]></AddressLine2> <AddressLine3><![CDATA[FRANCE]]></AddressLine3> <Telephone><![CDATA[33-1-48788022]]></Telephone> <Fax><![CDATA[33-1-42852313]]></Fax> <EmailAddress><![CDATA[hotel-albaoperaresidence@wanadoo.fr]]></EmailAddress> </AddressLines> <StarRating>3</StarRating> <Category><![CDATA[Superior Tourist Class Traditional Hotel]]></Category> <AreaDetails> <AreaDetail><![CDATA[20 kms to the airport (charles de Gaulle)]]></AreaDetail> <AreaDetail><![CDATA[20 kms to the airport (orly)]]></AreaDetail> <AreaDetail><![CDATA[2 minute walk to the nearest metro station (notre dame de lorette/cadet)]]></AreaDetail> <AreaDetail><![CDATA[Close to the station (gare du nord)]]></AreaDetail> </AreaDetails> <Reports> <Report Type="location"><![CDATA[Located in a quiet courtyard half way between Opera and Montmartre, a mere 5 minutes walk from the metro.]]></Report> <Report Type="rooms"><![CDATA[All the rooms are fully equipped. Very convenient for long stays as all the rooms are studios so all of them are larger than the Paris standard.]]></Report> <Report Type="restaurant"><![CDATA[There is no restaurant in the hotel, but there are lot of typical and nice good restaurant in the area.]]></Report> <Report Type="lobby"><![CDATA[The reception area is small and bright and has small seating area. The beautiful wrought iron old fashion lift is very small.]]></Report> <Report Type="general"><![CDATA[Nice property in a quiet environment, yet within walking distance from shopping areas and lively spots of Paris like 30-Sep-05 Version 2.3. 67096449.doc Page 88 of 91
Montmartre.]]></Report> <Report Type="inclusive"><![CDATA[All inclusive ***Test Only***]]></Report> <Report Type="pleasenote"><![CDATA[****Test please note field****]]></Report> </Reports> <RoomTypes RoomCount="24"> <RoomType Code="SB"><![CDATA[Single room]]></RoomType> <RoomType Code="DB"><![CDATA[Double rooms]]></RoomType> <RoomType Code="TB"><![CDATA[Twin rooms]]></RoomType> <RoomType Code="TR"><![CDATA[Triple rooms]]></RoomType> <RoomType Code="Q"><![CDATA[Quad roomd]]></RoomType> </RoomTypes> <RoomFacilities> <Facility Code="TV"><![CDATA[Television]]></Facility> <Facility Code="*DD"><![CDATA[Direct dial phone]]></Facility> <Facility Code="*VL"><![CDATA[Voltage 200v]]></Facility> </RoomFacilities> <Facilities> <Facility Code="*LS"><![CDATA[Small sized lobby]]></Facility> <Facility Code="*EC"><![CDATA[Earliest check-in at 12:00]]></Facility> <Facility Code="*LF"><![CDATA[1 lift]]></Facility> <Facility Code="*PT"><![CDATA[Porterage 24 hour]]></Facility> <Facility Code="*FL"><![CDATA[6 floors]]></Facility> <Facility Code="*BS"><![CDATA[Baby sitting]]></Facility> <Facility Code="*LY"><![CDATA[Laundry facilities]]></Facility> <Facility Code="*DF"><![CDATA[Disabled facilities]]></Facility> </Facilities> <Links> <MapLinks> <MapLink><![CDATA[http://interface.test.gta-travel.com/gtaxml/IMapLink.jsp? prov=3&cty=PAR&itm=ALB2&typ=HH ]]></MapLink> </MapLinks> <ImageLinks> <ImageLink Height="269" Width="360"> <Text><![CDATA[Entrance]]></Text> <ThumbNail><![CDATA[ http://images.test.gtatravel.com/HH/Images/F/PARth/PARALB29.jpg]]></ThumbNail> <Image><![CDATA[http://images.test.gtatravel.com/HH/Images/F/PARth/PARALB29.jpg]]></Image> </ImageLink> </ImageLinks> </Links> <GeoCodes> <Latitude>48.879600000000000</Latitude> <Longitude>2.342400000000000</Longitude> </GeoCodes> </HotelInformation> <Copyright><![CDATA[c)Donvand Limited 2008]]></Copyright> </ItemDetail> </ItemDetails> </SearchItemInformationResponse> </ResponseDetails> </Response>
Table 2a. Item Information search response flat structure (no Participation Level).
<?xml version="1.0" encoding="UTF-8"?> <Response> <ResponseDetails Language="en"> <SearchItemInformationResponse ItemType="hotel"> <ItemDetails> <ItemDetail> <City Code="PAR"><![CDATA[Paris]]></City> <Item Code="HIL"><![CDATA[Alba Opera]]></Item> <LocationDetails> <Location Code="G1"><![CDATA[Central]]></Location> <Location Code="09"><![CDATA[09e Arrondissement]]></Location> <Location Code="28"><![CDATA[Pigalle/Montmartre/Sacre Coeur]]></Location> </LocationDetails> <HotelInformation> <AddressLines> <AddressLine1><![CDATA[34 TER RUE DE LA TOUR D AUVERGNE]]></AddressLine1> <AddressLine2><![CDATA[75009 PARIS]]></AddressLine2> <AddressLine3><![CDATA[FRANCE]]></AddressLine3> <Telephone><![CDATA[33-1-48788022]]></Telephone> <Fax><![CDATA[33-1-42852313]]></Fax> <EmailAddress><![CDATA[hotel-hilton@wanadoo.fr]]></EmailAddress> </AddressLines> 30-Sep-05 Version 2.3. 67096449.doc Page 89 of 91
<StarRating>3</StarRating> <Category><![CDATA[Superior Tourist Class Traditional Hotel]]></Category> <AreaDetails> <AreaDetail><![CDATA[20 kms to the airport (charles de gaulle)]]></AreaDetail> <AreaDetail><![CDATA[20 kms to the airport (orly)]]></AreaDetail> <AreaDetail><![CDATA[2 minute walk to the nearest metro station (notre dame de lorette/cadet)]]></AreaDetail> <AreaDetail><![CDATA[Close to the station (gare du nord)]]></AreaDetail> </AreaDetails> <Reports> <Report Type="location"><![CDATA[Located in a quiet courtyard half way between Opera and Montmartre, a mere 5 minutes walk from the metro.]]></Report> <Report Type="rooms"><![CDATA[All the rooms are fully equipped. Very convenient for long stays as all the rooms are studios so all of them are larger than the Paris standard.]]></Report> <Report Type="restaurant"><![CDATA[There is no restaurant in the hotel, but there are lot of typical and nice good restaurant in the area.]]></Report> <Report Type="exterior"><![CDATA[It is a 6 storey Haussmann style building.]]></Report> <Report Type="lobby"><![CDATA[The reception area is small and bright and has small seating area. The beautiful wrought iron old fashion lift is very small.]]></Report> <Report Type="general"><![CDATA[Nice property in a quiet environment, yet within walking distance from shopping areas and lively spots of Paris like Montmartre.]]></Report> <Report Type="inclusive"><![CDATA[All inclusive ***Test Only***]]></Report> <Report Type="pleasenote"><![CDATA[****Test please note field****]]></Report> </Reports> <RoomCategories> <RoomCategory Id = "002:HIL1"> <Description><![CDATA[Standard]]></Description> <RoomDescription>The medium sized bedrooms are typical Hilton style with two double beds in each twin room. All the rooms were renovated in 2001 with modern furnishings in Italian style and strong, contrasting colours. The white tiled bathrooms are also in very good condition and the rooms offer all the facilities and the high standards that one would expect from a 5 star Hilton hotel.</RoomDescription> </RoomCategory> <RoomCategory Id = "002:HILTON:HL:04988:XXX:XXX:A02"> <Description><![CDATA[King Junior Suite]]></Description> </RoomCategory> <RoomCategory Id = "002:HILTON:HL:04988:XXX:XXX:A10"> <Description><![CDATA[Standard Double]]></Description> </RoomCategory> <RoomCategory Id = "002:HILTON:HL:04988:XXX:XXX:A09"> <Description><![CDATA[Executive King]]></Description> <RoomDescription>The very large Executive King bedrooms are very comfortably furnished. There is a mini-audio system in each room. The bathrooms are fitted to a very high standard.</RoomDescription> </RoomCategory> <RoomCategory Id = "002:HILTON:HL:04988:XXX:XXX:A03"> <Description><![CDATA[Presidential Suite]]></Description> </RoomCategory> </RoomCategories> <RoomTypes RoomCount="24"> <RoomType Code="SB"><![CDATA[Single room]]></RoomType> <RoomType Code="DB"><![CDATA[Double rooms]]></RoomType> <RoomType Code="TB"><![CDATA[Twin rooms]]></RoomType> <RoomType Code="TR"><![CDATA[Triple rooms]]></RoomType> <RoomType Code="Q"><![CDATA[Quad roomd]]></RoomType> </RoomTypes> <RoomFacilities> <Facility Code="TV"><![CDATA[Television]]></Facility> <Facility Code="*DD"><![CDATA[Direct dial phone]]></Facility> <Facility Code="*VL"><![CDATA[Voltage 200v]]></Facility> </RoomFacilities> <Facilities> <Facility Code="*LS"><![CDATA[Small sized lobby]]></Facility> <Facility Code="*EC"><![CDATA[Earliest check-in at 12:00]]></Facility> <Facility Code="*LF"><![CDATA[1 lift]]></Facility> <Facility Code="*PT"><![CDATA[Porterage 24 hour]]></Facility> <Facility Code="*FL"><![CDATA[6 floors]]></Facility> <Facility Code="*BS"><![CDATA[Baby sitting]]></Facility> <Facility Code="*LY"><![CDATA[Laundry facilities]]></Facility> <Facility Code="*DF"><![CDATA[Disabled facilities]]></Facility> </Facilities> <Links> <MapLinks> <MapLink><![CDATA[http://interface.test.gtatravel.com/gtaxml/IMapLink.jsp?prov=3&cty=PAR&itm=ALB2&typ=HH ]]></MapLink> </MapLinks> 30-Sep-05 67096449.doc Version 2.3. Page 90 of 91
<ImageLinks> <ImageLink Height="269" Width="360"> <Text><![CDATA[Entrance]]></Text> <ThumbNail><![CDATA[ http://images.test.gtatravel.com/HH/Images/F/PARth/PARALB29.jpg]]></ThumbNail> <Image><![CDATA[http://images.test.gtatravel.com/HH/Images/F/PARth/PARALB29.jpg]]></Image> </ImageLink> </ImageLinks> </Links> <GeoCodes> <Latitude>48.879600000000000</Latitude> <Longitude>2.342400000000000</Longitude> </GeoCodes> </HotelInformation> <Copyright><![CDATA[c)Donvand Limited 2008]]></Copyright> </ItemDetail> </ItemDetails> </SearchItemInformationResponse> </ResponseDetails> </Response>
Table 3b. Item Information search response (Participation Level 1/ 2 or above)
34.2.6 Item Information Download response attributes/parameters

For details of the attributes and parameters returned with the <ItemInformationDownloadResponse> please refer to paragraphs 9.3 and 9.5 in this document (Search Item Information).
30-Sep-05 67096449.doc

GTA Static Data 2 3

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

GTA Static Data 2 3

Încărcat de

Drepturi de autor:

Formate disponibile

System Scope Document for: -

Client Based XML Interface Static Data

Version 2.3. Page 1 of 91

Version 2.3. Page 4 of 91

1.2 Purpose of this document

1.3 The API Architecture document

Version 2.3. Page 5 of 91

Static Data Type Countries Cities Hotels

Examples Australia or Romania. London or Boston Olympia or Marriott

2.2 Codes recognised by the API

Version 2.3. Page 6 of 91

3.2 Example XML Search Currency request

3.2.1 Source parameters

3.2.2 Search Currency attributes/parameters

3.3 Example XML Search Currency response

Version 2.3. Page 7 of 91

3.3.1 Search Currency response parameters

Version 2.3. Page 8 of 91

4.2 Example XML Search Country request

4.2.1 Source parameters

4.2.2 Search Country attributes/parameters

If specified the country details for the single code will be

4.3 Example XML Search Country response

4.3.1 Search Country response parameters

Version 2.3. Page 10 of 91

5.2 Example XML Search City request

5.2.1 Source parameters

5.2.2 Search City attributes

Parameter CityName CityCode

Version 2.3. Page 11 of 91

5.3 Example XML Search City response

5.3.1 Search City response attributes and parameters

Version 2.3. Page 12 of 91

6.2 Example XML Search Area request

6.2.1 Source parameters

6.2.2 Search Area parameters

6.3 Example XML Search Area response

Version 2.3. Page 13 of 91

6.3.1 Search Area response parameters

Version 2.3. Page 14 of 91

7. Search Cities in Area

7.2 Example XML Search Cities in Area request

7.2.1 Source parameters

7.2.2 Search City attributes

7.3 Example XML Search Cities in Area response

Version 2.3. Page 15 of 91

7.3.1 Search Cities in Area response parameters

Version 2.3. Page 16 of 91

8.2 Example XML Search Item request

8.2.1 Source parameters

8.2.2 Search Item attributes/parameters

Parameters ItemDestination LocationCode ItemName ItemCode

8.3 Example XML Search Item response

8.3.1 Search Item response parameters

8.3.2 LocationDetails parameters

Version 2.3. Page 19 of 91

9. Search Item Information

Example XML Search Item Information request

9.2.1 Source parameters

9.2.2 Search Item Information attributes/parameters

Parameters ItemDestination LocationCode ItemName ItemCode

9.2.3 Search Apartment Information sub-parameters

9.2.4 Search Hotel Information sub-parameters

9.2.5 Search Sightseeing Information sub-parameters