RMS Developer Guide

• Intended Audience

• Communications

• Security

• OTA

• Supported Functions

• SMX for Apps

Intended Audience

This document is intended for developers and assumes the reader has working knowledge of XML and SOAP.

Communications

Communications between both systems is via the exchange of SOAP messages over secure HTTP (HTTPS). Operations are synchronous request/response pairs. A message is considered to be atomic and is either processed entirely or not at all by the Web Service.

Security

Encryption is provided by the transport layer via HTTPS. Each message contains a WS-Security (WSSE) UsernameToken SOAP header for authentication/authorisation purposes. Each connecting PMS will be provided with a username/password per hotel for authentication purposes.

OTA

The pmsXchange Web Service is based on the Open Travel Alliance (OTA) specifications for 2010A. Although this document attempts to be technically comprehensive it is expected that the connecting system’s developers be somewhat familiar with the OTA specifications found here http://www.opentravel.org.

Supported Functions

• OTA_HotelAvailNotifRQ - Used to update stop sell, minimum stay, maximum stay, closed to arrival and closed to departure.

• OTA_HotelRateAmountNotifRQ - Used to update rate and rate inclusions.

SMX for Apps

If you wish to consider receiving reservation data from the SiteMinder Channel Manager, or your Revenue Management System, you may wish to consider learning more about SMX For Apps. SMX is a product that is aimed at RMSs or applications, consisting multiple API's to allow applications to acquire data from the hoteliers RMS, without the need for proprietary integrations.