Clients are required to integrate to the Content API for receiving metadata, as soon as possible. We will continue to provide the Metadata files for existing clients who have not yet integrated to the Content API or are in the process of integrating.
Room-specific occupancy restrictions will be sent via the Metadata File and will include the following:
Direct Bill (DB) and all major Virtual Credit Cards (VCC) are accepted.
Only in certain cases where the hotel is charging the guest card for the reservation.
The pricing for all adults up to the MaxAdultOccupancy is sent in the \<BaseByGuestAmts> nodes. Additional child amount is sent in \<AdditionalGuestAmts> tag in ARI.
Yes. Child ages of 0-12 (inclusive) are supported.
The tag should contain the Demand Client code. The Demand Client in the reservation request should send the client-code in the following format.
<RequestorID Type = "22" ID = "client-code"/>
Yes, this node is mandatory but can be filled with a general client email address, although we highly recommend providing the guest email address since properties occasionally use this to validate the guest booking during inbound customer service calls that are placed directly with the hotel.
Resort Fees must be displayed or provided to all customers and clients before booking. See note in the Tax section.
After 10 minutes, the reservation is booked at the rates that are currently applicable. The back-office process is as follows -
Within 24 hours, an email will be sent to the clients with the notification that the rate sent was stale. The message will include supporting ARI messages.
Hotel Trader does not have a limit on the data sent across per single message. This can range from one day to a few year's worth of data.
Related article - Technical Best Practices
Hotel Trader’s PUSH API can provide access to several rateplan/board/meal-plan combinations. A property may choose to create a room-only or meal-plan included rateplan (half/full board). These options for mealplans are set up as an attribute of the rateplan. The available meal-plan options on each rateplan can be viewed in the Excel metadata sheet.
The price sent in the ARI for a rateplan does not include a break-up for meals/add-ons.
For example, say the rateplan HTRET is room only and in the ARI message, a price of $100 is sent. This price is only for the room. Another rateplan, say, HTRETB has room with breakfast included. The price sent in the ARI message for this rateplan could be $100, this is the price of room and breakfast combined.
No. Only 1 staggered policy will be present in a rateplan.
Staggered Policy is defined as a Cancellation Policy with multiple windows leading to the check-in date that will result in different penalty amounts if canceled in those windows.
Example,
Cxl Policy: Winter Special CXL Policy
Window 1: Cancel within 48 hours of Arrival: Non-Refundable
Window 2: Cancel within 7 days of Arrival: 75% Penalty
Window 3: Cancel within 30 days of Arrival: 50% Penalty
Related article - Seasonal Policies
| Standard Policy | Staggered Policy | Allowed (Yes/No) |
|---|---|---|
| True (multiple) | False | Yes |
| True (multiple) | True (only 1) | Yes |
| False | True (only 1) | Yes |
| True (multiple) | True (multiple) | No |
| False | True (multiple) | No |
| False | False | No |
Related article - Seasonal Policies