FAQ

The Partner Integration Team has put together a list of common questions we get from our partners working on development to the SMX for PMS API.

We ask that you bookmark this page and refer to it regularly, as many questions you might have are likely to be answered here. Below we've broken up the FAQ into sections that relate to the different parts of the API.

If your question is not listed here, please contact the Partner Integration team via email.

1 General
2 Reservations API
3 Availability and Rate API

General

Any hotel who is using a SMX certified PMS and a SMX certified application can use the interface without the need to be a SiteMinder customer.

The PMSs listed on our website are connected to our Channel Manager, but not all have an agreement to publish any data to SMX.

pmsXchange and SMX are 2 different products that need to be built separately, and being in our PMS List in our web, does not imply that the PMS is available in SMX. The PMSs connected to SMX will have a ‘Hotel App Store’ logo. You can also find the list here: SMX PMSs Reservations Capabilities Table

Reservations API

Direct reservations made on the Publisher system must be delivered immediately to SMX.
Reservations made on any channel (OTA, Booking Engine, etc.) are delivered to The Channel Manager and to the Publisher. Once the publisher have a new reservation, it must be delivered immediately to SMX. If the hotel does not have a Channel Manager, the (OTA, Booking Engine, etc.) reservations must be created in the Publisher system and then delivered immediately to SMX.
Once the reservations reach SMX, those reservations are delivered immediately to the application.

You will always upload the reservations to your existing pmsXchange v2 endpoint. The authentication credentials are the same ones used in pmsXchange v2.

Availability and Rate API

If your PMS is pushing availability, rates and restrictions to pmsXchange, your data is ready to be used by SMX. No more action is needed.