Overview
Intended Audience
This document is intended for developers and assumes the reader has working knowledge of JSON.
Introduction
Partner Applications will be able to query SMX for a variety of functions relating to the partner's subscription setup.
The response will be sent as a JSON message.
Communications
Communications between both systems is via the exchange of JSON messages over secure HTTP (HTTPS). Operations are synchronous request/response pairs.
OTA
The Availability and Rate API is derived from the Open Travel Alliance (OTA) specifications for 2017A.
Process Flow
Data is uploaded by the partner PMS application (Data Publisher) and is stored in SiteMinder's SMX platform. SMX Partner Applications can query SMX to retrieve the data for their subscribing hoteliers. Partner applications will need to use an authentication token that can be generated through the SMX Admin portal. The SMX Partner Application can use this data to offer value added solutions for the hospitality and travel industry.
Security
Encryption is provided by the transport layer via HTTPS. Each message contains a BearerAuthorization token that is unique to that partner application.
Endpoints
DNS TTL should be respected. IP addresses should not be cached indefinately by the connecting application. Doing so will result in connection timeouts.