Unavailable Properties

If a requested property is unavailable, a Property element is returned with the AvailabilityStatus set to “Closed.” This element will also include the ClosedReason attribute, which indicates the reason for the closure.

Additionally, an Error element is returned, often providing further details. The ResponseDataPath attribute within the Error element will reference the specific property ID related to the issue.

Below is an example response for a request involving three properties, where one is unavailable (edited for clarity):

<HotelML xmlns="http://www.xpegs.com/v2001Q3/HotelML" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Head>
<Route Destination="01" Source="00">
<Operation Action="Create" App="TIDispatcher" AppVer="1.12.40.2.8.1"
DataPath="/HotelML" StartTime="2010-09- 07T08:13:36.688+00:00" Success="true"
TotalProcessTime="228"/>
</Route>
<Error Code="IND12" Description="CTA RESTRICTION ON IN DATE"
ResponseDataPath="Hotel/Property@Code='XX;1111'" Type="Process"/>
</Head>
<Property xml:lang="en" AvailabilityStatus="Closed" ClosedReason="Unavailable" Code="XX;1111" />
<Property xml:lang="en" Code="XX;2222" AvailabilityStatus="Open">
... Room & Rate Details ....
</Property>
<Property xml:lang="en" Code="XX;3333" AvailabilityStatus="Open">
... Room & Rate Details ....
</Property>
</HotelML>

PreviousUltraDirect Account Author Negotiated Rate Processing NextUltraDirect Cache Processing

Last updated 1 year ago