Page 6 - demo demito

The rest of this chapter will be written to describe the syntax of the XML interface. The SOAP interface uses data structures equivalent to the complex elements of the XML interface. These can be constructed from the WSDL schema: http://www.roomsxmldemo.com/RXLStagingServices/ASMX/XmlService.asmx?W SDL
3.1. HTTP compression
The roomsXML Web Service Interface supports HTTP 1.1 compression. Clients must take advantage of compression by ensuring that requests to the interface specify the HTTP header:
Accept-Encoding: gzip,deflate
If this is specified on any request then the corresponding response will be returned in a compressed format.
We recommend that this header is specified for all requests as it can offer a significant performance improvement, especially for large availability searches.
3.2. Common parameter structures
There are a number of common parameter structures used in the roomsXML Web Service Interface. For example, all Web Service operations require authority information.
3.2.1. Authority
The authority information, required by all Web Service operations, combines authentication and configuration:
<Authority>
<Org>(Agency ID)
<User>(User Name)
<Password>
<Language>(optional)
<Currency>
<DebugMode>(optional)
<TestMode>(optional)
<Timeout>(optional)
<Version>
</Authority>
<User> String
<Language> Enum (optional)
The user’s logon, unique within the given organisation (User Name)
Override the organisation’s default language; accepts an ISO language identifier (e.g. en, fr, etc.); (Refer to the roomsXML Integration Portal)
<Org>
String The organisation short code identifying the agent responsible for the request (Agency ID)
<Password>
String The given user’s password
<Currency>
Enum Choose the currency used to return selling prices;
roomsXML.com API Specifications
Page 6 of 36