예약 가능 여부, 요금, 인벤토리 (ARI)는 야간 요금, 예약 가능 여부, 인벤토리를 제어하고 이를 결합하는 방법에 제약 조건을 적용하는 가격 게재 모드입니다. 또한 ARI는 세금, 수수료, 프로모션을 유연하게 포함할 수 있습니다.
숙박 일정 기반 가격 책정 전송 모드인 가격 가져오기 및 변동된 가격과 달리 ARI 피드는 특정 가격 또는 숙박 일정에 대해 쿼리되지 않습니다. 대신 가격 모델에 요금 세부정보, 제한사항, 이용 가능 여부 변경과 같은 새 데이터 또는 변경된 데이터가 있을 때 메시지를 푸시합니다.
이점
ARI는 다음과 같은 이점을 제공합니다.
대역폭 효율성: 전송해야 하는 데이터 양을 줄여 대역폭 효율성을 높입니다. Google은 매일 밤 ARI 데이터와 증분 변경사항만 전송하여 다양한 사전 구매 및 숙박 일수 값에 대한 가격을 계산하고 업데이트할 수 있습니다.
가격 정확도: 변경사항 푸시 이벤트 모델을 사용하여 실시간 업데이트를 제공하여 가격 정확성을 개선합니다.
더 넓은 가격 범위: 다양한 숙박 경로에 결합된 세분화된 데이터를 사용하여 더 넓은 가격 범위 (가격이 포함된 숙박 경로 수)를 달성합니다.
유연성: 프로모션 및 패키지를 더 유연하게 제공할 수 있습니다.
사용 편의성: 시스템에 저장되는 방식과 일치하는 방식으로 데이터를 전송하므로 여러 경로의 가격을 계산하거나 캐시할 필요가 없습니다.
요청 메시지 유형
Google에 전송되는 ARI 메시지는 ARI '요청' 메시지라고 합니다. Google은 이후 성공 또는 실패를 나타내는 '응답' 메시지를 반환합니다.
ARI는 사용 가능 여부 및 인벤토리를 정의하기 위한 일부 기본 메시지 유형에 OpenTravel Alliance (OTA)의 표준 프로토콜을 따릅니다.
수신된 각 요청 메시지에 대해 Google은 서버 연결에 성공한 경우 HTTP 200 OK로 응답하고 업데이트가 성공적으로 적용되었는지 또는 경고나 오류가 발생했는지를 나타내는 응답 메시지가 포함된 본문을 포함합니다. Google에서 HTTP 오류 코드로 응답하면 메시지를 다시 전송합니다. HTTP 응답 본문에 경고나 오류가 포함된 경우 메일을 다시 보내기 전에 이를 수정해야 합니다. Hotel Center의 피드 상태 페이지에서 특정 메시지에 발생한 문제를 확인할 수도 있습니다.
Live on Google (LoG)
'Google에 게시'(LoG)를 사용하면 Google 웹사이트에 호텔을 표시할 수 있습니다.
호텔의 기본 LoG 값은 true이므로 새 호텔은 Google에 자동으로 표시됩니다.
LoG를 사용하면 Google Ads의 상태 또는 숙박 시설의 요금이 Google에 있는지 여부에 관계없이 Hotel Center 계정에서 광고 및 무료 예약 링크에 내 숙박 시설을 사용 설정하거나 사용 중지할 수 있습니다.
호텔의 LoG 값을 설정하는 방법에는 두 가지가 있습니다. Travel Partner API or the Hotel Center
properties page. You can change the status of your existing properties in the
Live on Google column on the Hotel Center properties
page, or if you want to change the status
of a large number of properties at the same time, you can use the
Travel Partner API.
All rights reserved. 자바는 Oracle 및/또는 Oracle 계열사의 등록 상표입니다.
최종 업데이트: 2025-07-25(UTC)
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["필요한 정보가 없음","missingTheInformationINeed","thumb-down"],["너무 복잡함/단계 수가 너무 많음","tooComplicatedTooManySteps","thumb-down"],["오래됨","outOfDate","thumb-down"],["번역 문제","translationIssue","thumb-down"],["샘플/코드 문제","samplesCodeIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-07-25(UTC)"],[[["\u003cp\u003eAvailability, Rates, and Inventory (ARI) is a pricing model that allows hotels to push updates on rates, availability, inventory, and other pricing details to Google.\u003c/p\u003e\n"],["\u003cp\u003eARI offers benefits like bandwidth efficiency, price accuracy, greater price coverage, flexibility, and ease of use.\u003c/p\u003e\n"],["\u003cp\u003eFour key message types (transaction, rate, inventory, availability) are required for pricing to be available on Google.\u003c/p\u003e\n"],["\u003cp\u003eLive on Google (LoG) allows hotels to control their visibility on Google for free and paid bookings and can be managed through Hotel Center or the Travel Partner API.\u003c/p\u003e\n"],["\u003cp\u003eHotels should send ARI updates whenever data changes and can use the provided endpoints to push their data to Google.\u003c/p\u003e\n"]]],[],null,["# ARI Overview\n\nAvailability, Rates, and Inventory (ARI) is a pricing delivery mode that\ncontrols nightly rates, availability, and inventory, and provides constraints on\nhow these can be combined. ARI also provides flexibility to include taxes, fees,\nand promotions.\n\nUnlike the itinerary-based pricing [delivery\nmodes](/hotels/hotel-prices/dev-guide/delivery-mode), Pull and Changed\nPricing, ARI feeds aren't queried for specific prices or itineraries. Instead,\nyou push messages when your pricing model has new or changed data, such as\nchanges to rate details, restrictions, and availability.\n\nBenefits\n--------\n\nARI offers the following benefits:\n\n- **Bandwidth efficiency**: Increases bandwidth efficiency by reducing the\n volume of data that needs to be transmitted. By sending nightly ARI data and\n only incremental changes, Google can compute prices and updates for a wide\n range of advance purchase and length of stay values.\n\n- **Price accuracy**: Improves price accuracy by using a push-on-change event\n model to give live updates.\n\n- **Greater price coverage**: Achieves a higher price coverage (number of\n itineraries with prices) by using granular data that is combined into various\n itineraries.\n\n- **Flexibility**: Enables greater flexibility with offering promotions and\n packages.\n\n- **Ease of Use**: Transmits data in a way that is aligned with how it is\n stored on your system, avoiding the need to compute or cache prices for\n many itineraries.\n\nRequest message types\n---------------------\n\nARI messages sent to Google are termed as ARI \"request\" messages. Google\nsubsequently returns \"response\" messages indicating success or failure.\n\nARI follows the standard protocols of `OpenTravel Alliance (OTA)` for some of\nthe main message types for defining availability and inventory.\n| **Key Point:** You must send the four message types---transaction, rate, inventory, and availability---before pricing is available. It is recommended that you limit the size of ARI messages specifically `\u003cOTA_HotelRateAmountNotifRQ\u003e` to 5MB with a limit of 400 files per second upload rate.\n\nARI uses the following request messages:\n\n- [`Transaction` (Property Data)](/hotels/hotel-prices/xml-reference/ari-property).\n Defines the room type and package (rate plan) information.\n\n- [`OTA_HotelRateAmountNotifRQ`](/hotels/hotel-prices/xml-reference/ari-rate).\n Defines the per-date or LOS-based occupancy rate amounts per product (room\n type and rate plan combination) for specific date ranges.\n\n- [`OTA_HotelAvailNotifRQ`](/hotels/hotel-prices/xml-reference/ari-avail).\n Defines availability and restrictions based on room type and rate plans.\n Inventory can also be updated using this message, but\n `OTA_HotelInvCountNotifRQ` is preferred.\n\n- [`OTA_HotelInvCountNotifRQ`](/hotels/hotel-prices/xml-reference/ari-inv).\n Defines the physical room inventory or number of rooms available to be sold.\n\n- [`TaxFeeInfo`](/hotels/hotel-prices/xml-reference/ari-tax).\n (Optional) Defines per-property taxes and fees. This message isn't required\n if `AmountAfterTax`is specified in the `OTA_HotelRateAmountNotifRQ` message.\n\n- [`Promotions`](/hotels/hotel-prices/xml-reference/ari-promotions).\n (Optional) Defines promotional rates for certain bookings, stays, and\n users.\n\n- [`RateModifications`](/hotels/hotel-prices/xml-reference/ari-rate-modifications).\n (Optional) Defines rate modification rules for certain bookings, stays, and\n users.\n\n- [`ExtraGuestCharges`](/hotels/hotel-prices/xml-reference/ari-extra-guest-charges).\n (Optional) Defines how rates should be configured for children and\n additional adults.\n\nEach message contains a subset of information that Google uses to compute the\nprices and availability displayed to users when they search for your properties\nwith specific check-in and check-out dates and desired occupancy.\n\nFor more information about ARI, refer to the\n[XML Reference](/hotels/hotel-prices/xml-reference/ari-overview).\n\nPush messages\n-------------\n\nTo update ARI and property information, send the associated messages whenever\ndata changes in your system.\n| **Key Point:** Message data will be merged with data that has already been pushed. Therefore, you only need to push new or changed data.\n\nUse the following guidelines when sending messages:\n\n- Use the self-serve tool in the\n [Hotel Center Price Settings page](//hotelcenter.google.com/prices/settings)\n to add or update your IP addresses in our system.\n\n- Use the following base path for the endpoint:\n\n - `https://www.google.com` or `Host: www.google.com Port: 443`\n- Send messages using the `HTTP POST` method.\n\n- Set the `Content-Type` header to `application/xml`.\n\n- There is an account-level maximum update rate of 400 messages per second.\n If you exceed this limit, an error code of\n [6032](/hotels/hotel-prices/dev-guide/feed-status-errors#6032) is returned.\n\n- Use the following paths depending on the data being updated:\n\n \u003e - `Transaction` (Property Data): `/travel/hotels/uploads/property_data`\n \u003e - `OTA_HotelRateAmountNotifRQ`: `/travel/hotels/uploads/ota/hotel_rate_amount_notif`\n \u003e - `OTA_HotelAvailNotifRQ`: `/travel/hotels/uploads/ota/hotel_avail_notif`\n \u003e - `OTA_HotelInvCountNotifRQ`: `/travel/hotels/uploads/ota/hotel_inv_count_notif`\n \u003e - `TaxFeeInfo`: `/travel/hotels/uploads/taxes`\n \u003e - `Promotions`: `/travel/hotels/uploads/promotions`\n \u003e - `RateModifications`: `/travel/hotels/uploads/rate_modifications`\n \u003e - `ExtraGuestCharges`:`/travel/hotels/uploads/extra_guest_charges`\n\nFor each request message received, Google will respond with an `HTTP 200 OK`\nif the connection to the server succeeded and include a body with a response\nmessage indicating whether updates were applied successfully or encountered\nwarnings or errors. If Google responds with an HTTP error code, resend the\nmessage. If the HTTP response body contains warnings or errors, they should be\nfixed before resending the message. You can also view issues encountered for\nspecific messages on the Feed Status page in [Hotel Center](https://hotelcenter.google.com).\n\nLive on Google (LoG)\n--------------------\n\nLive on Google (LoG) lets you display your hotels on Google websites.\nSince the default LoG value for a hotel is `true`, any new hotels will\nautomatically be displayed on Google.\n\nUse LoG to turn your properties on and off for ads and free booking links in\nyour Hotel Center account, regardless of the status of Google Ads or whether the\nproperty has rates on Google.\n| **Key Point:** LoG is available for both Hotels and Vacation Rentals.\n\nThere are two ways to set a hotel's LoG value: the Travel Partner API or the Hotel Center properties page. You can change the status of your existing properties in the **Live on Google** column on the [Hotel Center properties\npage](//hotelcenter.google.com/properties), or if you want to change the status of a large number of properties at the same time, you can use the [Travel Partner API](/hotels/hotel-prices/api-reference/Usage).\n\nFor more details about LoG, refer to the [Hotel Center\nHelp](//support.google.com/hotelprices/answer/10981242).\n\nUsing the Travel Partner API, you can do the following:\n\n- View the status of your properties through the Hotel Center or use the\n `hotelViews.list` endpoint.\n\n- Retrieve a list of all your hotels displayed on Google by using the `filter`\n parameter with `liveOnGoogle = TRUE` in `hotelViews.list` endpoint.\n\n- Get a summary of the properties for a specific account including the number\n of properties live on Google by using `hotelViews.summary`.\n\nFor more information about how to set LoG using the API, refer to the\n[`hotelViews.list`\narticle](/hotels/hotel-prices/api-reference/rest/v3/accounts.hotelViews/list)\nand the [API Reference](/hotels/hotel-prices/api-reference/Usage)."]]