Chat with our AI Assistant to get instant answers on APIs, troubleshooting, and integration steps.
Ask ✨
Ctrlk
Sandbox LoginPartner ContactsBecome a SiteMinder Partner
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Error Handling

Learn how to handle and return error messages when using the SiteMinder Exchange API, including expected formats, retry strategies, and response codes.

It is expected that your application has a robust error-handling process in place. An error response should contain a short description of the error to assist our Support teams in troubleshooting.

Retry behaviour for failed reservation deliveries

When SMX receives an Error response from your application after attempting to deliver a reservation:

  • SMX retries the same reservation delivery every 30 seconds.

  • A maximum of 3 delivery attempts are made.

  • After the third failed attempt, the delivery times out and the reservation is marked as failed.

If the reservation still needs to be delivered after this point, the SiteMinder Exchange (SMX) Support team must manually flush and resend the reservation.

Error Responses using the <Errors> </Errors> tag will flag the reservation delivery from SMX to your endpoint as Failed.

Error Responses

HTTP Status should be 200 OK.

Invalid Hotel Code

<SOAP-ENV:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP-ENV:Body xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
        <OTA_HotelResNotifRS xmlns="http://www.opentravel.org/OTA/2003/05" Version="1.0" TimeStamp="2025-08-01T09:30:47+08:00" EchoToken="abc123-unique">
          <Errors>
            <Error Type="6" Code="392">Hotel not found for HotelCode=XXXXXX</Error>
          </Errors>
        </OTA_HotelResNotifRS>
    </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Invalid Username or Password

Warning Responses

HTTP Status should be 200 OK.

Any other warning responses that are not application or server-level issues should be sent as Success + Warning to avoid reservation delivery failures.

Our Reservations API specifications will have non-mandatory fields/attributes that a Publisher might not send in the reservation XML if it's not supported by them. Publishers should always send the mandatory reservation fields. Review our Reservations to view the mandatory and non-mandatory attributes.

Required Information Not Present - Missing email address

Required Information Not Present - Missing phone number

Recommended OTA Error Codes

SiteMinders recommends the following error codes to be used: Error Warning Types (EWT)and Error Codes (ERR)

SOAP Faults

Generally, OTA messages transmit "business logic" failures in the <Errors> element structure. However, a SOAP fault can be returned in case of an unexpected error caused by for example a SOAP message where the XML cannot be parsed. The SOAP Fault will identify the party at fault (CLIENT/SERVER).

sparkles

Still have questions?

Use the Ask button at the top of the page to chat with our AI assistant — it can help you navigate the guide, understand requirements, and troubleshoot issues.

If you need more support, visit Integration Support.

Last updated

Was this helpful?