Technical Guide
Explore the supported SOAP messages and REST endpoints available for the pmsXchange API
Last updated
Was this helpful?
Explore the supported SOAP messages and REST endpoints available for the pmsXchange API
Last updated
Was this helpful?
OTA_HotelAvailNotifRQ/RS
PMS → SiteMinder (PUSH)
Updates availability and restrictions
OTA_HotelRateAmountNotifRQ/RS
PMS → SiteMinder (PUSH)
Updates rates
OTA_ReadRQ/OTA_ResRetrieveRS
PMS ← SiteMinder (PULL)
Retrieves reservations, modifications, and cancellations
OTA_NotifReportRQ/RS
PMS → SiteMinder (PUSH)
Confirms that reservations, modifications, or cancellations have been processed
OTA_HotelResNotifRQ/RS
PMS → SiteMinder (PUSH)
Delivers reservations, modifications, and cancellations
SM_HotelResPaymentReadRQ/RS
PMS ← SiteMinder (PULL)
Retrieves payment transaction details
SM_HotelResPaymentResultRQ/RS
PMS → SiteMinder (PUSH)
Confirms the payment transaction has been processed and stored
/core-api/pmses/{pmsCode}/hotels/{hotelCode}/room-rates
GET - PMS ← SiteMinder (PULL)
Retrieves all configured room types and rate plans for the specified hotel
/core-api/pmses/{pmsCode}/hotels/{hotelCode}/reservation-import
POST - PMS → SiteMinder (PUSH)
Triggers the import job to retrieve active reservations for the hotel
In the SOAP 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).
The REST components of the pmsXchange API only support PMS-level authentication, which means using the same credentials across all properties. If you’re currently using hotel-level authentication (credentials per property), we recommend switching to PMS-level to ensure compatibility with the REST endpoints.