Query & Hints XML Reference

This section provides a reference for the XML-based Query, QueryControl, and hint-related messages.

<Hint> (Hint Response message)

The root element of a Hint Response message. Hint Response messages specify which hotel/itinerary combinations should be repriced. They are your response to a Hint Request message from Google.

A Hint Response message should specify only those hotels whose prices have changed since the last time Google received a successful Hint Response from your servers.

Hint Response messages use one of the following methods to specify which hotels and itineraries Google should reprice:

  • Exact itineraries: A combination of check-in date and length of stay.
  • Check-in date ranges: Specifies a range of check-in dates, beginning with the first check-in date and ending with the last check-in date.
  • Ranged stays (or ranged itineraries)

Each of these methods requires a different syntax for the Hint Response message.

For more information, see Hint Response Messages.

<Hint> syntax

The <Hint> element uses different syntax, depending on the type of Hint Response message:

Exact Itineraries

The following shows the syntax for exact itineraries in a Hint Response message:

<!-- Exact Itinerary Hint Response -->
<?xml version="1.0" encoding="UTF-8"?>
<Hint>
  <Item>
    <Property>hotel_ID</Property>
    ...
    <Stay>
      <CheckInDate>checkin_date</CheckInDate>
      <LengthOfStay>number_of_nights</LengthOfStay>
    </Stay>
  </Item>
  ...
</Hint>

Check-in Ranges

The following shows the syntax for check-in ranges in a Hint Response message:

<!-- Check-in Ranges Hint Response -->
<?xml version="1.0" encoding="UTF-8"?>
<Hint>
  <Item>
    <!-- At least one is required -->
    <!-- Can be > 1 if MultipleItineraries is "checkin_range" in your QueryControl message -->
    <Property>hotel_ID</Property>
    [...]

    <!-- Required -->
    <FirstDate>first_checkin_date</FirstDate>
    <!-- Required -->
    <LastDate>last_checkin_date</LastDate>
  </Item>
  ...
</Hint>

Ranged Stays

The following shows the syntax for ranged stays in a Hint Response message:

<!-- Ranged Stay Hint Response -->
<?xml version="1.0" encoding="UTF-8"?>
<Hint>
  <Item>
    <!-- At least one is required -->
    <!-- Can be > 1 if MultipleItineraries is "affected_dates" in your QueryControl message -->
    <Property>hotel_ID</Property>
    [...]

    <StaysIncludingRange>
      <!-- Required -->
      <FirstDate>first_date</FirstDate>

      <!-- Optional -->
      <LastDate>last_date</LastDate>
    </StaysIncludingRange>
  </Item>
  ...
</Hint>

<Hint> attributes

The <Hint> element has no attributes.

<Hint> child elements

The <Hint> element has the following child elements:

Child Element Required? Type Hint Response Type Description
<CheckInDate> Required Date Exact itineraries The check-in date for the itinerary.
<FirstDate> Required Date Check-in ranges and ranged itineraries The first date of the date range for a check-in range or ranged stay Hint Response message. Dates are inclusive.
<Item> Required Object All A container for the hotel/itinerary to be updated.
<LastDate> Required* Date Check-in ranges and ranged itineraries The last date of the date range for a check-in range or ranged stay Hint Response message. Dates are inclusive.

* This element is optional for ranged stays.

<LengthOfStay> Required Integer Exact itineraries The number of nights for the itinerary, expressed as a positive integer.
<Property> Required String All The ID of a hotel, using the same ID as the Hotel List Feed. The number of <Property> elements you can specify in a single <Item> block is determined by the type of Hint Response message:

  • Exact itineraries: Up to 100 hotels.
  • Check-in ranges: More than one if you set <MultipleItineraries> to "checkin_range" in your <QueryControl> message.
  • Ranged stay: More than one if you set <MultipleItineraries> to "affected_dates" in your <QueryControl> message.

For more information, see QueryControl Messages.

<Stay> Required Object Exact itineraries A container for the <CheckinDate> and <LengthOfStay> elements in an exact itinerary Hint Response message. Each <Item> can contain only a single <Stay>.
<StaysIncludingRange> Required Object Ranged itineraries A container for the <FirstDate> and <LastDate> elements in a ranged stay Hint Response message.

<Hint> examples

Exact Itineraries

The following example defines multiple itineraries for a single property a Hint Response message:

<!-- Exact Itinerary Hint Response -->
<?xml version="1.0" encoding="UTF-8"?>
<Hint>
  <Item>
    <Property>12345</Property>
    <Stay>
      <CheckInDate>2018-07-03</CheckInDate>
      <LengthOfStay>3</LengthOfStay>
    </Stay>
  </Item>
  <Item>
    <Property>12345</Property>
    <Stay>
      <CheckInDate>2018-07-03</CheckInDate>
      <LengthOfStay>4</LengthOfStay>
    </Stay>
  </Item>
</Hint>

Check-in Ranges

The following example specifies two hotels whose pricing has changed and should be fetched again. Google gets all itineraries between July 3 and July 6 for properties 12345 and 67890:

<!-- Check-in Ranges Hint Response -->
<?xml version="1.0" encoding="UTF-8"?>
<Hint>
  <Item>
    <Property>12345</Property>
    <Property>67890</Property>
    <FirstDate>2018-07-03</FirstDate>
    <LastDate>2018-07-06</LastDate>
  </Item>
</Hint>

Note that for a check-in range message to be able to specify multiple properties in a single <Item>, the value of <MultipleItineraries> in <QueryControl> must be set to "checkin_range".

Ranged Stays

The following example shows two different uses of ranged stays, one for a range of nights and the other for a single night:

<!-- Ranged Stay Hint Response -->
<?xml version="1.0" encoding="UTF-8"?>
<Hint>
  <!-- Google fetches prices for all itineraries (first and last date are set) -->
  <Item>
    <Property>12345</Property>
    <StaysIncludingRange>
      <FirstDate>2018-07-03</FirstDate>
      <LastDate>2018-07-06</LastDate>
    </StaysIncludingRange>
  </Item>

  <!-- Google fetches prices for a single night (first date only) -->
  <Item>
    <Property>67890</Property>
    <StaysIncludingRange>
      <FirstDate>2018-07-03</FirstDate>
    </StaysIncludingRange>
  </Item>
</Hint>

Note that for a ranged stay message to be able to specify multiple properties in a single <Item>, the value of <MultipleItineraries> in <QueryControl> must be set to "affected_dates".

For each of these examples, Google responds with a <Query>, and you should then respond with a <Transaction> that includes price updates for the specified hotels/itineraries.

<HintRequest>

The root element of a Hint Request message. Google sends a Hint Request message to your server and expects a response that specifies the hotels and itineraries whose prices have changed since the last time Google received a successful Hint Response from your server.

If there are any price changes, Google then sends a <Query> that fetches the updated pricing data for the indicated hotels and itineraries.

For more information, see Hint Request Messages.

<HintRequest> syntax

The <HintRequest> element uses the following syntax:

Syntax

<?xml version="1.0" encoding="UTF-8"?>
<HintRequest>
  <LastFetchTime>last_fetch_time</LastFetchTime>
</HintRequest>

<HintRequest> attributes

The <HintRequest> element has no attributes.

<HintRequest> child elements

The <HintRequest> element has the following child elements:

Child Element Type Description
<LastFetchTime> DateTime The last time that Google succeeded in getting a Hint Response message to a Hint Request message.

If this time is older than the last time you updated prices on your server, then you should respond with a Hint Response message specifying which hotels have changed.

For more information, see Hint Response Messages.

<HintRequest> examples

Example

The following example shows a Hint Request message:

<?xml version="1.0" encoding="UTF-8"?>
<HintRequest id="ABCDEF" timestamp="2018-06-07T16:20:00Z">
  <LastFetchTime>2018-03-25T00:04:09Z</LastFetchTime>
</HintRequest>

<Query>

The root element of a Query message. Query messages are requests from Google for pricing or metadata updates. They are used with both the Pull and Pull with Hints delivery modes.

There are two types of Query messages:

  • Pricing: Google requests pricing updates for the specified hotels. When you receive a pricing Query message, you should respond with a <Transaction> message that contains the requested pricing information in <Result> elements.

    Live Queries are a special type of pricing Query message in which Google asks for real-time price updates.

    For more information, see Pricing Overview.

  • Metadata: Google requests metadata updates for the rooms and Room Bundles for the specified hotels. When you receive a metadata Query message, you should respond with a <Transaction> message that specifies data about the rooms and Room Bundles in <PropertyDataSet> elements.

    For more information, see Room Bundle metadata.

The syntax for the messages is different, depending on the type. Both types are described in this section.

<Query> syntax

The <Query> element uses the following syntax:

Syntax

<?xml version="1.0" encoding="UTF-8"?>
<Query>

  <!-- PRICING QUERIES -->
    <Checkin>YYYY-MM-DD</Checkin>

    <Nights>number_of_nights</Nights>

    <!-- Only for Check-in Date Range pricing queries (Pull + Hints) -->
    <FirstDate>YYYY-MM-DD</FirstDate>
    <LastDate>YYYY-MM-DD</LastDate>

    <!-- Only for Ranged Stay pricing queries (Pull + Hints) -->
    <AffectedNights>number_of_nights</AffectedNights>

    <PropertyList>
      <Property>hotel_id</Property>
       ...
    </PropertyList>

    <!-- Only for Live Queries -->
    <LatencySensitive>[false|true]</LatencySensitive>
    <DeadlineMs>deadline</DeadlineMs>

  <!-- METADATA QUERIES -->
    <HotelInfoProperties>
      <Property>property_ID</Property>
      ...
    </HotelInfoProperties>

</Query>

<Query> attributes

The <Query> element has no attributes.

<Query> child elements

The <Query> element has the following child elements:

Child Element Query Type Type Description
<AffectedNights> Pricing Integer The number of nights for a ranged stay. This element is used only for Ranged Stay pricing queries used with Pull with Hints.
<Checkin> Pricing Date The dates of a specific price change.
<DeadlineMs> Pricing (Live Queries only) Number The amount of time, in milliseconds, that you have to respond to a Live Query. If you respond with a price within this amount of time, then your ad can be included in the auction. If you do not respond within this amount of time, then you risk not being part of the auction.

The presence of this value indicates that the request is a Live Query. Messages that do not include this element are not Live Queries.

For more information, see Live Queries.

<FirstDate> Pricing Date The start date for a range of itineraries to which the pricing applies. This element is used only for Check-in Date Range pricing queries used with Pull with Hints.
<HotelInfoProperties> Metadata String One or more properties for which Google wants updated room and Room Bundle metadata in a metadata Query message. This element can contain one or more <Property> elements that specify hotel property IDs.
<LastDate> Pricing Date The end date for a range of itineraries to which the pricing applies. This element is used only for Check-in Date Range pricing queries used with Pull + Hints.
<LatencySensitive> Pricing (Live Queries only) Boolean "true" if the request is a Live Query. Otherwise, "false".

When set to "true", you must respond to the Live Query within the number of milliseconds specified by <DeadlineMs>.

For more information, see Live Queries.

<Nights> Pricing Integer The number of nights for a particular itinerary, up to 14.
<PropertyList> Pricing Object One or more IDs for hotel that require pricing updates.

Define each hotel in a <Property> element. The value is a string that matches a hotel ID in your Hotel List Feed. For example:

<PropertyList>
  <Property>pid1</Property>
  <Property>pid2</Property>
</PropertyList>

<Query> examples

Pricing Query

The following example shows a pricing Query message that requests price updates for a set of hotels, available for 3 nights, and starting on June 10, 2018:

<?xml version="1.0" encoding="UTF-8"?>
<Query>
  <Checkin>2018-06-10</Checkin>
  <Nights>3</Nights>
  <PropertyList>
    <Property>pid5</Property>
    <Property>pid8</Property>
    <Property>pid13</Property>
    <Property>pid21</Property>
  </PropertyList>
</Query>

Live Query

The following example shows a Live Query with a response time limit of 500 milliseconds:

<?xml version="1.0" encoding="UTF-8"?>
<Query>
  <Checkin>2018-06-07</Checkin>
  <Nights>46</Nights>
  <PropertyList>
    <Property>8675309</Property>
  </PropertyList>
  <LatencySensitive>true</LatencySensitive>
  <DeadlineMs>500</DeadlineMs>
</Query>

Metadata Query

The following example shows a metadata Query message:

<?xml version="1.0" encoding="UTF-8"?>
<Query>
  <HotelInfoProperties>
    <Property>pid5</Property>
    <Property>pid8</Property>
    <Property>pid13</Property>
    <Property>pid21</Property>
  </HotelInfoProperties>
</Query>

For additional examples, including ranged stay and check-in date range pricing queries, see Query message examples.

<QueryControl>

The root element of a Query Control message. Query Control messages define the number of days in advance of check-in for the stay that will be queried by Google. You can also use Query Control messages to override these values for certain properties. In addition, you can use Query Control messages to exclude properties from being repriced.

The Query Control message schema defines the structure and constraints of a Query Control message.

You can use the Feed Validation tool in Hotel Ads Center to ensure that your Query Control messages conform to this schema. For more information, see Tools.

For more information, see Query Control Messages.

<QueryControl> syntax

The <QueryControl> element uses the following syntax:

Syntax

<?xml version="1.0" encoding="UTF-8"?>
<QueryControl>
  <ItineraryCapabilities>

    <!-- Define one DefaultValue block for all hotels -->
    <DefaultValue>
      <State>[enabled|disabled]</State>
      <MinAdvancePurchase>min_advanced_purchase</MinAdvancePurchase>
      <MaxAdvancePurchase>max_advanced_purchase</MaxAdvancePurchase>
      <MinLengthOfStay>min_length_of_stay</MinLengthOfStay>
      <MaxLengthOfStay>max_length_of_stay</MaxLengthOfStay>
    </DefaultValue>

    <!-- Define any number of PropertyOverride blocks -->
    <PropertyOverride>
      <State>[enabled|disabled]</State>
      <MinAdvancePurchase>min_advanced_purchase</MinAdvancePurchase>
      <MaxAdvancePurchase>max_advanced_purchase</MaxAdvancePurchase>
      <MinLengthOfStay>min_length_of_stay</MinLengthOfStay>
      <MaxLengthOfStay>max_length_of_stay</MaxLengthOfStay>
      <!-- At least one property is required for each PropertyOverride block -->
      <Property>hotel_ID</Property>
      ...
    </PropertyOverride>
    ...
  </ItineraryCapabilities>

  <HintControl>
    <!-- Optional. For use with hints only. -->
    <MultipleItineraries>[checkin_range|affected_dates]</MultipleItineraries>
  </HintControl>

  <!-- Deprecated. Use <PropertyOverride> instead. -->
  <Item>
    <Property>hotel_ID</Property>
    <MaxAdvancePurchase>max_advanced_purchase</MaxAdvancePurchase>
    <MaxLengthOfStay>max_length_of_stay</MaxLengthOfStay>
  </Item>

</QueryControl>

<QueryControl> attributes

The <QueryControl> element has no attributes.

<QueryControl> child elements

The <QueryControl> element has the following child elements:

Child Element Required? Type Description
<HintControl> Optional <HintControl> Configures your Hint Response messages.
<Item> (Deprecated) Optional <Item> Defines repricing settings for the properties within the current block.
<ItineraryCapabilities> Optional <ItineraryCapabilities> Defines default itinerary settings and property-specific overrides.

<QueryControl> examples

Example 1

The following example Query Control message defines the default pricing settings for all hotels:

<?xml version="1.0" encoding="UTF-8"?>
<QueryControl>
  <ItineraryCapabilities>
    <!-- Define defaults for all properties. -->
    <DefaultValue>
      <MaxAdvancePurchase>210</MaxAdvancePurchase>
      <MaxLengthOfStay>18</MaxLengthOfStay>
    </DefaultValue>
  </ItineraryCapabilities>
</QueryControl>

Example 2

The following example builds on the previous example and defines several <PropertyOverride> blocks that override the defaults:

<?xml version="1.0" encoding="UTF-8"?>
<QueryControl>
  <ItineraryCapabilities>
    <!-- Define defaults for all properties. -->
    <DefaultValue>
      <MaxAdvancePurchase>210</MaxAdvancePurchase>
      <MaxLengthOfStay>18</MaxLengthOfStay>
    </DefaultValue>

    <!-- Define different values for several properties. -->
    <PropertyOverride>
      <MinAdvancePurchase>4</MinAdvancePurchase>
      <MaxAdvancePurchase>320</MaxAdvancePurchase>
      <MinLengthOfStay>7</MinLengthOfStay>
      <MaxLengthOfStay>21</MaxLengthOfStay>
      <Property>12345</Property>
      <Property>67891</Property>
      <Property>060773</Property>
    </PropertyOverride>

    <!-- Define narrower values for a single property. -->
    <PropertyOverride>
      <MaxAdvancePurchase>60</MaxAdvancePurchase>
      <MinLengthOfStay>6</MinLengthOfStay>
      <MaxLengthOfStay>8</MaxLengthOfStay>
      <Property>8675309</Property>
    </PropertyOverride>

  </ItineraryCapabilities>
</QueryControl>

Example 3

The following example builds on the previous examples and prevents several hotels from being repriced by setting a "disabled" state on one of the <PropertyOverride> blocks:

<?xml version="1.0" encoding="UTF-8"?>
<QueryControl>
  <ItineraryCapabilities>
    <!-- Define defaults for all properties. -->
    <DefaultValue>
      <MaxAdvancePurchase>210</MaxAdvancePurchase>
      <MaxLengthOfStay>18</MaxLengthOfStay>
    </DefaultValue>

    <!-- Prevent several properties from being repriced. -->
    <PropertyOverride>
      <State>disabled</State>
      <Property>11235</Property>
      <Property>81321</Property>
      <Property>345589</Property>
    </PropertyOverride>

    <!-- Define different values for several properties. -->
    <PropertyOverride>
      <MinAdvancePurchase>4</MinAdvancePurchase>
      <MaxAdvancePurchase>320</MaxAdvancePurchase>
      <MinLengthOfStay>7</MinLengthOfStay>
      <MaxLengthOfStay>21</MaxLengthOfStay>
      <Property>12345</Property>
      <Property>67891</Property>
      <Property>060773</Property>
    </PropertyOverride>

    <!-- Define narrower values for a single property. -->
    <PropertyOverride>
      <MaxAdvancePurchase>60</MaxAdvancePurchase>
      <MinLengthOfStay>6</MinLengthOfStay>
      <MaxLengthOfStay>8</MaxLengthOfStay>
      <Property>8675309</Property>
    </PropertyOverride>

  </ItineraryCapabilities>
</QueryControl>

<HintControl>

Configures your Hint Response messages. <HintControl> defines whether you can specify multiple hotels for each itinerary or date range in a Hint Response message.

For more information, see Hint Response Messages.

<HintControl> is a child element of <QueryControl>. It uses the syntax shown in <QueryControl>.

The <HintControl> element has no attributes.

The <HintControl> element has the following child elements:

Child Element Required? Type Description
<MultipleItineraries> Required Enum Defines whether you can specify multiple hotels for each itinerary or date range in a Hint Response message. You can specify one of the following values for this element:

  • checkin_range: Lets you specify multiple properties and multiple itineraries for check-in range hints. These are hints in which you set the values of the <FirstDate> and <LastDate> child elements of <Item>.
  • affected_dates: Lets you specify multiple properties for Check-in Date Range or Ranged Itinerary hints. These are hints in which you set the values of the <FirstDate> and <LastDate> child elements of <Item> , OR use the <StaysIncludingRange> element.
  • Omitted (default): If you do not specify a value for the <MultipleItineraries> element, then you can only specify one hotel for each <Item> in a Hint Response message.

For more information, see Hint Response Messages.

<Item> (Deprecated)

Defines repricing settings for the properties within the current block.

NOTE: <Item> is deprecated. Documentation is included here for legacy implementations. Use <PropertyOverride> inside <ItineraryCapabilities> instead.
<Item> is a child element of <QueryControl>. It uses the syntax shown in <QueryControl>.

The <Item> element has no attributes.

The <Item> element has the following child elements:

Child Element Required? Type Description
<MaxAdvancePurchase> Required Integer Same as <MaxAdvancePurchase> in the <DefaultValue> block, except that this value applies to the hotels in this <Item> only.
<MaxLengthOfStay> Required Integer Same as <MaxLengthOfStay> in the <DefaultValue> block, except that this value applies to the hotel in this <Item> only.
<Property> Required String The ID of the hotel that matches the ID you set in your Hotel List Feed.

<ItineraryCapabilities>

Defines default itinerary settings and property-specific overrides.

<ItineraryCapabilities> is a child element of <QueryControl>. It uses the syntax shown in <QueryControl>.

The <ItineraryCapabilities> element has no attributes.

The <ItineraryCapabilities> element has the following child elements:

Child Element Required? Type Description
<DefaultValue> Optional <DefaultValue> Defines itinerary settings for all properties. These settings can be overridden for specified properties with <PropertyOverride> blocks.
<PropertyOverride> Optional <PropertyOverride> Defines repricing settings for the properties within the current <ItineraryCapabilities>.

You can define any number of <PropertyOverride> blocks in <ItineraryCapabilities>.

For example, you can use one <PropertyOverride> to disable repricing of one set of properties, and another block to define properties to reprice with a much wider range of itineraries than your defaults. A third block could define very narrow itineraries.

<DefaultValue>

Defines itinerary settings for all properties. These settings can be overridden for specified properties with <PropertyOverride> blocks.

<DefaultValue> is a child element of <ItineraryCapabilities>. It uses the syntax shown in <QueryControl>.

The <DefaultValue> element has no attributes.

The <DefaultValue> element has the following child elements:

Child Element Required? Type Description
<MinAdvancePurchase>
<MaxAdvancePurchase>
Optional Integer Defines the number of days in advance of check-in for which Google can fetch prices.

<MinAdvancePurchase> is the minimum number of days; <MaxAdvancePurchase> is the maximum number of days.

For example, if <MinAdvancePurchase> is 10 and <MaxAdvancePurchase> is 240, Google can fetch prices for stays that begin between 10 and 240 days from today, inclusive.

The value of <MinAdvancePurchase> only controls fetching, not serving. After fetching stops for an itinerary, it will continue to be served for an amount of time before becoming expired. This time is determined by Google.

The values of these elements are used in conjunction with <MinLengthOfStay> and <MaxLengthOfStay> to determine the size of the price update.

The following settings result in up to 4,320 possible prices for each hotel (240 * 18):

<MinAdvancePurchase>0</MinAdvancePurchase>
<MaxAdvancePurchase>240</MaxAdvancePurchase>
<MinLengthOfStay>1</MinLengthOfStay>
<MaxLengthOfStay>18</MaxLengthOfStay>

The value of <MinAdvancePurchase> must be less than or equal to the value of <MaxAdvancePurchase>, and the values of both must be between 0 and 330, inclusive.

The default value of <MinAdvancePurchase> is 0.

You must explicitly set the value of <MaxAdvancePurchase>. There is no default value.

<MinLengthOfStay>
<MaxLengthOfStay>
Optional Integer Defines the length of stay for which Google can fetch prices.

For example, if <MinLengthOfStay> is 3 and <MaxLengthOfStay> is 21, Google can fetch price data for offers with a length of stay between 3 and 21 days, inclusive.

The values of these elements are used in conjunction with <MinAdvancePurchase> and <MaxAdvancePurchase> to determine the size of the price update.

For Pull with Hints, Google fetches data for 1 to 5 nights of stay, unless you explicitly set the value of <MinLengthOfStay> and/or <MaxLengthOfStay>.

The value of <MinLengthOfStay> must be less than or equal to the value of <MaxLengthOfStay>, and the values of both must be between 1 and 30, inclusive.

The default value of <MinLengthOfStay> is 1.

You must explicitly set the value of <MaxLengthOfStay>. There is no default value.

<State> Optional String Whether to include or exclude all properties from pricing updates. Set to "enabled" to include properties in repricing updates. Set to "disabled" to exclude properties from pricing updates. Disabled properties are not included in Live Queries, hints, or any other pricing update messages.

The default value of <State> is "enabled".

You can override the value of this element for individual properties by using <PropertyOverride>.

<PropertyOverride>

Defines repricing settings for the properties within that block. These repricing settings override the values of <DefaultValue>.

<PropertyOverride> is a child element of <ItineraryCapabilities>. It uses the syntax shown in <QueryControl>.

You can also use <PropertyOverride> to disable repricing of certain properties.

The <PropertyOverride> element has no attributes.

The <PropertyOverride> element has the following child elements:

Child Element Required? Type Description
<MinAdvancePurchase>
<MaxAdvancePurchase>
Optional Integer Same as <MinAdvancePurchase> and <MaxAdvancePurchase> in <DefaultValue>, except that this value applies to the hotels in this <PropertyOverride> only.
<MinLengthOfStay>
<MaxLengthOfStay>
Optional Integer Same as <MinLengthOfStay> and <MaxLengthOfStay> in <DefaultValue>, except that this value applies to the hotels in this <PropertyOverride> only.
<Property> Required String The ID of the hotel that matches the ID you set in your Hotel List Feed.

Each property can appear in a single <PropertyOverride> block only.

<State> Optional String Whether to include or exclude the listed properties from pricing updates.

Set to "enabled" to include the properties in repricing updates. Set to "disabled" to exclude properties from pricing updates. Disabled properties are not included in Live Queries, hints, or any other pricing update messages.

The value of <State> applies to properties specified in <Property> child elements of this <PropertyOverride> only.

The default value is "enabled".