Page Comparison

No. SMX is built on the mentality of 'develop once, connect to many'. Once your connection is certified with SMX you will be able to connect to all available data publishers. SMX will handle any message conversion required.

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 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 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 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 be delivered and we don't understand why, we will let you know and once it has been fixed, we will resume the certification. This means you can "fail" it any number of times, the important thing is that at the end of this process we fixed all the issues.