SOAP Message Structure


All messages exchanged with HotelRunner are soap messages. They include a SOAP Security header for authentication purposes and contain the SOAP Body contains the OTA message. The following example is a complete SOAP message.



<soap:Envelope xmlns:soap="">

    <wsse:Security soap:mustUnderstand="1" xmlns:wsse="">
        <wsse:Password Type="">TOKEN</wsse:Password>


 <OTA_ReadRQ xmlns="" Version="1.0" TimeStamp="2016-04-01T12:31:47+03:00" Version="1.0" EchoToken="echo-1903">
      <RequestorID Type="22" ID="PMS1"/>
    <HotelReadRequest HotelCode="ABC">
      <SelectionCriteria SelectionType="Undelivered" ResStatus="Modify"/>


SOAP Security Header

The Security Header structure conveys authentication information. It is mandatory and both the /wsse:UsernameToken/wsse:Username and /wsse:UsernameToken/wsse:Password elements are mandatory.
Each connecting HotelRunner partner will be allocated a USERNAME* and PASSWORD* per property for use with this header.


SOAP Faults

Generally OTA messages transmit "business logic" failures in the 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).

<SOAP-ENV:Envelope xmlns:SOAP-ENV="">
      <faultstring xml:lang="en" xmlns:xml="">
        Authentication failed - invalid username