Zenith API‎ > ‎1. Hotels‎ > ‎

3. Push availability and restrictions


Request

<OTA_HotelAvailNotifRQ xmlns="http://www.opentravel.org/OTA/2003/05" Version="1.0" TimeStamp="2015-11-11T11:11:11+00:00" EchoToken="12345678">
  <AvailStatusMessages HotelCode="HOTEL1">
    <AvailStatusMessage BookingLimit="10">
      <StatusApplicationControl Start="2015-02-01" End="2015-02-01" InvTypeCode="A1K" RatePlanCode="GLD"/>
      <RestrictionStatus Status="Close" />
    </AvailStatusMessage>
    <AvailStatusMessage>
      <StatusApplicationControl Start="2015-02-01" End="2015-02-01" InvTypeCode="A1K" RatePlanCode="GLD"/>
      <LengthsOfStay>
        <LengthOfStay MinMaxMessageType="SetMinLOS" Time="2"/>
      </LengthsOfStay>
    </AvailStatusMessage>
    <AvailStatusMessage>
      <StatusApplicationControl Start="2015-02-01" End="2015-02-01" InvTypeCode="A1K" RatePlanCode="GLD"/>
      <RestrictionStatus Status="Close" Restriction="Arrival"/>
    </AvailStatusMessage>
    <AvailStatusMessage>
      <StatusApplicationControl Start="2015-02-01" End="2015-02-01" InvTypeCode="A1K" RatePlanCode="GLD"/>
      <RestrictionStatus Status="Close" Restriction="Depature"/>
    </AvailStatusMessage>
  </AvailStatusMessages>
</OTA_HotelAvailNotifRQ>

 ItemType Description 
 AvailStatusMessages @HotelCodeString The hotel code for which the node relates to 
 AvailStatusMessage @BookingLimitIntegerAvailability. How many rooms are available for the type and rateplan inside 
 StatusApplicationControl @StartDate format: YYYY-MM-DD  the start date of the specific restriction
 StatusApplicationControl @EndDate format: YYYY-MM-DD  the start date of the specific restriction 
 StatusApplicationControl @InvTypeCodeStringThe room code for which the restriction applies to 
 StatusApplicationControl @RatePlanCodeStringThe rate plan for which the restriction applies to 
There a several supported scenarios for restrictions:
Setting Stop Sells, Closed to Arrival and Closed to Departure
Set the RestrictionStatus node in the following manner:
Room is stop sold
<RestrictionStatus Status="Close" />
Room is opened for sale
<RestrictionStatus Status="Open" />
Room is set as closed to arrival  
<RestrictionStatus Status="Close" Restriction="Arrival" />
Room is set as open to arrival
<RestrictionStatus Status="Open" Restriction="Arrival" />
Room is set as closed to departure
<RestrictionStatus Status="Close" Restriction="Departure" />
Room is set as open to departure
<RestrictionStatus Status="Open" Restriction="Departure" />

Setting Minimum Stay
In order to set a minimum stay restriction use the LengthsOfStay element. This element contains a single LengthOfStay element with the attributes @MinMaxMessageType and @Time. MinMaxMessageType has a fixed value of "SetMinLOS" or "SetMaxLOS" and the @Time it the minimum/maximum stay period in days. for example:
<LengthsOfStay>
    <LengthOfStay MinMaxMessageType="SetMinLOS" Time="2"/>
</LengthsOfStay>

Response

<OTA_HotelAvailNotifRS xmlns="http://www.opentravel.org/OTA/2003/05" Version="1.0" TimeStamp="2015-11-11T11:11:12+00:00" EchoToken="12345678">
  <Success/>
</OTA_HotelAvailNotifRS>

In case of Error
<OTA_HotelAvailNotifRS xmlns="http://www.opentravel.org/OTA/2003/05" Version="1.0" TimeStamp="2015-11-11T11:11:12+00:00" EchoToken="12345678">
  <Errors>
    <Error Type="6" Code="392">Cannot find hotelier with code HOTEL1</Error>
  </Errors>
</OTA_HotelAvailNotifRS>
Comments