AI-generated Key Takeaways
-
Validate your hotel data feeds with published schemas before submitting to Google to ensure they are correctly formatted.
-
Use the provided table to find the correct schema based on the type of data feed and pricing delivery mode.
-
Utilize a third-party XML tool like
xmllint
along with the schema location to validate your feed files. -
When using
xmllint
, ensure you replacehttps:
withhttp:
in the schema location URL for proper validation. -
Refer to the provided examples for validating against specific schemas like Transaction or Hotel List Feed.
Before submitting your feeds to Google, you can validate them with published schemas.
The following table lists the available schemas that you can use to validate your feeds against:
Schema Download | Applicable pricing delivery modes | Schema Location |
---|---|---|
Hotel List | All | gstatic.com/localfeed/local_feed.xsd |
Landing pages | All | gstatic.com/ads-travel/hotels/api/point_of_sale.xsd |
Transaction (Property Data) | ARI | gstatic.com/ads-travel/hotels/api/transaction_property_data.xsd |
Transaction (Property Data) Response | ARI | gstatic.com/ads-travel/hotels/api/transaction_property_data_response.xsd |
OTA_HotelRateAmountNotifRQ | ARI | gstatic.com/ads-travel/hotels/api/ota_hotel_rate_amount_notif_rq.xsd |
OTA_HotelRateAmountNotifRS | ARI | gstatic.com/ads-travel/hotels/api/ota_hotel_rate_amount_notif_rs.xsd |
OTA_HotelAvailNotifRQ | ARI | gstatic.com/ads-travel/hotels/api/ota_hotel_avail_notif_rq.xsd |
OTA_HotelAvailNotifRS | ARI | gstatic.com/ads-travel/hotels/api/ota_hotel_avail_notif_rs.xsd |
OTA_HotelInvCountNotifRQ | ARI | gstatic.com/ads-travel/hotels/api/ota_hotel_inv_count_notif_rq.xsd |
OTA_HotelInvCountNotifRS | ARI | gstatic.com/ads-travel/hotels/api/ota_hotel_inv_count_notif_rs.xsd |
TaxFeeInfo | ARI | gstatic.com/ads-travel/hotels/api/tax_fee_info.xsd |
TaxFeeInfoResponse | ARI | gstatic.com/ads-travel/hotels/api/tax_fee_info_response.xsd |
Promotions | ARI | gstatic.com/ads-travel/hotels/api/promotions.xsd |
PromotionsResponse | ARI | gstatic.com/ads-travel/hotels/api/promotions_response.xsd |
RateModifications | ARI | gstatic.com/ads-travel/hotels/api/rate_modifications.xsd |
RateModificationsResponse | ARI | gstatic.com/ads-travel/hotels/api/rate_modifications_response.xsd |
Transaction | Pull, Changed Pricing | gstatic.com/ads-travel/hotels/api/transaction.xsd |
Rate rules | Pull, Changed Pricing | gstatic.com/ads-travel/hotels/api/private_rates.xsd |
Hint Response | Changed Pricing | gstatic.com/ads-travel/hotels/api/hint.xsd |
Query (from Google to partners) | Pull, Changed Pricing, Live Pricing Query | gstatic.com/ads-travel/hotels/api/query.xsd |
How to validate files
To validate your files with these schemas, you can use a third-party XML tool
such as xmllint
.
The syntax for using xmllint
to validate a schema is as follows:
xmllint --schema schema_location file_to_validate
The following example validates the mypriceupdates.xml
file against the
Transaction message schema:
xmllint --schema http://gstatic.com/ads-travel/hotels/api/transaction.xsd mypriceupdates.xml
The following example validates the myfeed.xml
file against the Hotel List
Feed schema and shows errors if they exist:
xmllint --noout --schema http://gstatic.com/localfeed/local_feed.xsd myfeed.xml