Developer Guide
Supported Messages
OTA_HotelAvailNotifRQ/RS- used to update availability, stop sell, minimum stay, maximum stay, closed to arrival and closed to departure.OTA_HotelRateAmountNotifRQ/RS- used to update rates.OTA_ReadRQ/OTA_ResRetrieveRS- used to retrieve reservations, modifications and cancellations.OTA_NotifReportRQ/RS- used to confirm that reservations, modifications or cancellations have been processed.SM_HotelResPaymentReadRQ/RS- used to pull payment transactions every 2-5 minutes per Hotel.SM_HotelResPaymentResultRQ/RS- used to confirm the payment transaction has been processed and stored by the PMS.
Best Practices
Queuing Mechanism
It is recommended that the PMS implements a queuing mechanism to manage upload messages in scenarios where connectivity with the pmsXchange service is unavailable, such as during network disruptions or scheduled release outages. If pmsXchange fails to respond, the PMS should retain the messages in the queue and automatically resend them once connectivity is re-established.
Multiplicity (M)
In the Specification tables M refers to the number of instances or occurrences of an element or attribute that are allowed or required in a given context. It defines how many times a particular component (element or attribute) can appear within a specific structure.
1
The element or attribute must be present exactly once.
0..1
The element or attribute is optional; it can be present zero or one time.
0..n
The element or attribute can be present zero or more times, with no upper limit (where n represents an infinite number of occurrences).
1..n
The element or attribute must be present at least once and can be present any number of times, with no upper limit.
n..m
Specific range, the element or attribute must be present at least n times and no more than m times (where n and m are specific numbers).
Last updated