Skip to main content
The Book functionality for our RatePlanToken product is directly based on our original OTA_HotelResRQ/RS. The request message is almost identical from the classic model.

​
Purpose

  • Confirm successful processing (<Success/>) or return error diagnostics (<Errors/>). Error Scenarios.
  • Return one HotelReservation with one RoomStay item, linked ResGuests, and booking-level context under ResGlobalInfo.
  • Quote (ResStatus="Quote" in the request): verify availability, totals, and cancellation policy without creating a reservation ID at Axis Data (the client reference is echoed).
  • Commit (ResStatus="Commit" in the request): create a binding booking if accepted, with cancellation penalties per contract.

​
Details and Structure

All the details regarding this message can be found at OTA_HotelResRS. The Booking for RP Token products has to be done using the RatePlanToken, retrieved from the Search Response. The Response will echo this RatePlanToken

​
RatePlanToken

This code, once requested in the Book Request will be echoed in the Booking Response as follows:

​
Differences with classic Hotel Book

The structure of the message is exactly the same as OTA_HotelResRS plus the RatePlanToken.

​
What’s not included

All other elements and their rules are equivalent to the traditional booking flow, including Price Breakdown usage.

​
RatePlans and Multicontracting

In this flow, rateplans and multicontracting are always included. The codes, in this case, will already be encoded inside the RatePlanToken and don’t need to be used in the traditional “concatenated to room code” approach. The Rateplan code is needed to ensure a proper distribution of the rates. It will be visible in the booking confirmation in the following section, but it does not have to be used at the booking request.

​
Taxes and Fees

The Taxes and Fees are small rates or commisions that may be added to a booking if a contract requests it. There are three main types of Taxes and Fees:
  • Mandatory: They are treated as a supplement in the contract, and calculated as one in the booking. Visible in Price Breakdown.
  • Included: They are included in the hotel rate. They are visible under the Tax section as “Inclusive”.
  • Payable Locally: Taxes for the customer to pay on spot. They are visible under the tax section as “Exclusive”.
The Code represents which type of Tax or Fee the element refers to. The Mapping of the codes is the following: ChargeFrequency uses OTA CHG codes:
  • 1 per night
  • 12 per stay
  • 18 per room per stay
  • 19 per room per night
  • 20 per pax per stay
  • 21 per pax per night
Code uses OTA FTT codes:
  • 3 city tax
  • 6 federal tax
  • 30 country tax
  • 12 resort fee
  • 18 tourism tax
  • 27 miscellaneous
  • 5 energy tax
  • 36 VAT

​
Complete Examples