Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Saat Google mengirimkan pesan Permintaan Petunjuk, server Anda harus merespons dengan pesan Respons Petunjuk yang menentukan hotel yang harganya telah berubah sejak terakhir kali Google menerima Respons Petunjuk yang berhasil dari server yang sama. Jika ada perubahan harga, Google akan mengirimkan <Query> yang mengambil data harga yang diperbarui untuk hotel dan itinerari yang ditunjukkan.
Untuk ringkasan proses penetapan ulang harga, lihat
Ringkasan Harga.
Pesan Respons Petunjuk menggunakan metode berikut untuk menentukan ulang harga hotel yang dipilih dan itinerarinya:
Elemen root pesan Respons Petunjuk adalah <Hint>. Anda meminta hotel atau
itinerari agar diperbarui menggunakan satu atau beberapa elemen <Item>. Satu pesan Respons
Petunjuk dapat menentukan sejumlah elemen <Item>.
Setiap pesan Respons Petunjuk harus menentukan minimal satu elemen <Property> untuk
setiap <Item>. <Property> mengidentifikasi hotel menggunakan ID yang sama seperti
Daftar Hotel. Secara default, Anda dapat menentukan satu ID hotel untuk setiap blok
<Item>. Namun, Anda dapat menginstruksikan Google untuk mengizinkan beberapa hotel dalam blok item jika Anda menggunakan rentang tanggal check in atau masa inap dengan rentang untuk penetapan ulang harga.
Alur permintaan dan respons itinerari pasti
Pesan petunjuk dapat didasarkan pada itinerari individual seperti kombinasi
tanggal check-in dan lama menginap. Dalam hal ini, Anda menentukan tanggal check in dan lama menginap untuk hotel Anda, dan Google mengambil data harga baru hanya untuk itinerari tersebut.
Respons partner
Pesan Respons Petunjuk berikut menentukan satu properti dan satu
itinerari:
Kemudian, Anda diharapkan untuk membuat <Transaction> dengan pembaruan harga untuk
hotel untuk lama menginap berikut:
5/20/23 - 5/23/23
Alur permintaan dan respons rentang tanggal check in
Pesan Respons Petunjuk dapat menentukan rentang tanggal check in, dimulai dengan tanggal check in pertama dan diakhiri dengan tanggal check in terakhir. Saat Google mengambil data harga baru, Google mengambil itinerari untuk setiap tanggal check in untuk hotel yang dimulai dengan tanggal tersebut dan memperpanjang hingga lama menginap yang Anda tentukan.
Rentang tanggal partner
Contoh berikut untuk pesan Respons Petunjuk menentukan satu properti dengan
rentang tanggal untuk check in:
Contoh ini menggunakan lama menginap 5 malam. Lama menginap default adalah 30
hari.
Alur permintaan dan respons rentang menginap
Pesan Respons Petunjuk dapat mencakup rentang tanggal yang telah berubah. Tindakan ini
memberi tahu Google bahwa Google harus mengambil itinerari apa pun yang terpengaruh oleh salah satu
tanggal tersebut. Kumpulan itinerari yang sebenarnya diambil adalah fungsi dari kumpulan tanggal dengan perubahan dan lama menginap maksimum.
Menginap dengan rentang partner
Contoh pesan Respons Petunjuk berikut menggunakan rentang menginap:
Semua hak dilindungi undang-undang. Java adalah merek dagang terdaftar dari Oracle dan/atau afiliasinya.
Terakhir diperbarui pada 2025-07-25 UTC.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Informasi yang saya butuhkan tidak ada","missingTheInformationINeed","thumb-down"],["Terlalu rumit/langkahnya terlalu banyak","tooComplicatedTooManySteps","thumb-down"],["Sudah usang","outOfDate","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Masalah kode / contoh","samplesCodeIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-07-25 UTC."],[[["\u003cp\u003eWhen Google requests hotel price updates via a Hint Request message, your servers should respond with a Hint Response message detailing the hotels with changed pricing.\u003c/p\u003e\n"],["\u003cp\u003eHint Response messages can specify price changes using three methods: exact itineraries (specific check-in date and length of stay), check-in date ranges, and ranged stays (affecting multiple itineraries).\u003c/p\u003e\n"],["\u003cp\u003eGoogle then sends a Query message requesting updated pricing data for the specified hotels and itineraries based on the Hint Response.\u003c/p\u003e\n"],["\u003cp\u003eAfter receiving the Query, you need to provide a Transaction message containing the updated prices for the requested itineraries.\u003c/p\u003e\n"],["\u003cp\u003eIf Changed Pricing is not implemented, Google fetches data for all hotels in your Hotel List, potentially leading to unnecessary data transfers.\u003c/p\u003e\n"]]],[],null,["# Hint Response Messages\n\nWhen Google sends a [Hint Request\nmessage](/hotels/hotel-prices/dev-guide/hint-request-messages), your servers\nshould respond with a Hint Response message that specifies the hotels whose\nprices have changed since the last time Google received a successful Hint\nResponse from those same servers. If there are any price changes, Google then\nsends a [`\u003cQuery\u003e`](../xml-reference/queries#Query) that fetches the updated pricing data for the indicated\nhotels and itineraries.\n\nFor an overview of the repricing process, see the\n[Pricing Overview](/hotels/hotel-prices/dev-guide/updating-prices).\n| **Key Point:** If you don't implement [Changed Pricing](/hotels/hotel-prices/dev-guide/delivery-mode#hints), Google fetches data for all hotels in your [Hotel List](../xml-reference/hotel-list-feed).\n\nHint Response messages uses the following methods to reprice the selected hotels\nand their itineraries:\n\n- [Exact itineraries](#type1)\n- [Check-in date ranges](#type2)\n- [Ranged stays](#type3)\n\n| **Note:** The default length of stay using Changed Pricing is 30 days.\n\nThe root element of a Hint Response message is [`\u003cHint\u003e`](../xml-reference/queries#Hint). You request a hotel or\nitinerary to be updated by using one or more [`\u003cItem\u003e`](../xml-reference/queries#Item) elements. A single Hint\nResponse message can define any number of `\u003cItem\u003e` elements.\n\nEach Hint Response message must specify at least one `\u003cProperty\u003e` element for\neach `\u003cItem\u003e`. The `\u003cProperty\u003e` identifies a hotel by using the same IDs as\nthe [Hotel List](../xml-reference/hotel-list-feed). By default, you specify a single hotel ID for each `\u003cItem\u003e`\nblock. However, you can instruct Google to allow multiple hotels in an item\nblock if you are using check-in date ranges or ranged stays for repricing.\n\nExact itinerary request and response flow\n-----------------------------------------\n\nHint messages can be based on individual itineraries such as the combination of\ncheck-in date and length of stay. In this case, you specify a check-in date and\nlength of stay for your hotels, and Google fetches the new pricing data for just\nthat itinerary. \n\n### Partner's response\n\nThe following Hint Response message defines a single property and a single\nitinerary: \n\n \u003cHint\u003e\n \u003cItem\u003e\n \u003cProperty\u003e12345\u003c/Property\u003e\n \u003cStay\u003e\n \u003cCheckInDate\u003e2023-05-20\u003c/CheckInDate\u003e\n \u003cLengthOfStay\u003e3\u003c/LengthOfStay\u003e\n \u003c/Stay\u003e\n \u003c/Item\u003e\n \u003c/Hint\u003e\n\n### Google's response\n\nGoogle responds to your Hint Response message with a [`\u003cQuery\u003e`](../xml-reference/queries#Query) similar to the\nfollowing: \n\n \u003cQuery\u003e\n \u003cCheckin\u003e2023-05-20\u003c/Checkin\u003e\n \u003cNights\u003e3\u003c/Nights\u003e\n \u003cPropertyList\u003e\n \u003cProperty\u003e12345\u003c/Property\u003e\n \u003c/PropertyList\u003e\n \u003c/Query\u003e\n\n### Create `\u003cTransaction\u003e`\n\nYou are then expected to create a [`\u003cTransaction\u003e`](../xml-reference/transaction-messages#Transaction) with price updates for the\nhotel for the following stay: \n\n 5/20/23 - 5/23/23\n\nCheck-in date ranges request and response flow\n----------------------------------------------\n\nA Hint Response message can specify a range of check-in dates, beginning with\nthe first check-in date and ending with the last check-in date. When Google\nfetches new pricing data, Google pulls itineraries for every check-in date for\nthe hotel starting with those dates and extending up to the length of stay that\nyou indicate. \n\n### Partner's ranged dates\n\nThe following example for Hint Response message defines a single property with\na range of dates for the check-in: \n\n \u003cHint\u003e\n \u003cItem\u003e\n \u003cProperty\u003e12345\u003c/Property\u003e\n \u003cFirstDate\u003e2023-05-20\u003c/FirstDate\u003e\n \u003cLastDate\u003e2023-05-23\u003c/LastDate\u003e\n \u003c/Item\u003e\n \u003c/Hint\u003e\n\n### Google's response\n\nGoogle responds to this Hint Response message with [`\u003cQuery\u003e`](../xml-reference/queries#Query) similar to\nthe following: \n\n \u003cQuery\u003e\n \u003cFirstDate\u003e2023-05-20\u003c/FirstDate\u003e\n \u003cLastDate\u003e2023-05-23\u003c/LastDate\u003e\n \u003cNights\u003e5\u003c/Nights\u003e\n \u003cPropertyList\u003e\n \u003cProperty\u003e12345\u003c/Property\u003e\n \u003c/PropertyList\u003e\n \u003c/Query\u003e\n\n### Create `\u003cTransaction\u003e`\n\nYou are then expected to create a [`\u003cTransaction\u003e`](../xml-reference/transaction-messages#Transaction) with price updates\nfor the following stays for that hotel: \n\n 5/20/23 - 5/21/23\n 5/20/23 - 5/22/23\n 5/20/23 - 5/23/23\n 5/20/23 - 5/24/23\n 5/20/23 - 5/25/23\n\n 5/21/23 - 5/22/23\n 5/21/23 - 5/23/23\n 5/21/23 - 5/24/23\n 5/21/23 - 5/25/23\n 5/21/23 - 5/26/23\n\n 5/22/23 - 5/23/23\n 5/22/23 - 5/24/23\n 5/22/23 - 5/25/23\n 5/22/23 - 5/26/23\n 5/22/23 - 5/27/23\n\nThis example uses length of stay of 5 nights. The default length of stay is 30\ndays.\n\nRanged stays request and response flow\n--------------------------------------\n\nA Hint Response message can include a range of dates that have changed. This\ninforms Google that it should fetch any itinerary affected by any of those\ndates. The actual set of itineraries fetched is a function of both the set of\ndates with changes and the maximum length of stay. \n\n### Partner's ranged stays\n\nThe following example Hint Response message uses ranged stays: \n\n \u003cHint\u003e\n \u003cItem\u003e\n \u003cProperty\u003e12345\u003c/Property\u003e\n \u003cStaysIncludingRange\u003e\n \u003cFirstDate\u003e2023-05-20\u003c/FirstDate\u003e\n \u003cLastDate\u003e2023-05-23\u003c/LastDate\u003e\n \u003c/StaysIncludingRange\u003e\n \u003c/Item\u003e\n \u003c/Hint\u003e\n\n### Google's response\n\nGoogle responds to your Hint Response message with a [`\u003cQuery\u003e`](../xml-reference/queries#Query) similar to the\nfollowing: \n\n \u003cQuery\u003e\n \u003cFirstDate\u003e2023-05-20\u003c/FirstDate\u003e\n \u003cLastDate\u003e2023-05-23\u003c/LastDate\u003e\n \u003cAffectedNights\u003e3\u003c/AffectedNights\u003e\n \u003cPropertyList\u003e\n \u003cProperty\u003e12345\u003c/Property\u003e\n \u003cProperty\u003e67891\u003c/Property\u003e\n \u003c/PropertyList\u003e\n \u003c/Query\u003e\n\n### Create `\u003cTransaction\u003e`\n\nYou are then expected to create a [`\u003cTransaction\u003e`](../xml-reference/transaction-messages#Transaction) with price updates for the\nhotel for the following stays: \n\n 5/17/23 - 5/20/23\n\n 5/18/23 - 5/20/23\n 5/18/23 - 5/21/23\n\n 5/19/23 - 5/20/23\n 5/19/23 - 5/21/23\n 5/19/23 - 5/22/23\n\n 5/20/23 - 5/21/23\n 5/20/23 - 5/22/23\n 5/20/23 - 5/23/23\n\n 5/21/23 - 5/22/23\n 5/21/23 - 5/23/23\n 5/21/23 - 5/24/23\n\n 5/22/23 - 5/23/23\n 5/22/23 - 5/24/23\n 5/22/23 - 5/25/23\n\n 5/23/23 - 5/24/23\n 5/23/23 - 5/25/23\n 5/23/23 - 5/26/23\n\n| **Note:** With ranged stays, all itineraries including those that start *before* the first date and those that overlap with it should be repriced."]]
