If you received a Feed Status error message, use the links below to find your
error message and its solution.
| Code |
Message |
Description |
| 1001 |
Can't understand format on timestamp |
Replace the timestamp provided with one that follows the
Date/Time format. |
| 1002 |
Can't understand Currency in Tax conversion |
Add a valid three-letter currency code, such as EUR or USD. |
| 1003 |
Can't understand Currency in OtherFees conversion |
Add a valid three-letter currency code, such as EUR or USD. |
| 1005 |
Invalid Baserate, Tax, or OtherFees |
Make sure the values of <Baserate>, <Tax>, and <OtherFees> are valid for those fields. |
| 1006 |
An all_inclusive rate is specified, but Tax is also provided |
all_inclusive itinerary should not also include <Tax> and <OtherFees>. |
| 1007 |
Result tag is used in the wrong context |
The <Result> tag can only be placed as an immediate child of <Transaction>. |
| 1008 |
RoomID tag is used in the wrong context |
Make sure the <RoomID> tag is used only with <PackageData> or <RoomBundle>. |
| 1009 |
PackageID tag is used in the wrong context |
Make sure the <PackageID> is used only with <PackageData> or <RoomBundle>. |
| 1010 |
RatePlanID is used in the wrong context |
The <RatePlanID> is valid only in a <RoomBundle>. |
| 1011 |
Capacity or Occupancy is used in the wrong context |
<Occupancy> can be used only with <RoomBundle>,
<RoomData>, <PackageData>, <Result>, and <Rates>.
<Capacity> can be used only with <RoomData>. |
| 1012 |
Capacity or Occupancy is over the maximum limit |
To prevent data errors, both <Capacity> and <Occupancy> are limited to a value of 20 or less. Be sure your <Capacity> and <Occupancy> 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 <Text> element has been used in an inappropriate context, and so has been ignored. Correct this element or move it to the appropriate context. |
| 1017 |
Can't understand context for Refundable element |
The <Refundable> element can't be used directly in <Result>. Use the <Refundable> element only in <RoomBundle>, <RoomData>, and/or <PackageData>. |
| 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 we were unable to match the data. Contact Google if you need additional
support. |
| 1025 |
RoomID string is empty |
To declare a valid <RoomBundle>, each <RoomData> must have a <RoomID>. |
| 1026 |
PackageID string is empty |
To be accessed from a <RoomBundle>, each <PackageData> must have a <PackageID>. |
| 1027 |
Nesting data error: PartnerData, PropertyData, RoomData, and PackageData should not be nested within each other |
Check the XML schema and fix nesting errors. |
| 1028 |
The CheckInDate can't be understood |
Enter the <CheckInDate>. in the format YYYY-MM-DD. |
| 1029 |
The CheckInDate is out of range |
Make sure that all <CheckInDate>. 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 <LengthOfStay>. Edit your data so that the <LengthOfStay> 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 we were 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 <Property> and itinerary. |
| 1034 |
The XML response can't contain multiple results with the same Property and itinerary |
To prevent data errors, <RoomBundle> <Baserate> values can't be empty, negative, or greater than the maximum nightly price of USD 20,000. <RoomBundle> <Baserate> 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 <RoomBundle> exists for the BaseRate. One or more of these errors has occurred: invalid <Baserate> currency, no <Baserate>, invalid <DetailedTax>. currency, or invalid <DetailedFee>. currency. |
| 1037 |
A RoomBundle matched the Baserate for the given Result, but not the Tax. Room rates weren't stored |
Make sure that every <Result> has a <Baserate> with a <Tax> that matches one of the <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 <Result> has a <Baserate> with <OtherFees> that matches one of the <RoomBundle>s. |
| 1039 |
Closest RoomBundle did not match the currency of the Result |
Make sure the same currency is used for each <Result> and its matching <RoomBundle>. |
| 1040 |
Closest RoomBundle did not match the Result eligibility |
Make sure that every <Result> has a <Baserate>, including <Tax> and <OtherFees> as needed. Each <Baserate> must match a <RoomBundle>. |
| 1041 |
Can't understand Currency given for a hotel ID |
Add a valid three-letter currency code, 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 <Tax> or <OtherFees> as
a numerical float value, such as 123 or 12.34. |
| 1045 |
Unexpected first element |
The first element must be <Transaction>. Correct the file schema. |
| 1047 |
Missing or incomplete RoomID or PackageID |
Invalid <RoomID> or <PackageID>. Define <RoomID> or <PackageID> in the metadata before sending prices. |
| 1048 |
Can't find PointOfSale ID |
The ID value for this <PointOfSale>. attribute wasn't found in the set of the defined landing pages. Define an additional <PointOfSale>. 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 |
<Rate>. with duplicate <RatePlanID> was not stored. Set unique or empty <RatePlanID> within each <Result>. |
| Code |
Message |
Description |
| 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 <Rates> tag placement. The <Rates> tag can only be specified as an immediate child of <Result> and <RoomBundle>. |
| 1054 |
Invalid Rates tag placement |
Invalid <Rate> tag placement. The <Rate> tag can only be specified inside <Rates>. |
| 1056 |
Rate with duplicate rate_rule_id |
<Rate>. with duplicate rate_rule_id was not stored. Make sure each <Rate>. occurs only once in any given <RoomBundle> or <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 |
<Nights> must be a number greater than zero. Supply a valid <Nights> value in <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 will not 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 <RoomID> is provided under both <RoomBundle> and an inline <RoomData>, then the two values must match. |
| 1065 |
Invalid context for Name, Description or PhotoURL |
The elements <Name>, <Description> and <PhotoURL> should be placed in a <RoomData>, not a <RoomBundle>. To fix, create a contained <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 <RoomBundle> must have a <RatePlanID> element. The URL typically needs the <RatePlanID>. If you don't need a <RatePlanID>, 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 <RoomData> or <PackageData> is missing <RoomID> or <PackageID> respectively, then Google will first attempt to store with the <RoomID> or <PackageID> under <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 <Tax> and <OtherFees>. The value of <Tax> and <OtherFees> may be 0, but they must be given unless all_inclusive is selected. For properties which have known non-zero <Tax> and <OtherFees>, include those details. When <Tax> and <OtherFees> are known to be zero, report them as 0 and do not set all_inclusive. For properties with unknown <Tax> and <OtherFees>, 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 <Occupancy> in <RoomBundle> is not larger than the capacity of the room. For instance: if a room has capacity of 1, then <Occupancy> in <RoomBundle> must be set to 1. |
| 1073 |
No valid RoomBundle is specified, so Rate has been set as unavailable |
All <RoomBundle> values for this itinerary are invalid and have been rejected. Make sure that every <RoomBundle> contains valid data. Specific errors will have been reported separately. |
| 1074 |
Double-occupancy price can't be listed for single-capacity RoomBundles |
The <Baserate> listed is for double-occupancy, which can't be specified when all <RoomBundle>s submitted for the itinerary are of <Capacity> 1. For results where all available bundles are for rooms with <Capacity> 1, set <Baserate> to -1 (unavailable). |
| 1075 |
NumAdults is over the maximum limit |
To prevent data errors, total <Occupancy> is limited to a value of 20 or less. Be sure your <Occupancy> entries are within that limit. |
| 1076 |
The text value for NumAdults can't be understood as an integer |
Change the value for adult <Occupancy> 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 <Child> age is 17. Be sure your <Child> 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, <Occupancy> is limited to a value of 20 or less. Be sure your <Occupancy> 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 <OccupancyDetails> must match the total number of guests listed in <Occupancy>. |
| 1081 |
NumAdults appears more than once |
<OccupancyDetails> must have exactly one <NumAdults> value as a child element. Any additional occurrences will be ignored. |
| 1082 |
OccupancyDetails values are provided, but without a value for Occupancy |
When <OccupancyDetails> are provided, they must be preceded by a specific value for <Occupancy>. |
| 1083 |
NumAdults is missing in OccupancyDetails |
<OccupancyDetails> must have exactly one <NumAdults> value as a child element. |
| 1084 |
The RoomID exceeds the maximum character limit |
Make sure all <RoomID> values are within the character limit. |
| 1085 |
Error for partner: PackageID exceeds character limit |
Make sure all <PackageID> 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 |
<DetailedTax>. 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 <DetailedFee>.. |
| 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 <DetailedFee>.. |
| 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 <DetailedFee>.. |
| 1091 |
Invalid usage of Tax / OtherFees and DetailedTax / DetailedFee |
Supply either <Tax> / <OtherFees> or <DetailedTax>. / <DetailedFee>. 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 <Baserate> currency, no <Baserate>, invalid <DetailedTax>. currency, or invalid <DetailedFee>. currency. Make sure each currency_code is valid, and that a <Baserate> exists for all prices. |
| 1093 |
Invalid usage of Tax / OtherFees and DetailedTax / DetailedFee |
Supply either <Tax> / <OtherFees> or <DetailedTax>. / <DetailedFee>. for prices, but not both. |
| 1094 |
Can't understand Currency in converting DetailedTax |
Add a valid three-letter currency code, 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 <RoomBundle>s do not share the same combination of hotel ID, <RoomID>, <PackageID>, and <RatePlanID>. |
| 1097 |
RoomBundle must include a child element for Occupancy |
<Occupancy> should indicate the maximum number of guests for which a <RoomBundle> is intended. If it isn't set, then the <Occupancy> value in <RoomData> or <PackageData> is used instead. |
| 1098 |
The Baserate for Result should have a positive value unless price is unavailable (-1) |
Change the value of <Baserate> to a positive
number or mark it unavailable (-1). |
| 1099 |
Invalid Tax and OtherFees |
<Tax> and <OtherFees> must be non-negative. |
| 1100 |
Invalid LengthOfStay |
<LengthOfStay>. must be equal to or greater than 1. |
| Code |
Message |
Description |
| 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 <Tax> and <OtherFees> should be no greater than 10 times the <Baserate> value. |
| 1104 |
Custom field is too long |
The Custom field's value exceeds the maximum character length (200) for
<Custom[1-5]> 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. |
| 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 <RoomID> or <RoomData>
to this <RoomBundle>. |
| 1111 |
Baserate for RoomBundle should be a positive value unless price is
unavailable (-1) |
Change the value of <Baserate> to a positive number
or mark it unavailable (-1). |
| 1112 |
Baserate for Rate should be a positive value unless price is
unavailable (-1) |
Change the value of <Baserate> to a positive number
or mark it unavailable (-1). |
| 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 should not also include <Tax> and <OtherFees>. |
| 1128 |
Capacity or Occupancy is zero or negative |
Value is too small for <Capacity> or <Occupancy>.
To prevent data errors, both <Capacity> and <Occupancy>
must be positive. |
| 1141 |
The rate was not available, but did not contain an Unavailable
element |
Unavailable rates were mentioned without using Unavaliable
element. Specify unavailable rates by including Unavailable
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. |
| Code |
Message |
Description |
| 3001 |
Unexpected element |
The root element must be <Hint> 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 <FirstDate> text can't be understood as a date. Enter the date in the form YYYY-MM-DD. |
| 3003 |
LastDate can't be understood |
The <LastDate> 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 <Checkin> 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 <LengthOfStay>. 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 <Checkin> date or <LengthOfStay>. 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 <FirstDate> and <LastDate> to the <Item>. |
| 3009 |
LengthOfStay is over the maximum limit |
To prevent data errors, <LengthOfStay>. 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 |
<LastDate> must be after the <FirstDate>. |
| 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 |
<LastDate> can be no more than 330 days in advance. Adjust your values so that the <LastDate> 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 correctly whitelisted. |
| 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 by Google, or we may be unable to match the partner ID. Contact Google support if you need further help. |
| 3017 |
The LastDate given is in the past |
<Hint> 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 <Item> 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 from POST |
Error occurred while pulling data. Check your logs and make sure the Google IP address is correctly whitelisted. |
| Code |
Message |
Description |
| 4001 |
Partner is not enabled for room metadata |
This account hasn't been enabled for hotel room metadata, which must be enabled separately from standard prices. (Note that storing can be enabled without serving.) Contact Google support to activate room metadata. |
| 4002 |
Timestamp can't be understood as a date |
The timestamp attribute doesn't conform to the required Google format. Fractional seconds should not be included. |
| 4003 |
Unexpected first element |
The expected element was <HotelInfoFeed>. The XML root element was incorrect for a changed price response. Correct either the first element or the path as appropriate. |
| 4004 |
Occupancy or Capacity is over the allowable limit |
The value of the <Occupancy> or <Capacity> will not be used because it is above the available limit. This limit was chosen to avoid unlikely error values. If the value isn't accurate, correct it. If the actual value is above the limit, either remove the value or set it at the limit. If removing, make sure the description text provides the information. |
| 4005 |
Value for Occupancy or Capacity can't be understood as a number |
Replace the value provided, which can't be understood. |
| 4006 |
Value found in Roomdata can't be understood as a Boolean |
Check these elements: The available attribute value under <Refundable> element; the <BreakfastIncluded> element; the <InternetIncluded> element; the <ParkingIncluded> element. Replace the bad value with one of these accepted Boolean values: 0, 1, true, false. |
| 4007 |
Value given is over the maximum limit for Refundable days |
Enter a lower value. Or, if the actual value is greater than the limit, code this room as not refundable. |
| 4008 |
Value given can't be understood as a number for Refundable days |
Change the value to an integer. |
| 4009 |
Timestamp can't be understood as a time |
The timestamp attribute doesn't conform to the required Google format. Fractional seconds should not be included. Enter the correct hour and minute in the format HH:MM. |
| 4010 |
No matching Google hotel ID exists for the given partner and Property |
Data can't be stored because Google has no mapping from this partner ID to a Google ID. This could be due to delays in manifest processing, or to another failure in mapping. Make sure that all information needed for matching is provided in the hotel feed. See documentation on the hotel feed. |
| 4011 |
Can't understand given value as a Baserate number |
<Baserate> values must be parseable as a number. |
| 4012 |
Can't understand Boolean value for all_inclusive |
The value provided must be understandable as a Boolean. |
| 4013 |
Can't understand currency |
The currency given is not one Google recognizes. Replace with a valid currency. |
| 4014 |
Can't understand Tax and OtherFees string |
Replace the value provided with one that fits the format for <Tax> and <OtherFees>. |
| 4015 |
Invalid payment type |
Enter one of the accepted values: web, hotel, or deposit. |
| 4017 |
Can't find Google hotel ID for the given partner hotel ID |
The partner ID isn't mapped to a Google ID. This could be due to delays in manifest processing, or to some other reason. See documentation on the hotel feed, and make sure all the information needed for matching is provided. |
| 4018 |
Empty RoomID string in RoomData |
Each <RoomData> must have a <RoomID> in order to be accessed from a <RoomBundle>. Add a valid <RoomID> for this <RoomData>. |
| 4020 |
XML can't be understood in the HotelInfo feed |
Make sure XML in the in the <HotelInfo> feed can pass xmllint or an equivalent validity checker, including the schema. |
| Code |
Message |
Description |
| 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 of 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 we 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 <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. |
| 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 whitelisted 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 us. |
| 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. |
| Code |
Message |
Description |
| 7001 |
Error from POST |
Check your logs and make sure the Google IP address is correctly whitelisted. 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. |
| 7005 |
Can't determine a hotel ID for the given RoomStay |
The <RoomStay> 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 <Tax> from this XML message can't be
understood. Check the string shown and fix the price. |
| 7009 |
Can't understand price after Tax |
We can't understand the price after <Tax> from this
XML message. Check the string shown and fix the price. |
| 7010 |
Can't understand Tax |
Can't understand <Tax> 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
<Effective> and <Expire> dates are
shown as they appear in the XML (and may be empty). Fix the dates and
retry. |
| 7012 |
Unsupported time unit |
<Day> and <FullDuration> are the
only time units supported for elements. <Day> means the
rate applies per day, while <FullDuration> 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 (<Baserate> + 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 <OtherFees> from this XML message can't be
understood. Adjust the <OtherFees> 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. |
| Code |
Message |
Description |
| 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. |
| 8003 |
Error understanding XML |
Check the contents of the associated file to make sure it adheres to the approved schema. |
| 8004 |
Error understanding XML message |
The XML was parseable, but the message is not one we know how to understand. Confirm that the XML has correct formatting. |
| 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. |
| 8006 |
Can't find RestrictionStatus for AvailStatusMessage |
The AvailStatusMessage couldn't be understood with the given index, as no <RestrictionStatus> was present. |
| 8007 |
Can't understand RestrictionStatus for AvailStatusMessage |
We can't process the AvailStatusMessage with the given index. We don't recognize the value of the <RestrictionStatus>, which is shown in the error message. |
| 8008 |
Can't understand restriction for AvailStatusMessage |
We can't process the AvailStatusMessage with the given index. We don't recognize the value of the <RestrictionStatus>, which is shown in the error message. |
| 8009 |
Can't understand min LOS for AvailStatusMessage |
We can't understand the minimum LOS for the AvailStatusMessage with the given index. |
| 8010 |
Can't understand max LOS for AvailStatusMessage |
We can't understand the minimum LOS for the AvailStatusMessage with the given index. |
| 8011 |
Can't understand min LOS for AvailStatusMessage |
We can't understand the minimum LOS for the AvailStatusMessage with the given index. |
| 8012 |
Can't understand max LOS for AvailStatusMessage |
We can't understand the minimum LOS for the AvailStatusMessage with the given index. |
| 8013 |
Min LOS is greater than the Max LOS for AvailStatusMessage |
The minimum <LengthOfStay>. must be less than the maximum <LengthOfStay>.. |
| 8014 |
Can't understand status application control in RateAmountMessage |
The given RateAmountMessage can't be processed, because the <StatusApplicationControl> element is missing. Add the element and try again. |
| 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 |
We can't find a currency for the given XML element in the RateAmountMessage. Also, no default currency is set. |
| 8017 |
Can't understand nightly rate for RateAmountMessage / BaseByGuestAmt |
We can't understand the nightly rate given in the XML element specified in the string at the end of the error message. |
| 8018 |
We can't process the AvailStatusMessage with the given index. We don't recognize the value of the RestrictionStatus, which is shown in the error message |
The total price (<Baserate> + tax/fee) in the OTA XML message can't be understood. |
| 8019 |
Can't understand the tax/fee amount from the XML |
Make sure you're sending the correct tax/fee XML message. |
| 8020 |
Can't understand the basis attribute for the given tax/fee |
The total price (<Baserate> + 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) |
We 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 |
We 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, we expected to receive one <RestrictionStatus> and one <LengthOfStay>.. |
| 8025 |
Advanced booking value for AvailStatusMessage is malformed |
N/A |
| Code |
Message |
Description |
| 10001 |
Unexpected PointOfSale data |
The <PointOfSale>. data provided is not the expected landing page. |
| 10002 |
Unexpected PointOfSale element |
N/A |
| 10003 |
Invalid PointOfSale type |
N/A |
| 10006 |
Can't understand PointOfSale attribute |
N/A |
| 10016 |
URL is missing for PointOfSale |
N/A |
| 10017 |
Can't understand PointOfSale |
N/A |
| 10018 |
Can't understand match status |
N/A |
| 10019 |
Language is invalid |
N/A |
| 10020 |
Unknown match for sitetype |
N/A |
| 10021 |
Unknown match for devicetype |
N/A |
| 10022 |
No partner name found |
N/A |
| 10023 |
Parsing error for partner |
N/A |
| 10024 |
No valid landing pages found |
N/A |
| 10027 |
A DisplayName is duplicated across more than one PointOfSale |
N/A |
| 10028 |
No PointOfSale found |
N/A |
| 10029 |
A DisplayName is duplicated across more than one PointOfSale |
N/A |
| 10030 |
Can't recognize the binary file |
N/A |
| 10031 |
Found duplicate language display names |
N/A |