# Request message format

<table data-header-hidden><thead><tr><th></th><th></th><th></th><th></th><th width="156"></th></tr></thead><tbody><tr><td><strong>Element Path</strong> </td><td><strong>Attribute</strong> </td><td><strong>Occ</strong> </td><td><strong>Type</strong> </td><td><strong>Notes</strong></td></tr><tr><td>HotelML/Head/Process</td><td><br></td><td>1</td><td><br></td><td><br></td></tr><tr><td><br></td><td>DataPath</td><td>1</td><td>Char</td><td>Set to "/HotelML/Form/MultiAvailability”</td></tr><tr><td><br></td><td>Function</td><td>1</td><td>Char</td><td>Set to “TI_MultiAvailabilityV1_1”</td></tr><tr><td><br></td><td>Token</td><td>1</td><td>Char</td><td>Unique ID for the transaction generated by the system sending the transaction.</td></tr><tr><td><br></td><td>Timeout</td><td>0..1</td><td>Integer</td><td>Specifies the maximum time (in milliseconds) that UltraDirect should wait for responses from the CRSs before returning a response to the affiliate.<br><br>If the timeout expires before the rates and availability has been obtained for all properties then UltraDirect will return details to the affiliate of all properties that have responded. UltraDirect will also return a second response for all remaining properties if requested (by using the AcceptMultipartResponse attribute – see below).<br><br>If the attribute is omitted, the standard UltraDirect timeout value will be used.<br><br>If the requested timeout is greater than the UltraDirect standard timeout, the standard timeout will be used.</td></tr><tr><td><br></td><td>AcceptMultipart Reponse</td><td>0..1</td><td>Boolean</td><td>Specifies whether the requesting system will accept a response in multiple parts – i.e. the results for an initial set of properties after the affiliate- specified timeout expired, followed by the results for the remaining properties. This is implemented as a ‘chunked’ transfer-encoded HTTP response. If multi-part responses are not requested (i.e. the value is false or the attribute is omitted) then only one response will be returned.<br><br>This attribute is only applicable when the Timeout attribute is supplied. It will be ignored if Timeout is omitted.</td></tr><tr><td>HotelML/Head/Route</td><td><br></td><td>1</td><td><br></td><td><br></td></tr><tr><td><br></td><td>Source</td><td>1</td><td>Char 2-3</td><td>Identifies the organization sending the transaction. The value to use will be provided during the implementation project.</td></tr><tr><td><br></td><td>Destination</td><td>1</td><td>Char 2</td><td>Always set to “00” (i.e. zero zero).</td></tr><tr><td><br></td><td>RequestedAccuracy</td><td>0..1</td><td>Enum</td><td>This specifies whether the response can be generated from the UltraDirect transaction cache. Note: this is a preference, since it can be overridden by the hotel chain. Valid values are:<br>“CacheOrSource” (default if attribute is omitted) - First attempt to respond with data from the cache, but if data is not available, deliver the request to the source (hotel CRS) for processing.<br>“SourceOnly” - Bypass the cache and return availability from the source (hotel CRS) only.<br>“CacheOnly” - Only return data from the cache. If data is not available in the cache for the requested parameters, then an availability status of “Unknown” will be returned.<br><br>It is strongly recommended to set this to “CacheOrSource”.</td></tr><tr><td>HotelML/Form/MultiAvailability/ Property/Locale</td><td><br></td><td>0..1</td><td><br></td><td>This is used to request the room/rate information is returned in a specific language from the CRS (if available).</td></tr><tr><td><br></td><td>Language</td><td>1</td><td>Char 2</td><td>Language code – e.g. “FR”</td></tr><tr><td><br></td><td>Country</td><td>0..1</td><td>Char</td><td>Optional country name – e.g. “France”.</td></tr><tr><td>HotelML/Form/MultiAvailability/ Property</td><td><br></td><td>1..200</td><td><br></td><td>Repeated for each property.</td></tr><tr><td><br></td><td>Code</td><td>1</td><td>Char</td><td>Chain and property code, separated by a semi-colon – e.g. “UI;AB1234”</td></tr><tr><td></td><td>CodeContext</td><td>0</td><td>Char</td><td>Only used if partner is using their own property codes. partner's SGA code
<br>("AA" for Sabre)</td></tr><tr><td>HotelML/Form/MultiAvailability/ RateCriteria</td><td><br></td><td>1</td><td><br></td><td>Specifies rate selection criteria.</td></tr><tr><td><br></td><td>VersionCompliance</td><td>1</td><td>Enum</td><td>Valid values:
<br>“Enhanced_V1” (Standard EST functionality)
<br>“Enhanced_V2” (new functionality added for Sabre SAPI release)</td></tr><tr><td><br></td><td>  Usage</td><td>  0..1</td><td>  Enum</td><td>    Values are:<br>“PreBook” – re-check the rate and/or availability status prior to  making a booking<br>“CacheShopping” – availability transactions that are automatically generated by the demand partner’s system to fill and/or refresh a local cache.<br>“ProductDetails” – availability transaction to obtain additional information about a room/rate during the booking flow<br>“UserShopping” – availability transaction generated by an end-user event (e.g. searching on a website)<br>“Shop2Push” (RateGain Internal Use Only)</td></tr><tr><td><br></td><td>MatchingQualifier</td><td>0..1</td><td>Enum.</td><td>Valid only when at least one rate plan code<br>(RateCriteria/RateSearch/@RatePlanCode) is included in the request.<br>If “ExactAndPublic” the CRS should return the requested rate plans (if available) plus the public rates.<br>If “Exact” the CRS should return rates for the requested rate plans only.<br>If “ExactOrPublic” the CRS should return rates for the requested rate plans when available, or return public rates if requested rate plans are not available.</td></tr><tr><td></td><td>MaxRoomRateCount</td><td>0..1</td><td>Integer</td><td>Specifies the maximum number of room/rate combinations to return in the
<br>response.</td></tr><tr><td></td><td>PrePayQualifier</td><td>0..1</td><td>Char</td><td>Specifies whether prepaid or Non prepaid rates should be returned in the
<br>response.<br>Valid values are:
<br>“PrePayOnly” = Include Prepaid rates only
<br>“NoPrePay” = Exclude Prepaid rates
<br>“AllRates” = Return all rates</td></tr><tr><td></td><td>RefundableQualifier</td><td>0..1</td><td>Char</td><td>Specifies whether Refundable or Non Refundable rates should be returned in
<br>the response.<br>Valid values are:
<br>“Refundable” = Refundable rates only
<br>“NonRefundable” = Non Refundable rates only
<br>“AllRates” = Return all rates</td></tr><tr><td><br></td><td>CalculationMethod</td><td>0..1</td><td>Enum.</td><td>Specifies the preferred rate calculation method to use when a rate change occurs across the length of stay. Valid values are:<br>“First” – rate for the first night<br> “Highest” – highest nightly rate<br> “Average” – average nightly rate<br>“Frequent” – most frequently occurring rate<br>When this element is not included on the request, the CRS will apply their default method to calculate the rate range.</td></tr><tr><td><br></td><td>Commissionable Status</td><td>0..1</td><td>Enum.</td><td>Specifies whether commissionable and/or non-commissionable rate are required.<br>“Commissionable” = Return commissionable rates only<br>“NonCommissionable” = Return non-commissionable rates only<br>“Both” = Return both non-commissionable and commissionable rates. This is the default if not sent.</td></tr><tr><td><br></td><td>ReturnUnavailable</td><td>0..1</td><td>Boolean</td><td>If “true”, closed properties will be included in the response.<br>If “false”, closed properties will not be included in the response.</td></tr><tr><td><br></td><td>NumberOfAdults</td><td>1</td><td>Integer</td><td>This attribute is deprecated – should use GuestCount element instead.</td></tr><tr><td><br></td><td>NumberOfChildren</td><td>0..1</td><td>Integer</td><td>This attribute is deprecated – should use GuestCount element instead.</td></tr><tr><td><br></td><td>NumberOfRooms</td><td>1</td><td>Integer</td><td>Total number of rooms required, which is used when checking availability. The prices in the response will be per room.</td></tr><tr><td><br></td><td>NumberOfBeds</td><td>0..1</td><td>Integer</td><td>Preferred number of beds per room</td></tr><tr><td><br></td><td>BedType</td><td>0..1</td><td>Enum</td><td>Indicates the preferred bed type. Values are:<br>Single, Twin, Double, King, Queen, Futon, MurphyBed, SofaBed, TatamiMats, Rollaway, Crib</td></tr><tr><td><br></td><td>ReturnRateChanges</td><td>0..1</td><td>Boolean</td><td>Preference for whether response should include each distinct rate if it changes during the stay.</td></tr><tr><td><br></td><td>RoomCategory</td><td>0..1</td><td>Enum</td><td>Indicates the preferred quality of room. The following values are most commonly used:<br>Deluxe, Superior, Standard, Moderate, Economy, Premium<br>The attribute also supports the following values but these are generally not used in this context:<br><br>FirstClass, Budget, Upscale, Luxury, MeetingConvention, ResidentialApartment, Resort, CorporateBusinessTransient, AllSuite, ExtendedStay, Tourist, Efficiency</td></tr><tr><td>HotelML/Form/MultiAvailability/ RateCriteria/GuestCount</td><td><br></td><td>0..M</td><td><br></td><td>This element specifies the number of adults and children (optionally including child counts by age).<br><br>GuestCount must occur once (and only once) with Type=”Adult”.<br><br>It can also occur once with Type=”Child” if no Age attribute is supplied. Alternatively, it can multiple times for Type=”Child” when an Age attribute is specified.<br><br>It should be used instead of the NumberOfAdults and NumberOfChildren attributes of PropertyRate because it allows the age of each child to be specified.</td></tr><tr><td><br></td><td>Type</td><td>1</td><td>Enum</td><td>Values “Adult” or “Child”</td></tr><tr><td><br></td><td>Count</td><td>1</td><td>Integer</td><td>Number of guests of this type</td></tr><tr><td><br></td><td>Age</td><td>0..1</td><td>Integer</td><td>The optional age of the guest. Only applicable when Type=”Child”.</td></tr><tr><td>HotelML/Form/MultiAvailability/ RateCriteria/ExtraBed</td><td><br></td><td>0..1</td><td><br></td><td>This is used to request rollaway beds or cots/cribs. The element can occur up to three times - once for each type of extra bed – as defined by the Type attribute.</td></tr><tr><td><br></td><td>Type</td><td><br></td><td>Enum</td><td>Type of extra bed required. Valid values are:<br>AdultRollAway, ChildRollAway, Crib</td></tr><tr><td><br></td><td>Number</td><td><br></td><td>Integer</td><td>The number of beds of this type</td></tr><tr><td>HotelML/Form/MultiAvailability/ RateCriteria/AgentInfo</td><td><br></td><td>0..1</td><td><br></td><td><br></td></tr><tr><td><br></td><td>Number</td><td>1</td><td>Char 8</td><td>Travel agent identifier – often the IATA number.</td></tr><tr><td><br></td><td>Type</td><td>1</td><td>Enum.</td><td>Identifies the type of travel agent identifier. Values are: “ARC” , “IATA”, “TIDS”,  “CLIA”,  “AAA”,  “GDS”, “Other”.</td></tr><tr><td><br></td><td>City</td><td>0..1</td><td>Char 3</td><td>Originating Agent’s City. Not normally required.</td></tr><tr><td><br></td><td>Country</td><td>0..1</td><td>Char 2</td><td>Originating Agent’s Country Code (ISO Standard Codes). Not normally required.</td></tr><tr><td>HotelML/Form/MultiAvailability/ RateCriteria/Amenity</td><td><br></td><td>0..6</td><td><br></td><td>This is used to request specific room or rate features, such as breakfast (“BRKFST”) or a non-smoking room (“NSMK”) etc.</td></tr><tr><td><br></td><td>Code</td><td>1</td><td>Char 6</td><td>The list of codes can be obtained using the AmenityInformation transaction.</td></tr><tr><td>HotelML/Form/MultiAvailability/ RateCriteria/DateRange</td><td><br></td><td>1</td><td><br></td><td><br></td></tr><tr><td><br></td><td>InDate</td><td>1</td><td>Date</td><td>The arrival date in format “2011-12-24”</td></tr><tr><td><br></td><td>OutDate</td><td>1</td><td>Date</td><td>The departure date in format “2011-12-27”</td></tr><tr><td>HotelML/Form/MultiAvailability/ RateCriteria/PriceRange</td><td><br></td><td>0..1</td><td><br></td><td>Specifies the required maximum and/or minimum rate (per room per night). Rarely used.</td></tr><tr><td><br></td><td>Currency</td><td>1</td><td>Char</td><td>ISO currency code – e.g. “USD”</td></tr><tr><td><br></td><td>Max</td><td>0..1</td><td>Decimal</td><td>Maximum required daily rate per room - e.g. “150.00”</td></tr><tr><td><br></td><td>Min</td><td>0..1</td><td>Decimal</td><td>Minimum required daily rate per room - e.g. “150.00”</td></tr><tr><td>HotelML/Form/ MultiAvailability/ RateCriteria/RateSearch</td><td><br></td><td>0..M</td><td><br></td><td>The RateSearch element is used to request one or more specific rate plan codes. This is used in conjunction with PropertyRate/@MatchingQualifier to specify whether the CRS should return the requested rate plans and/or public rates.<br><br>If this element is not present, the CRS may return any available rate plan codes it wishes to promote.<br><br>A maximum of 15 rate plan codes can be supplied in the RateSearch element for each hotel chain.</td></tr><tr><td><br></td><td>RatePlanCode</td><td>0..1</td><td>Char 10</td><td>Rate access code.<br><br>This can be used to request special types of rate, such as specific negotiated or corporate rates. If this functionality is required, the actual RatePlanCode and RatePlanType to send will be provided to the affiliate by the hotel chain or RateGain as part of the UltraDirect implementation project.<br><br>Also, many hotels recognize the following standard (generic) rate plan codes. These all require RatePlanType=”Standard”.<br><br>"PRO" = Promotional<br> "COR" = Corporate<br> "WKD" = Weekend<br> "RAC" = Rack<br>"SNR" = Senior<br>"GOV" = Government<br>"MIL" = Military<br>"PKG" = Package<br>“WEB” = Web/Internet<br>“CLB” = Club<br>“FAM” / “FPM” = Family<br>“CVN” or “CNV” = Convention<br>"TVL” = Travel Agent<br>"TUR" = Tour</td></tr><tr><td><br></td><td>RatePlanType</td><td>0..1</td><td>Char</td><td>Specifies the type of RatePlanCode. Values are:<br>Corporate, Negotiated, NetRate, Standard</td></tr><tr><td><br></td><td>BrandCode</td><td>0..1</td><td>Char 6</td><td>If BrandCode is specified then the information in the RateSearch element (such as rate plan code, corporate customer number, frequent guest number etc.) would only be included in transactions to the specified chain’s Central Reservation System (CRS). If the BrandCode is not supplied then the information will be included in transactions to all hotel chains’ CRSs.<br><br>It should therefore be used when information in the RateSearch element is specific to a hotel chain.</td></tr><tr><td>HotelML/Form/MultiAvailability/ RateCriteria/RateSearch/AutoInfo</td><td>Code</td><td>0..1</td><td>Char 25</td><td>Auto Frequent Traveler Number</td></tr><tr><td>HotelML/Form/MultiAvailability/ RateCriteria/RateSearch/CorpInfo</td><td>Code</td><td>0..1</td><td>Char 25</td><td>Corporate Account Number. This should only be sent when<br>RateSearch/@RatePlanType=”Corporate”.</td></tr><tr><td>HotelML/Form/MultiAvailability/ RateCriteria/RateSearch/FlyerInfo</td><td>Code</td><td>0..1</td><td>Char 25</td><td>Frequent Flyer Number</td></tr><tr><td>HotelML/Form/MultiAvailability/ RateCriteria/RateSearch/FreqGuest</td><td>Code</td><td>0..1</td><td>Char 25</td><td>Frequent Guest Number</td></tr></tbody></table>