Google에서 힌트 요청 메시지를 전송하면 서버는 Google이 동일한 서버로부터 마지막으로 힌트 응답을 수신한 이후 가격이 변경된 호텔을 지정하는 힌트 응답 메시지로 응답해야 합니다. 가격이 변경되면 Google은 지정된 호텔 및 숙박 일정의 업데이트된 가격 데이터를 가져오는 <Query>를 전송합니다.
힌트 응답 메시지의 루트 요소는 <Hint>입니다. 하나 이상의 <Item> 요소를 사용하여 호텔 또는 숙박 일정 업데이트를 요청합니다. 단일 힌트 응답 메시지는 <Item> 요소를 원하는 만큼 정의할 수 있습니다.
각 힌트 응답 메시지는 각 <Item>에 대해 하나 이상의 <Property> 요소를 지정해야 합니다. <Property>는 호텔 목록과 동일한 ID를 사용하여 호텔을 식별합니다. 기본적으로 각 <Item> 블록에 하나의 호텔 ID를 지정합니다. 하지만 재가격 책정에 체크인 기간 또는 숙박 기간 범위를 사용하는 경우 Google에 상품 블록에서 여러 호텔을 허용하도록 지시할 수 있습니다.
정확한 숙박 일정 요청 및 응답 흐름
힌트 메시지는 체크인 날짜와 숙박 기간의 조합과 같은 개별 숙박 일정을 기반으로 할 수 있습니다. 이 경우 호텔의 체크인 날짜와 숙박 기간을 지정하면 Google에서 해당 숙박 일정에 대한 새 가격 데이터만 가져옵니다.
All rights reserved. 자바는 Oracle 및/또는 Oracle 계열사의 등록 상표입니다.
최종 업데이트: 2025-07-25(UTC)
[null,null,["최종 업데이트: 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."]]
