Page Comparison

Overview

External channel will send reservations to Windsurfer CRS using the reservation notification request messages. Each reservation notification request will hold a single reservation record. Windsurfer CRS will send either success response with Windsurfer CRS confirmation code or error response with reasons for failure.

New, modified and cancelled reservations are all pushed by sending OTA_HotelResNotifRQ messages and receiving an OTA_HotelResNotifRS message in response.

The exchange of information between Windsurfer and external channel happens through the exchange of SOAP messages. Each message is contained within a SOAP envelope. All messages must contain an HTNG specified Soap Header that complies with WS Security (authentication only) and WS- Addressing standards.

General Design

The Availability, Rates and Inventory Notification Service provides three primary operations; one for updating restrictions/availability, one for updating rates based on base by GuestAmount and AdditionalGuestAmount, another for the inventory at room type level.  

Each operation involves the exchange of two OTA messages. Availability, Inventory and Restrictions are updated by sending an OTA_HotelAvailNotifRQ message and receiving an OTA_HotelAvailNotifRS message in response. Rates (BaseByGuestAmount / AdditionalGuestAmount) are updated by sending an OTA_HotelRateAmountNotifRQ and receiving an OTA_HotelRateAmountNotifRS in response.

Authentication

...

Introduction

All request messages exchanged between the Windsurfer and partners must be authenticated using the WS-Security mechanism of the SOAP standards. This should conform to the specification of HTNG Web Services Framework 2.1

The SOAP header elements are based on HTNG format and the elements are described below:

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" xmlns:a="
http://schemas.xmlsoap.org/ws/2004/08/addressing">
	<s:Header>
		<a:Action>http://cgbridge.rategain.com/2011A/ARIService/Availability</a:Action>
		<a:To>endpoint URL</a:To>
		<o:Security xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
			<o:UsernameToken>
				<o:Username>userName</o:Username>
				<o:Password>password</o:Password>
			</o:UsernameToken>
		</o:Security>
	</s:Header>
	<s:Body>
		
	</s:Body>
</s:Envelope>

SOAP Faults

SOAP Faults are provided as a mechanism for handling error conditions. A SOAP fault will be generated and returned if the message does not meet the web service specifications. It is also possible to receive this response occasionally, due to software malfunction on the Windsurfer side. The external channel system must be prepared to receive and process SOAP faults.

...