Table of Contents | ||||
---|---|---|---|---|
|
Info |
---|
Intended Audience This document is intended for developers and assumes the reader has working knowledge of |
...
Partners will need to provide SMX with a single web service endpoint to be used for message delivery. This endpoint must be global for all hotels using the connection, not for each individual hotel.
The endpoint must also accept incoming SMX requests with header 'Accept' with value application/xml
.
...
Security
Encryption is provided by the transport layer via HTTPS. Each message contains a WS-Security (WSSE) UsernameToken SOAP header for authentication/authorization purposes. Each connecting SMX Partner Application will need to provide a webservice endpoint to receive the reservation notifications.
...
Note |
---|
Response time should not exceed 1000ms. |
...
Reservations Historical Data
SiteMinder Exchange is able to send a flush of historical reservations data for a selected time period: 3 months, 6 months, 1 year etc. The time period is only based on the creation date (booked-on date) of the reservation so the flush might include future reservations that were created (booked) in the selected time frame. All ResStatus values are expected to be sent in the flush.
...
Process Flow
When a reservation is created, modified or cancelled in the partner PMS application (Reservation Uploader/Data Publisher) and is pushed to SiteMinder’s SMX platform, SiteMinder will generate a notification for each reservation event and PUSH reservation notifications to subscribing SMX partner applications. Partner applications will need to provide a webservice endpoint to receive the reservation notifications. The subscribing SMX partner applications can then use these reservations to offer value added solutions for the hospitality and travel industry.
...
If the
OTA_HotelResNotifRQ
message is delivered successfully by SiteMinder to the SMX partner application, the partner application's web service endpoint will need to respond with anOTA_HotelResNotifRS
success message.If the
OTA_HotelResNotifRQ
message delivery flags an error in the SMX partner application, the partner application's web service endpoint will need to respond with anOTA_HotelResNotifRS
error message, which should include an error string. The reservation will be retained in SMX's retry cycle and resent once the error is resolved. The message resend process may need to be done manually upon expiry of retry cycle time period.If the
OTA_HotelResNotifRQ
message is unable to be delivered to SMX partner application due to a network outage or similar connectivity issues, the reservation will be retained in SMX's retry cycle and resent once the error is resolved. The message resend process may need to be done manually upon expiry of retry cycle time period.
The SMX Partner Application should be able to accept all ResStatus values and respond with Success (200 OK status).
Reserved
Waitlisted
Cancelled
No-show
In-house
Checked-Out
Redacted
Child pages (Children Display) | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|