Hotel Policy Rooms and More Read

Supply the universal profile ID of the agency that you wish to retrieve configured Rooms and More locations for.

Sample Hotel Policy Rooms and More Read request data

xmlns:v1="http://www.travelport.com/schema/policy/admin/roomsandmore/v1”
<v1:performCRUDRQ>
         <v1:BasePolicyRequestHeader source="Web" requestorId="DaveS" accountId="451698" requestCategory="Read"/>
</v1:performCRUDRQ>

The following elements are supplied in a Read request:

performCRUDRQ / BasePolicyRequestHeader (requestCategory = Read)

Sample Hotel Policy Rooms and More Read response data

xmlns:ns4="http://www.travelport.com/schema/policy/admin/roomsandmore/v1"
xmlns:ns5="http://www.travelport.com/schema/policy/admin/common/v1"
<ns4:performCRUDRS>
         <ns4:BasePolicyResponseHeader accountId="451698" requestorId="DaveS"/>
         <ns5:AdditionalMessage iD="0" status="Processed"/>
         <ns4:RoomAndMoreResponseProfile>
            <ns4:TRMLocation id="22" locCode="AUSYD@" name="SYD">
               <ns4:Location country="AU" state="NS"/>
            </ns4:TRMLocation>
         </ns4:RoomAndMoreResponseProfile>
</ns4:performCRUDRS>

The following elements are found in a Read response:

performCRUDRS / BasePolicyResponseHeader

AdditionalMessage – overall status of the response
attribute: iD – “0” / not used on a Rooms and More Read
attribute: status – will be either “Processed” or “Failure”.

RoomAndMoreResponseProfile– wrapper element for Rooms and More data

TRMLocation - Rooms and More location
attribute: id - Policy DB id of this specific Rooms and More location
attribute: locCode - Rooms and More database code
attribute: name – name Agency wants to use to refer to this location

Location – wrapper element for location data
attribute: country – country code that this location exists in
attribute: state – state code that this location exists in (states are supported for AU/CA/US country codes only)

Considerations for a Hotel Policy Rooms and More Read

Rooms and More configurations are stored at the agency level and are available to all accounts under the agency.

A valid response will return status information in the AdditionalMessage section.

If you attempt to read data from an account on the uProfile hierarchy that is not an Agency you will get the following error:

<ns5:AdditionalMessage iD="0" name="Rooms And More" status="Failure">
            <ns5:Element iD="0" name="Rooms And More" status="Failure">
               <ns5:SubElement iD="0" name="Rooms And More" status="Failure">Invalid Agency</ns5:SubElement>
            </ns5:Element>
</ns5:AdditionalMessage>

If there are no Rooms and More locations configured under the requested Agency you will get the following error:

<ns5:AdditionalMessage iD="0" status="Failure">
            <ns5:Element iD="0" name=" Rooms And More " status="Failure">
               <ns5:SubElement iD="11" name=" Rooms And More " status="Failure">No Record Found</ns5:SubElement>
            </ns5:Element>
</ns5:AdditionalMessage>

Sample Request and Response

See the Downloads page to download a zip file containing the following XML files.

Sample request:

HotelPolicyTRMReadRQ.xml

Sample response:

HotelPolicyTRMReadRS.xml