Page Comparison

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

Data publishers should send through an updated version of the reservation message when it is modified within their system. This can include events such as a reservation status being adjusted to In-house (the guest is checked in), a guest has been moved to another room, or a modification was being received from the booking source (ie: Booking.com).

In most scenarios, the data publisher can simply push the data through to SMX and it will be passed on to you. However, you will need to discuss with the data publisher to determine if they are able to can push through historical data.

• ResGuest: This will contain the details of the 'staying' guest if provided by the data publisher.

• ResGlobalInfo: This will contain the details of the 'booking' customer, and may also contain details of business, wholesaler or travel agent information

It is a good idea to ensure you are able to can use both the ResGuest and ResGlobalInfo profiles, as it cannot be guaranteed that both will always be sent.

SMX can only provide you with reservation data that is sent by the data publisher. It is expected that your system will be able to return an appropriate Success+Warning response for missing data or an Error message in the event that if a reservation message cannot be processed. Please refer to the Error Handling section of the documentation for more detaildetails.

No. SMX is derived from the Open Travel Alliance (OTA) industry standards, which uses use SOAP XML. At the time SMX was created, JSON was not a supported message format. However, there are plans to introduce a JSON version of the reservation API in the future.

We ask you to provide us with an identifier for the hotelier within your system as this ensures that the HotelCode attribute within each message is unique to your system and in a format you are able to can handle. As we connect to multiple data publishers, there is the possibility that duplicate codes will exist between these data publishers (ie: HOTEL1 may exist in 2 different data publishers).

Certification The certification process is very straightforward. We will create some reservations (some of them will be modified and/or cancelled) and will verify that all of them will trigger either a successful response or a meaningful error response. Your responses should be well in line with our OTA_HotelResNotifRS specifications. We will also test sending through our Minimum and Maximum content samples.

 If some reservations trigger an error (for instance, due to missing data), this error must be as eloquent as possible and it should not impact the http status that which should remain as 200. If you have server-level issues, then it is OK to respond with HTTP standard error codes. See our Error Handling specs for more details.

The only thing that is required from your side is to leave your endpoint up and running until we complete certification.

 If there's an issue with your responses or some of the reservations could not cannot be delivered and we don't understand why, we will let you know and once . Once it has been fixed, we will resume the certification. This means you can "fail" it any number of times, the . The important thing is that at the end of this process, we fixed all the issues.

No, Little Hotelier and The Channel Manager are not pushing yet ARI data to SMX just yet.