Reference · built on requestConnectorHospitality & property systems

SiteMinder

Reservations, availability, and rates from hotels on SiteMinder, delivered to an application through SiteMinder Exchange (SMX).

Request accessPricing ↗

About

SiteMinder is a hotel distribution platform: a channel manager, a booking engine, and connections to property management systems. For applications that need hotel data, SiteMinder publishes SMX, the SiteMinder Exchange API. SMX pushes reservations, modifications, cancellations, and check-in and check-out statuses to your endpoint as OTA_HotelResNotifRQ messages, and serves availability and rates per publisher, hotel, and room type as JSON. Separate APIs (pmsXchange, SiteConnect, Channels Plus, Direct Booking) serve PMS vendors, booking channels, and hotel groups.

Through Fibric, an operator receives each reservation message, reads the availability behind it, and proposes actions in the systems it can write to, such as your PMS or messaging tools, for your approval.

This is a reference listing. It documents what Fibric would read from SiteMinder and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Reservations, modifications, and cancellations pushed to your endpoint as OTA_HotelResNotifRQ, answered with OTA_HotelResNotifRS
  • ResStatus values on each reservation: Reserved, Waitlisted, Cancelled, No-show, In-house, Checked-Out
  • Publishers connected to your application, and the hotels, room types, and rate plans under each
  • Availability per publisher, hotel, and room type by date: bookingLimit, minLOS, maxLOS, restriction type, and Open, Close, or OnRequest status
  • Rates for a rate plan code over a date range

Proposed actions

Read-only. Actions need a separate connector.

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Build the arrivals list from every channel

    Receive each OTA_HotelResNotifRQ as it lands, keep the current ResStatus per reservation, and propose the day's arrivals brief before the desk opens.

    With Arrival Prep, Morning Brief

  • Watch for a walk before it happens

    Compare bookingLimit and Close restrictions across room types for the next 30 days with incoming reservations, and propose an alert when inventory is oversold.

    With Walk Risk, Demand Outlook

  • Recover a cancelled stay

    On a Cancelled status, read the reservation and propose a follow-up message or an offer in your messaging tool for approval.

    With Service Recovery, Churn Watch

Requirements

  • A completed integration application and agreement with SiteMinder's Ecosystem team before test credentials are issued
  • A single global HTTPS endpoint on a registered domain name, TLS 1.2 or higher, no self-signed certificates, to receive OTA_HotelResNotifRQ
  • Each hotel submits SiteMinder's activation form itself, naming your application property code (HotelCode), its Property Publisher, and your application
  • SiteMinder's test scenarios completed before production; a pilot property may be required
Authentication
For reservation pushes, one WS-Security UsernameToken that SiteMinder places in the SOAP header of each request to your endpoint; for availability and rates, a JWT bearer token obtained through the SMX Subscriber Admin portal at exchange.siteminder.com.

Limits

  • SMX is read-only for applications; changes to reservations, rates, or availability go through the hotel's PMS or channel manager
  • Availability and rate queries cover at most 30 days per request, and ARI data is not available from Little Hotelier or SiteMinder Channel Manager publishers
  • One username and password covers every hotel; reservation messages are SOAP/XML, not JSON
  • A hotel stays connected and billed until the deactivation form is submitted

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request SiteMinder ↗

Questions and answers

Is SMX a pull or a push interface?
Both, by operation. Reservations are pushed: SiteMinder sends OTA_HotelResNotifRQ to your single HTTPS endpoint and expects OTA_HotelResNotifRS back. Availability and rates are pulled over REST with a JWT bearer token, per publisher, hotel, and room type, for up to 30 days at a time.
Can an application change a reservation through SiteMinder?
Not through SMX. The application path receives reservation, availability, and rate data. Writing availability, rates, restrictions, or reservations to SiteMinder is the pmsXchange API for property management systems and SiteConnect for booking channels, each with its own certification.
How does a hotel connect to an application on SMX?
The hotelier submits SiteMinder's activation request form directly, because it carries legal terms the property must accept. You give the hotel your application property code (HotelCode) and the form link; the hotel selects its Property Publisher and your application, and SiteMinder's Activation Team completes the connection.
Ask about SiteMinder

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with SiteMinder through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy