Overview
SMX is an any-to-any data exchange that connects various applications that help hotels acquire and manage guests better to PMS data without the need for proprietary integrations. Both ends of the supply chain win by being able to focus on building out their product, not connectivity. It contains a set of Open Travel Alliance (OTA) based messages that allows a PMS providers to push reservations to SMX and be passed on to SMX Partner Applications.
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 SMX Partner Application will need to provide a webservice endpoint to receive the reservation notifications.
OTA
The SMX For PMS API is based on the Open Travel Alliance (OTA) specifications for 2017A. 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_HotelResNotifRQ - Used to push reservation notifications to SMX via pmsXchange.
