RMS Inventory API

Owned by Rod De Sebastian Martin
Last updated: 21, Nov 2023 by Cian Ó Ceallaigh
2 min read

The connecting a Revenue Management System (RMS) should use OTA_HotelAvailNotifRQ to send restrictions, and OTA_HotelRateAmountNotifRQ to send rates and inclusions to pmsXchange.


General Guidelines for Inventory Updates

These guidelines must be followed by all connecting property management systems.

  • The HotelCode, InvTypeCode, RatePlanCode and RoomTypeCode are NOT codes provided by SiteMinder Channel Manager (they're not fixed/static). These codes can be adapted to fit your RMS (if the codes exist) OR our integrations team simply work with your support teams to generate them at the time of each hotel integration.

  • pmsXchange v2 only allows Inventory Updates for Room/Rate code combinations that are known to SiteMinder (i.e. have been setup and mapped to the RMS within the SiteMinder Channel Manager). Inventory messages (OTA_HotelAvailNotifRQ & OTA_HotelRateAmountNotifRQ ) containing an unmapped Inventory/Rate Code will fail to be applied in the property's SiteMinder Channel Manager.

  • The RMS should send only changes made by the operation performed in the RMS and not full refreshes or other operations. For example if rate changes from 500 to 400, the OTA_HotelRateAmountNotifRQ should only contain the rate change and no other data/operation (such as Stop Sell or MinLOS).

  • When a hotel is initially connected to pmsXchange a full refresh should be sent to load up the hotel data. After that only changes should be send and refreshes may only be sent under exceptional circumstances. In the case of a full refresh, the operations should be grouped within the same message.

  • Identical changes in rate should be grouped when possible. i.e if the rate value for a rate changes to 500 for the dates 1st and 2nd of October then one message should be sent to pmsXchange with the rate value 500 for the 1st and 2nd of October rather than 2 messages, one for each date.

  • Overlapping date range data is not to be sent in an Rate Message, all date ranges in a singular message should be unique for each room rate. 

  • The RMS should be able to resend messages if it is unable to connect to pmsXchange due to for example schedules outages.