If you received a Feed Status error message, use the following links to find your error message and its solution. | Find your error message |||| |---|---|---|---| | [1001-1050](https://developers.google.com/hotels/hotel-prices/dev-guide/feed-status-errors#1001) | [1051-1100](https://developers.google.com/hotels/hotel-prices/dev-guide/feed-status-errors#1051) | [1101-2000](https://developers.google.com/hotels/hotel-prices/dev-guide/feed-status-errors#1101) | [3001-4000](https://developers.google.com/hotels/hotel-prices/dev-guide/feed-status-errors#3001) | | [6001-7000](https://developers.google.com/hotels/hotel-prices/dev-guide/feed-status-errors#6005) | [7001-8000](https://developers.google.com/hotels/hotel-prices/dev-guide/feed-status-errors#7001) | [8001-8100](https://developers.google.com/hotels/hotel-prices/dev-guide/feed-status-errors#8001) | [8101-8204](https://developers.google.com/hotels/hotel-prices/dev-guide/feed-status-errors#8101) | | [10001-11000](https://developers.google.com/hotels/hotel-prices/dev-guide/feed-status-errors#10001) | [11001-11015](https://developers.google.com/hotels/hotel-prices/dev-guide/feed-status-errors#11001) | | Code | Message | Description | |---|---|---| | 1001 | Can't understand format on timestamp | Replace the timestamp provided with one that follows the [Date/Time format](https://developers.google.com/hotels/hotel-prices/xml-reference/datetime#DateTime). | | 1002 | Can't understand Currency in Tax conversion | Add a valid three-letter [currency code](https://developers.google.com/hotels/hotel-prices/dev-guide/currency-codes), such as EUR or USD. | | 1003 | Can't understand Currency in OtherFees conversion | Add a valid three-letter [currency code](https://developers.google.com/hotels/hotel-prices/dev-guide/currency-codes), such as `EUR` or `USD`. | | 1005 | Invalid Baserate, Tax, or OtherFees | Make sure the values of ``, ``, and `` are valid for those fields. | | 1006 | An all_inclusive rate is specified, but Tax is also provided | `all_inclusive` itinerary shouldn't also include `` and ``. | | 1007 | Result tag is used in the wrong context | The [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#Result) tag can only be placed as an immediate child of [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#Transaction). | | 1008 | RoomID tag is used in the wrong context | Make sure the `` tag is used only with [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#PackageData) or [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#RoomBundle). | | 1009 | PackageID tag is used in the wrong context | Make sure the `` is used only with [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#PackageData) or [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#RoomBundle). | | 1010 | RatePlanID is used in the wrong context | The `` is valid only in a [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#RoomBundle). | | 1011 | Occupancy must be \> 1 in the base rate for a Result | An `` value of 1 is not allowed in the base rate for a ``. Please specify an occupancy \> 1 for the base rate. | | 1012 | Capacity or Occupancy is over the maximum limit | To prevent data errors, both `` and `` are limited to a value of 20 or less. Be sure your `` and `` entries are within that limit. | | 1013 | The text value for Capacity or Occupancy can't be understood as an integer | Change the value to an integer. | | 1014 | Value can't be understood as a Boolean | Replace with one of these accepted values: 0, 1, true, false. | | 1015 | Text entered for a tag that doesn't allow text | Replace the entry with an appropriate non-text element. | | 1016 | Can't understand context for a Text element | A `` element has been used in an inappropriate context, and so has been ignored. Correct this element or move it to the appropriate context. | | 1018 | Value for Refundable days is over the maximum limit | Enter a lower value. Or, if the actual value is greater than the limit, code this room as not refundable. | | 1019 | Value for Refundable days can't be understood | Change the value to an integer. | | 1020 | Value can't be understood as a time | Enter the correct hour and minute in the format HH:MM. | | 1021 | The given attribute value is not valid for its intended element | The given attribute value is not valid for this element. Remove this attribute from the XML element or use a different valid attribute value. | | 1022 | Can't find a match for the given partner and hotel ID | Make sure the hotel ID is in your hotel feed and that the property is matched to a Google Maps feature. | | 1023 | Partner name isn't recognized | This may be due to a Google internal error. Retry the transmission. If that fails, contact Google support. | | 1024 | Can't find a matched Google hotel ID for the given partner and hotel ID | Google does not have a mapping from this given partner and hotel ID to a Google hotel ID. This could be due to delays in processing by Google or if the data can't be matched. Contact Google if you need additional support. | | 1025 | RoomID string is empty | To declare a valid [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#RoomBundle), each [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#RoomData) must have a ``. | | 1026 | PackageID string is empty | To be accessed from a [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#RoomBundle), each [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#PackageData) must have a ``. | | 1027 | Nesting data error: PartnerData, PropertyData, RoomData, and PackageData shouldn't be nested within each other | Check the XML schema and fix nesting errors. | | 1028 | The CheckInDate can't be understood | Enter the ``. in the format YYYY-MM-DD. | | 1029 | The CheckInDate is out of range | Make sure that all ``. values are in the future and not in the past. | | 1030 | LengthOfStay value is over the maximum limit | 30 days is the maximum limit for ``. Edit your data so that the `` is 30 days or less. | | 1031 | Unable to find a matched Google hotel ID for the given partner and hotel ID | Google does not have a mapping from this given partner and hotel ID to a Google hotel ID. This could be due to delays in processing by Google or if Google was unable to match the data. Contact Google support if you need additional support. | | 1033 | Multiple results with the same key: the existing partner hotel ID and the new partner hotel ID | The XML response cannot contain multiple results with the same `` and itinerary. | | 1034 | The XML response can't contain multiple results with the same Property and itinerary | To prevent data errors, [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#RoomBundle) `` values can't be empty, negative, or greater than the maximum nightly price of USD 20,000. [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#RoomBundle) `` values also can't have Can't understand or empty currency. | | 1036 | No RoomBundle Baserate matched the Baserate for the given Result. Room rates weren't stored | Make sure that a [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#RoomBundle) exists for the BaseRate. One or more of these errors has occurred: invalid `` currency, no ``, invalid ``. currency, or invalid ``. currency. | | 1037 | A RoomBundle matched the Baserate for the given Result, but not the Tax. Room rates weren't stored | Make sure that every [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#Result) has a `` with a `` that matches one of the [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#RoomBundle)s. | | 1038 | One or more RoomBundle values matched the Baserate and Tax, but not the OtherFees of the hotel price. Bundles weren't stored | Make sure that every [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#Result) has a `` with `` that matches one of the [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#RoomBundle)s. | | 1039 | Closest RoomBundle did not match the currency of the Result | Make sure the same currency is used for each [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#Result) and its matching [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#RoomBundle). | | 1040 | Closest RoomBundle did not match the Result eligibility | Make sure that every [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#Result) has a ``, including `` and `` as needed. Each `` must match a [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#RoomBundle). | | 1041 | Can't understand Currency given for a hotel ID | Add a valid three-letter [currency code](https://developers.google.com/hotels/hotel-prices/dev-guide/currency-codes), such as EUR or USD. | | 1042 | Can't understand payment type | The text value provided for ChargeCurrency couldn't be understood. | | 1043 | Can't understand string for Tax or OtherFees | Reformat `` or `` as a numerical float value, such as 123 or 12.34. | | 1045 | Unexpected first element | The first element must be [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#Transaction). Correct the file schema. | | 1047 | Missing or incomplete RoomID or PackageID | Invalid `` or ``. Define `` or `` in the metadata before sending prices. | | 1048 | Can't find PointOfSale ID | The ID value for this ``. attribute wasn't found in the set of the defined landing pages. Define an additional ``. or correct the ID in your price feed. | | 1049 | Fetch failed due to an external error | Failed to fetch prices. Check your server logs for more details. | | 1050 | Rate with duplicate RatePlanID | ``. with duplicate `` was not stored. Set unique or empty `` within each [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#Result). | | 1051 | Invalid duplication with key, hotel ID, and new partner hotel ID | Dropped price for hotel due to map overlap. Use manual match to correct the hotels in your feed. | | 1053 | Invalid Rates tag placement | Invalid `` tag placement. The `` tag can only be specified as an immediate child of [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#Result) and [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#RoomBundle). | | 1054 | Invalid Rates tag placement | Invalid `` tag placement. The `` tag can only be specified inside ``. | | 1056 | Rate with duplicate rate_rule_id | ``. with duplicate `rate_rule_id` was not stored. Make sure each ``. occurs only once in any given [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#RoomBundle) or [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#Result). | | 1058 | XML can't be understood | XML can't be understood. Check the XML to make sure it passes `xmllint` or an equivalent validity checker. | | 1061 | Itinerary not requested | Itinerary not requested. Respond only with the itineraries Google requested. | | 1062 | Nights either not specified or not greater than zero | `` must be a number greater than zero. Supply a valid `` value in [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#Result). | | 1063 | Can't find a matching Google hotel ID for partner and partner hotel ID | Google maintains a mapping between Google IDs and partner IDs. In this case, there are multiple partner IDs for a single Google ID. Google chooses one to be primary. Others won't be recorded. After ensuring the two properties are truly unique and not a case of ID drift, contact Google support to separate the IDs. | | 1064 | RoomId in the RoomBundle is not equal to the RoomId found in RoomData | If a `` is provided under both [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#RoomBundle) and an inline [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#RoomData), then the two values must match. | | 1065 | Invalid context for Name, Description or PhotoURL | The elements ``, `` and `` should be placed in a [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#RoomData), not a [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#RoomBundle). To fix, create a contained [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#RoomData) with these elements. If possible, send it independently of each itinerary and refer to it only from the itinerary. | | 1066 | RoomBundle is missing a RatePlanID | Every [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#RoomBundle) must have a `` element. The URL typically needs the ``. If you don't need a ``, insert an empty value, in which case a value will be assigned. | | 1067 | A RoomData or PackageData value is given without a corresponding internal RoomID or PackageID | If the internal [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#RoomData) or [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#PackageData) is missing `` or `` respectively, then Google will first attempt to store with the `` or `` under [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#RoomBundle). Otherwise, Google will generate random IDs. | | 1068 | Property lacks Tax and OtherFees or all_inclusive setting | Properties must either be set to `all_inclusive` or include `` and ``. The value of `` and `` may be 0, but they must be given unless `all_inclusive` is selected. For properties which have known non-zero `` and ``, include those details. When `` and `` are known to be zero, report them as 0 and don't set `all_inclusive`. For properties with unknown `` and ``, set `all_inclusive` instead. | | 1069 | One or more hotel itineraries were missing from the response | Make sure that transactions contain all items requested in the query. | | 1070 | Can't understand a value for RoomUpgradeIncluded, NightlyValue, or OnPropertyCredit | Correct the formatting so that each entry is a currency value that can be understood as a float. | | 1071 | Can't understand the number of miles listed in MilesIncluded | Change the value to an integer. | | 1072 | Occupancy in RoomBundle was too large for RoomID and Capacity | Make sure that the `` in [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#RoomBundle) is not larger than the capacity of the room. For example: if a room has capacity of 1, then `` in [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#RoomBundle) must be set to 1. | | 1073 | No valid RoomBundle is specified, so Rate has been set as unavailable | All [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#RoomBundle) values for this itinerary are invalid and have been rejected. Make sure that every [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#RoomBundle) contains valid data. Specific errors will have been reported separately. | | 1074 | Double-occupancy price can't be listed for single-capacity RoomBundles | The `` listed is for double-occupancy, which can't be specified when all [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#RoomBundle)s submitted for the itinerary are of `` 1. For results where all available bundles are for rooms with `` 1, set `` to -1 (unavailable) or use [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#UnavailableTag) element. | | 1075 | NumAdults is over the maximum limit | To prevent data errors, total `` is limited to a value of 20 or less. Be sure your `` entries are within that limit. | | 1076 | The text value for NumAdults can't be understood as an integer | Change the value for adult `` to an integer, with no decimals or non-numerical features. | | 1077 | Child age is over the maximum limit | To prevent data errors, the maximum allowable `` `age` is 17. Be sure your `` `age` range is within that limit. | | 1078 | The text value for Child age can't be understood as an integer | Change the value to an integer. | | 1079 | The number of guests given in OccupancyDetails is over the maximum limit | To prevent data errors, `` is limited to a value of 20 or less. Be sure your `` entries are within that limit. | | 1080 | Total number of guests given in Occupancy does not match the number in OccupancyDetails | The total number of adults and children specified in `` must match the total number of guests listed in ``. | | 1081 | NumAdults appears more than once | `` must have exactly one `` value as a child element. Any additional occurrences will be ignored. | | 1082 | OccupancyDetails values are provided, but without a value for Occupancy | When `` are provided, they must be preceded by a specific value for ``. | | 1083 | NumAdults is missing in OccupancyDetails | `` must have exactly one `` value as a child element. | | 1084 | The RoomID exceeds the maximum character limit | Make sure all `` values are within the character limit. | | 1085 | Error for partner: PackageID exceeds character limit | Make sure all `` values are within the character limit. | | 1086 | DetailedFee must have a value as well as attributes for currency and type | N/A | | 1087 | DetailedTax is missing required data | ``. must have a value as well as attributes for currency and type. | | 1088 | Can't understand DetailedFee type | The specified fee type couldn't be understood, so the fee type "other" will be used. For best results, use a supported fee type in ``.. | | 1089 | Can't understand DetailedFee source | The specified fee source couldn't be understood, so the fee source "other" will be used. For best results, use a supported fee source in ``.. | | 1090 | Can't understand DetailedTax type | The specified tax type couldn't be understood, so the tax type "other" will be used. For best results, use a supported tax type in ``.. | | 1091 | Invalid usage of Tax / OtherFees and DetailedTax / DetailedFee | Supply either `` / `` or ``. / ``. for prices, but not both. | | 1092 | Can't understand detailed Tax and OtherFees for a partner | One or more of these errors has occurred: invalid `` currency, no ``, invalid ``. currency, or invalid ``. currency. Make sure each currency_code is valid, and that a `` exists for all prices. | | 1093 | Invalid usage of Tax / OtherFees and DetailedTax / DetailedFee | Supply either `` / `` or ``. / ``. for prices, but not both. | | 1094 | Can't understand Currency in converting DetailedTax | Add a valid three-letter [currency code](https://developers.google.com/hotels/hotel-prices/dev-guide/currency-codes), such as EUR or USD. | | 1095 | Can't understand Currency in converting DetailedFee from $0 to $1 | Add a valid three-letter currency, such as EUR or USD. | | 1096 | More than one RoomBundle found with the same hotel ID, RoomID, PackageID, and RatePlanID | Make sure that different [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#RoomBundle)s don't share the same combination of hotel ID, ``, ``, and ``. | | 1097 | RoomBundle must include a child element for Occupancy | `` should indicate the maximum number of guests for which a [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#RoomBundle) is intended. If it isn't set, then the `` value in [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#RoomData) or [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#PackageData) is used instead. | | 1098 | The Baserate for Result should have a positive value unless price is unavailable specified by ``) | Change the value of `` to a positive number or mark it unavailable using [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#UnavailableTag). | | 1099 | Invalid Tax and OtherFees | `` and `` must be non-negative. | | 1100 | Invalid LengthOfStay | ``. must be equal to or greater than 1. | | 1101 | Can't understand currency string | N/A | | 1102 | The combination of Baserate, Tax, OtherFees, LengthOfStay and Occupancy is invalid or exceeds the default Google price per night limit, which is 10,000 USD plus 2,000 USD for each additional guest over 2. If this limit is too low, it can be manually adjusted by your Technical Account Manager | N/A | | 1103 | Tax + OtherFees to Baserate ratio exceeds the Google limit of 10 | The sum of `` and `` should be no greater than 10 times the `` value. | | 1104 | Custom field is too long | The Custom field's value exceeds the maximum character length (200) for `` elements in Transaction messages. You must update the field's value to make it less than 200 characters in length. | | 1105 | Refundable fields may be set incorrectly | `refundable_until_days` and `refundable_until_time` should be empty when `available` is set to false. | | 1106 | refundable_until_time requires refundable_until_days | `refundable_until_days` is required if `refundable_until_time` is set. | | 1107 | refundable_until_days is required | `refundable_until_days` is required if `available` is set to true. | | 1108 | RoomData photo URL is missing its protocol | Add the value in the `PhotoURL` attribute as defined in the `RoomData>` photo URL protocol. | | 1109 | refundable_until_time is strongly recommended | `refundable_until_time` is strongly recommended if `available` is set to true. | | 1110 | RoomBundle must contain RoomID or RoomData but not both | Add a valid `` or `` to this ``. | | 1111 | Baserate for RoomBundle should be a positive value unless price is unavailable | Change the value of `` to a positive number or mark it unavailable using [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#UnavailableTag). | | 1112 | Baserate for Rate should be a positive value unless price is unavailable using `` | Change the value of `` to a positive number or mark it unavailable using [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#UnavailableTag). | | 1113 | Can't recognize query_id in Result element | `query_id` should be included in [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#Result) elements that are returned in response to `Query` with the same ` ID.` | | 1114 | Can't understand "action" in PropertyDataSet | `action` in `` should have values that are `overlay` or `delta`. These values specifies if Google should overlay or merge the room rate mapping definitions. | | 1115 | Custom field name was already used | Custom field names must be unique. | | 1116 | AllowableRoomIDs must contain at least one AllowableRoomID | `AllowableRoomIDs` must not be empty. It must contain at least one `ID`. | | 1117 | AllowablePackageIDs must contain at least one AllowablePackageID | `AllowablePackageIDs` must not be empty. It must contain at least one `ID`. | | 1118 | AllowableRoomIDs or AllowablePackageIDs string is empty | Invalid `AllowableRoomID` or `AllowablePackageID`. | | 1119 | Unknown element | An unknown XML element was found in the response. Correct the error and then validate it against the schema. | | 1120 | An all_inclusive rate is specified, but Tax is also provided | `all_inclusive` itinerary shouldn't include `` and ``. | | 1121 | Timezone in "refundable_until_time" will be ignored. "refundable_until_time" is parsed in the hotel's local timezone | Timezone not allowed in `refundable_until_time`. Enter the correct hour and minute in the format HH:MM. | | 1122 | The text value for MinAge can't be understood as an integer | Change the `` attribute value to an integer. | | 1123 | Value is over the maximum limit for `MinAge ` | `` is over the maximum limit. To prevent data errors, `` is limited to a value of 99 or less. Ensure that your `` entries are within the allowed limit. | | 1124 | OccupancySettings must have at least one valid child element value | The `` is invalid. It must have at least one valid child element value. | | 1125 | Value is over the maximum limit for MinOccupancy | `` is over the maximum limit. To prevent data errors, `` is limited to a value of 99 or less. It is required to keep your `` value within the limit. | | 1126 | The text value for MinOccupancy can't be understood as an integer | The `` should be an integer value. | | 1127 | OccupancySettings is only accepted in RoomData which is inside of the PropertyDataSet element | You can include `` only in `` of the `` element. | | 1128 | Capacity or Occupancy is zero or negative | Value is too small for `` or ``. To prevent data errors, both `` and `` must be positive. | | 1129 | Invalid AirportTransportationIncluded direction | The `` attribute of `` should have either `from`, `to`, or `round_trip`. | | 1130 | The text value for AdultCapacity can't be understood as an integer | The `` value was provided as text. Change the value to an integer | | 1131 | The text value for ChildCapacity can't be understood as an integer | The `` value was provided as text. Change the value to an integer. | | 1132 | Value is over the maximum limit for AdultCapacity | `` limit has exceeded over the maximum limit. To prevent data errors, `` is limited to a value of 99 or less. | | 1134 | Value is too small for AdultCapacity | `` is zero or negative. To prevent data errors, `` and `` must be positive. | | 1135 | Value is too small for ChildCapacity | `` is zero or negative. To prevent data errors, `` and `` must be positive. | | 1136 | Duplicate localizations found for language | Multiple localizations for a single language are not allowed. | | 1137 | Result specifies both price and Unavailable | The result found both price and [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#UnavailableTag). It should specify a positive price or [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#UnavailableTag), but not both. | | 1138 | Value couldn't be understood as an integer | Change the value to an integer. | | 1139 | Value couldn't be understood as a date | Change the value to a date in `YYYY-MM-DD` format. | | 1140 | `` specified for mergeable Result | Mergeable [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#Result)s should only be used for sending available rates. Set the `` attribute to `false`. | | 1141 | The rate was not available, but did not contain an `` element | Unavailable rates were mentioned without using [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#UnavailableTag) element. Specify unavailable rates by including [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#UnavailableTag) element in the message. | | 1142 | Internal error during fetch | An internal error occurred during send request and fetch will be retried. No action needed. | | 1143 | Error during fetch | Google tried to reach your server but it returned an error. The fetch will be retried. Check your server logs for more details. | | 1144 | Invalid JapaneseHotelRoomStyle | Invalid value for ``. The value must be either `western`, `japanese`, or `japanese_western`. | | 1145 | Missing "included" attribute in "Breakfast" or "Dinner" | The "included" attribute is required in `` and ``. | | 1146 | Some attributes in "Breakfast" or "Dinner" are ignored | The values in `` and ` ` such as `in_room`, `in_private_space` and `buffet` are ignored unless the `included` attribute is set as `true` | | 1147 | Invalid Bed size | Invalid value for the `` attribute of ``. The value must be either `single`, `semi_double`, `double`, `queen`, or `king`. | | 1148 | Width or Length outside Bed | `` and `` must not appear outside `.` | | 1149 | Invalid Width or Length | `` and `` must have `unit="cm"` and a positive integer number. | | 1150 | Timezone not allowed in CheckinTime and CheckoutTime | Timezone in `` and `` will be ignored. `` and `` are parsed in the hotel's local timezone. | | 1151 | Value can't be understood as a time | Enter the correct hour and minute in the format `HH:MM`. | | 1152 | BathAndToilet relation requires both Bath and Toilet | `` in `` is ignored unless both `` and `` exist. | | 1153 | Invalid BathAndToilet relation | The `` attribute of `` must be `together` or `separate`. | | 1154 | Invalid Roomsharing | Invalid value for ``. The value must be one of `shared` or `private`. | | 1155 | Invalid Smoking | Invalid value for ``. The value must be either `non_smoking` or `smoking`. | | 1156 | Provide both Breakfast and Dinner | It is highly recommended to provide both `` and ``. Otherwise, your package may not be shown to users looking for packages with specific meal conditions. | | 1157 | Account is not enabled for RoomBundle or metadata | Account is not enabled for `` or metadata. Please contact support to have your account enabled for room bundles. | | 1158 | Account is not enabled for non-default occupancy | Account is not enabled for non-default occupancy, but non-default occupancy prices were received. Please contact support to have your account enabled for occupancy rates. | | 1159 | Account is not enabled for child occupancy | Account is not enabled for child occupancy, but child occupancy prices were received. Please contact support to have your account enabled for child occupancy. | | 1160 | Rate rule ID cannot be empty | Rate rule ID cannot be empty, Please use a non-empty rate rule ID. | | 3001 | Unexpected element | The root element must be `` for a changed price response. This problem may be caused by responding with a different message type or incorrect path. Correct either the file schema or path as appropriate. | | 3002 | FirstDate can't be understood | The `` text can't be understood as a date. Enter the date in the form `YYYY-MM-DD`. | | 3003 | LastDate can't be understood | The `` text can't be understood as a date. Enter the date in the form `YYYY-MM-DD`. | | 3004 | Checkin date can't be understood | The `` date text can't be understood as a date. Enter the date in the form `YYYY-MM-DD`. | | 3005 | LengthOfStay can't be understood | The ``. text can't be understood as a date. Enter the date in the form `YYYY-MM-DD`. | | 3006 | Required elements are missing or invalid: Checkin date and/or LengthOfStay | Either a valid `` date or `` is missing. Add the elements noted in the alert. | | 3007 | Item with StaysIncludingRange is missing a FirstDate | N/A | | 3008 | The FirstDate and LastDate are missing or invalid | Add the appropriate `` and `` to the ``. | | 3009 | LengthOfStay is over the maximum limit | To prevent data errors, `` is limited to a maximum of 30 days. | | 3010 | Checkin date is in the past | All check-in dates must be in the future. | | 3012 | FirstDate is after LastDate | `` must be after the ``. | | 3013 | FirstDate is too far in the future | Make sure the check-in date for each itinerary is no more than 330 days in the future. | | 3014 | LastDate is too far in the future | `` can be no more than 330 days in advance. Adjust your values so that the `` is within that limit. | | 3015 | Error in POST | This error happened as partner data was being pulled. Check your logs and make sure that the Google IP address is in the allowlist. | | 3016 | Can't find a matching Google ID for hotel ID | Google has no mapping from this partner hotel ID to a Google hotel ID. This could be due to delays in processing, or Google is unable to match the partner ID. Contact Google support if you need further help. | | 3017 | The LastDate given is in the past | `` values can't include ranges with dates in the past. | | 3018 | Item with Stay is missing valid hotel ID values | N/A | | 3019 | Item with StaysIncludingRange is missing a valid hotel ID | Make sure all IDs are valid and match those in the hotel feed. | | 3020 | Item with Stay is missing valid hotel ID values, and has been skipped | Make sure that every `` contains at least one hotel ID. | | 3021 | XML can't be understood | Make sure XML can pass xmllint or an equivalent validity checker, including the schema. | | 3022 | Error occurred while issuing HintRequest | Check if the configured endpoint is reachable. | | 3023 | Internal error processing "hint" response, will retry | Internal error occurred when processing ``. Contact Google support if these errors persist. | | 6005 | Upload path not recognized | The upload path did not match any of the accepted paths. To correct the upload path, see documentation on the developer site. | | 6006 | Message from an IP that is unknown or not allowed | A message came in from an unknown IP. Make sure the `partner` attribute for this message is correct and that it was uploaded from one the known IPs shared with Google. | | 6007 | Can't extract OTA information from the OTA message | The OTA message was not in the expected OTA XML format. Make sure the file passes xmllint or an equivalent validity checker. | | 6008 | No Partner tag in file | The uploaded file did not contain a `partner` attribute, and the partner can't be deduced from the IP address. Add the `partner` attribute and check your sending IP address. | | 6009 | `partner` not recognized | The name provided in the Partner attribute is not a known partner. Confirm the spelling, or contact Google support to check your exact partner name. | | 6013 | Uploaded XML failed to parse | The file failed parsing by a generic XML parser. Reformat the file and make sure it passes xmllint or an equivalent XML validity checker. | | 6014 | No Partner tag in file, and more than one Partner with the same IP | The file lacks a `partner` attribute. Multiple partners are listed at the same IP, so Google can't infer the partner from the IP address. Add a `partner` tag to the file. | | 6015 | Transaction push not authorized for a partner | A [``](https://developers.google.com/hotels/hotel-prices/xml-reference/transaction-messages#Transaction) file was pushed for a partner that is configured for pull or hint modes. Contact Google support to change your transmission mode. | | 6018 | Partner not active | The file wasn't processed because the partner is not active. Contact Google support to activate your feed. | | 6019 | Account not configured properly | Ask Google to verify your partner configuration. | | 6020 | Not authorized to upload feed for `subaccount_id` | Partner is uploading from an IP address that is not authorized to upload for the partner name in the uploaded file. Verify the partner names in the upload file or upload from a different IP address, then retry. | | 6021 | Account not configured properly | Ask Google to verify your partner configuration. | | 6023 | Rejected request from a prohibited country or region | The IP of this request is from a prohibited country or region. Retry the transmission from an allowed country or region. | | 6024 | Rejected request for gaia_id for the given subaccount_id | A GAIA authorization of subaccount uploads is not yet active. Retry without the GAIA login, or use a non-subaccount upload request. | | 6025 | Rejected request for the given IP and subaccount_id | No partner was found for the requested `subaccount_id`. Without GAIA, IP is not valid for the partner. Check and verify the `subaccount_id` in the request. | | 6026 | Rejected request for the given IP, subaccount_id, and partner | The IP is not in the allowlist for this partner. Without GAIA, IP is not valid for the partner. Retry from a valid location or contact Google support to update your partner configuration. | | 6027 | No partner attribute in file. Partner was inferred from the IP address | A `partner` attribute was not included in the file, but we have inferred the partner from the IP address. Add a `partner` attribute and retry. | | 6030 | Problem uploading message. Try resending | Problem uploading message. Try resending. If the problem persists, [contact Google support](https://support.google.com/hotelprices/gethelp). | | 6031 | ARI push not authorized for this account | Contact your Technical Account Manager (TAM) to verify your account configuration. | | 6032 | File upload rate exceeds limit | Accounts are limited to a 400 file per second upload rate. Either reduce the number of files uploaded per request or reduce the number of simultaneous requests. | | 6033 | Failed to parse "account ID" from upload path | Either the upload path or account ID is incorrect. | | 6034 | Invalid "OAuth 2.0" credentials | Google has failed to upload due to invalid `OAuth 2.0` credentials. | | 6035 | Invalid "OAuth 2.0" credentials, fallback to IP | Invalid `OAuth 2.0` credentials. OAuth is continuing to check the Google `IP` address in the `allowlist`. | | 6037 | Service account doesn't have write permission | Failed to upload because the service account associated with the `OAuth 2.0` credential has insufficient write permissions. | | 6038 | Failed to authorize; falling back to IP | Service account associated with the `OAuth 2.0` credential has insufficient write permissions and it is continuing to check the IP addresses in the `allowlist`. | | 7001 | Error from POST | Check your logs and make sure the Google IP address is in the allowlist. Work with Google support to verify the OTA connection settings. | | 7002 | Error getting partner configuration | An error occurred while getting the partner configuration. Contact Google support and ask them to confirm that the partner configuration exists for you. | | 7004 | Error parsing XML message | The XML message is malformed and so can't be understood. Make sure the file passes xmllint or an equivalent validity checker. For more information, see [Schemas](https://developers.google.com/hotels/hotel-prices/dev-guide/schemas). | | 7005 | Can't determine a hotel ID for the given RoomStay | The `` element did not have a `property_ID` set. Also, no global property was defined in the message. Check the `property_ID`. | | 7006 | Item with StaysIncludingRange missing valid hotel ID values | The Google hotels manifest has no corresponding record for the hotel ID provided by the partner. Confirm that the hotel has been clustered. | | 7007 | A RoomRate element has multiple currencies in its Rate elements | One of the RoomRate elements in the XML message includes elements with different currencies. These elements are being ignored. Change your XML so that all related elements use a single currency. | | 7008 | Can't understand Tax and OtherFees string | The price before `` from this XML message can't be understood. Check the string shown and fix the price. | | 7009 | Can't understand price after Tax | Google can't understand the price after `` from this XML message. Check the string shown and fix the price. | | 7010 | Can't understand Tax | Can't understand `` from this XML message. Check the string shown and fix the price. | | 7011 | Can't understand date range for rate | The dates given for this element can't be understood. The `` and `` dates are shown as they appear in the XML (and may be empty). Fix the dates and retry. | | 7012 | Unsupported time unit | `` and `` are the only time units supported for elements. `` means the rate applies per day, while `` means the rate applies for the entire given date range. Change the time unit. | | 7013 | Base price can't be understood for hotel ID | The base price in the OTA XML message can't be understood. The message may be wrong, or the code needs to be updated to support a new format. | | 7014 | Price with Tax or OtherFees can't be understood for hotel ID | The total price (`` + taxes/fees) in the OTA XML message can't be understood. The message may be wrong, or the code needs to be updated to support a new format. | | 7015 | No price could be understood for hotel ID | A price couldn't be understood in the OTA XML message. The message may be wrong, or the code needs to be updated to support a new format. | | 7016 | No Currency found for hotel ID | Your OTA XML messages don't include a currency, and the partner configuration specifies no default currency. Contact Google support and ask them to fix the partner config or make sure you are sending currency info. | | 7017 | Can't understand Tax | The nightly breakdown given in `TPA_extensions` doesn't match the amounts given in other elements. As a result, the amount from the other elements was used. Adjust the `TPA_Elements` breakdown. | | 7018 | Can't understand OtherFees | The `` from this XML message can't be understood. Adjust the `` and try again. | | 7019 | XML warning | N/A | | 7020 | XML error | N/A | | 7021 | XML request didn't succeed | No success element was returned. In similar cases, 7020 errors will also often appear. | | 8001 | Configuration error | The partner configuration isn't correct. Contact Google support to fix the partner configuration. | | 8002 | Error reading file | An error occurred while reading the file. If you see this message often, contact Google support. | | 8005 | OTA message unsupported | The OTA message is valid, but we don't know how to parse this particular one. Only `OTA_HotelAvailNotifRQ` and `OTA_HotelRateAmountNotifRQ` can be understood. Make sure you're using one of the supported message types. | | 8007 | Can't understand RestrictionStatus for AvailStatusMessage | Google can't process the `AvailStatusMessage` with the given index. We don't recognize the value of the ``, which is shown in the error message. | | 8008 | Can't understand restriction for AvailStatusMessage | Google can't process the `AvailStatusMessage` with the given index. We don't recognize the value of the ``, which is shown in the error message. | | 8015 | Can't find AmountBeforeTax in RateAmountMessage / BaseByGuestAmt | An `AmountBeforeTax` attribute needs to be added to the XML element shown. | | 8016 | Can't find a CurrencyCode for RateAmountMessage and BaseByGuestAmt | Google can't find a currency for the given XML element in the `RateAmountMessage`. Also, no default currency is set. | | 8020 | Can't understand the basis attribute for the given tax/fee | The total price (`` + tax/fee) in the OTA XML message can't be understood. The message may be wrong, or the code needs to be updated to support a new format. | | 8021 | Can't understand the given period attribute | The period attribute for the given tax/fee can't be understood. Make sure to send the correct tax/fee XML message. | | 8022 | Can't understand a currency (or get one from config) | Google can't set a currency for the given tax/fee element, either by parsing the XML or from the partner config. Make sure to send the correct tax/fee XML message. | | 8023 | Can't understand the given Type element value | Google can't understand the type attribute for the given tax/fee. Make sure to send the correct tax/fee XML message. | | 8024 | Can't understand value for AvailStatusMessage | For `AvailStatusMessage`, Google expected to receive one `` and one ` ` | | 8027 | Duplicate BaseByGuestAmt occupancy | Two or more `` specified the same number of occupants. | | 8028 | BaseByGuestAmt occupancy over limit | The number of occupants specified in `:` should be limited to a value 99 or less. | | 8029 | Couldn't obtain rate plan code from RatePlan element | The rate plan code is unavailable in the `` element. Set the `` attribute in the `` element. | | 8030 | Couldn't find notification type at `` element | Set the `` attribute in the `` element. | | 8031 | Unsupported rate plan notification type at RatePlan | Set the `` to a supported string. | | 8032 | Failed to find start or end date at RatePlan element for rate deletion | Set the `` and `` attributes in the `` element. | | 8033 | Failed to parse start or end date at RatePlan or Rate element | Set the `` and `` attributes in the `` element or `` element to valid dates. | | 8034 | Failed to find InvTypeCode at Rate element | Set the `` attribute in the `` element. | | 8036 | Failed to parse RateTier at Rate element | Set the `` attribute in the `` element to a valid value. | | 8037 | Failed to parse Count, CountType from InvCount element | `` must have a `` and `` attribute. | | 8039 | Expected exactly one StatusApplicationControl | Only one `` element must be specified in the given context. | | 8040 | Failed to find start or end date at RatePlan or Rate element | Set the `` and `` attributes in the `` or `` element. | | 8041 | Missing Start or End date elements in StatusApplicationControl | Set the `` and `` attributes in the `` element. | | 8042 | Couldn't interpret Start or End date elements in StatusApplicationControl | Set the `` and `` attributes in the `` element to valid `YYYY-MM-DD` dates. | | 8043 | Couldn't find inventory code on StatusApplicationControl in Inventory | Ensure that the expected attribute `` is set in ``. | | 8044 | Couldn't extract incoming message from SOAP envelope | Make sure the partner SOAP configuration is correct and that the XML is structured as required. | | 8045 | Invalid device type | The device type isn't valid. | | 8047 | Invalid country code | The country code given is invalid. Enter a valid [country code](https://developers.google.com/hotels/hotel-prices/dev-guide/country-codes) such as `GB` or `US`. | | 8048 | Invalid identifier | Invalid identifier that cannot be parsed. | | 8049 | Promotion deletion not allowed within overlay | The promotion deletion is invalid. Promotions can't be deleted within an overlay. | | 8050 | Invalid action | There is an invalid action string that can't be parsed. | | 8051 | Invalid element | Elements can't be included within a promotion that has been deleted. | | 8052 | Invalid date | Can't understand this string as a date. Invalid date that can't be parsed. | | 8053 | Invalid date range | Date range with invalid start and end. The value for `` must be earlier than, or equal to, the value for ``. | | 8055 | Invalid numeric value,Numeric value that is not within allowed limits | The values given are invalid. It must be within the allowed limits. | | 8056 | Invalid integer range | The range given is invalid. The value for `min` must be less than or equal to the value for `max`. | | 8057 | Invalid percentage | Invalid percentage that can't be parsed. This percentage value isn't allowed. Percentage values must be between 0 and 100. | | 8058 | Invalid timestamp | Invalid timestamp that cannot be parsed. The string provided can't be understood as a timestamp. Timestamps must be in `RFC3339` format. | | 8059 | Invalid MinMaxMessageType for LengthOfStay | Specify ``, ``, ``, ``, or `` as the `` element. | | 8060 | Missing attribute Time on LengthOfStay element | Set the `