> ## Documentation Index > Fetch the complete documentation index at: https://docs.axisdata.net/llms.txt > Use this file to discover all available pages before exploring further. # OTA_HotelResRS The OTA\_HotelResRS (Hotel Reservation Response) confirms quote or commit processing for a hotel booking and returns room-level totals, linked guest profiles, partner references, cancellation policies, and optional TPA extensions. It is returned in reply to an `OTA_HotelResRQ` of type Quote or Commit. ## Purpose * Confirm successful processing (``) or return error diagnostics (``). [Error Scenarios](../glossary/errors). * Return one `HotelReservation` with one or more `RoomStay` items, linked `ResGuests`, optional `Services`, 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 penalties per contract. ## Structure – Root Element ```xml theme={null} ... ``` When `` is absent, inspect `` for diagnostics; multiple `` items may be returned. [Error Scenarios](../glossary/errors) ## Structure – Core Elements ### HotelReservation Envelope and item for the reservation response. Contains: `RoomStays`, optional `Services` (e.g., board), `ResGuests`, `ResGlobalInfo`, and `TPA_Extensions`. ### RoomStays Each `RoomStay` represents one reserved room (or quoted room) for the booking. It is very similar as the `RoomStay` returned in the [avail response](/searchRS#roomstays). * `RoomStay@RPH` is the room key used across the response; `IndexNumber` is a 1‑based display index. * Includes room identification (`RoomTypes/RoomType@RoomTypeCode`), `RoomDescription`, pricing at room level (`Total`), stay dates (`TimeSpan@Start/End`), and links to guests/services via `ResGuestRPHs` / `ServiceRPHs`. * Property context can be repeated under `RoomStay/BasicPropertyInfo` when needed. * Under `Features`, the booked board and a short description can be found. * `ResGuestRPH` and `ServiceRPH` link the Services and ResGuests to this RoomStay. * `Total@AmountAfterTax` returns the rate for this RoomStay. **Example** ```xml theme={null} Standard Room BB Breakfast ``` ### Services Non-room services (e.g., board) appear under `Services/Service` and can be linked to a `RoomStay` via `ServiceRPHs`. ```xml theme={null} ``` ### ResGuests Passenger/guest profiles for the booking, referenced from rooms and services via `ResGuestRPH`. * Adults `AgeQualifyingCode="10"`; Children `"8"`; Infants `"7"`. ```xml theme={null} Mr Bender Bending ``` ### ResGlobalInfo Holds booking totals, comments, partner/child references, cancellation penalties, handling office, and optional property/vendormessages context. #### Totals Booking-level roll‑up amount for all rooms and services. ```xml theme={null} ... ``` #### Comments Returns the specified comments at the RQ. ```xml theme={null} late arrival - flight lands at 22:55 local time ``` #### HotelReservationIDs * `ResID_Type="36"` — partner (distributor) reference (must be unique; prevents duplicates; print on voucher). * `ResID_Type="37"` — child references per item; associate with rooms/services via `Item_RPH`. ```xml theme={null} ``` #### CancelPenalties Cancellation policy is linked to the room using `CancelPenalty@Item_RPH` (matching the room `RPH`). Deadlines can be expressed relative to arrival or booking. ```xml theme={null} ``` #### BasicPropertyInfo Optional property context at booking level; [Vendor Messages](../general/messaging#vendor-messages) can include local taxes or operational notices. ```xml theme={null} Tax Payable Locally, Currency: EUR, type: city tax Due to the local logistics infrastructure, there is a possibility that your meeting point for arrival and departure transfer may not be direct at the hotel door, Approx. Distance: > 600 m ``` #### Handling Office Handling office details are provided under `Profiles/ProfileInfo/Profile/CompanyInfo/CompanyName`. ```xml theme={null} ``` ### TPA\_Extensions Provider-specific details. #### RateDetails Breakdown by guest and stay day; includes per‑guest totals and booking‑level totals under `Totals`. Returned if `Instance=PriceBreakdown` is specified at the RQ. ```xml theme={null} ``` #### BookingStatus Reservation status echo (TPA namespace), typically `ReservationStatusType="Available"` for a successful Quote/Commit. ```xml theme={null} ``` #### Extras Optional and included extras. Optional extras may be offered or booked; see `IncludedInRate`, `Applicability`, `Amount`, and `ResGuestRPH`. ## Complete Examples ```xml Basic Expandable theme={null} Standard Room BB Breakfast Mr Bender Bending Mrs Angelina Bending Jr Ben Bending late arrival - flight lands at 22:55 local time Due to the local logistics infrastructure, there is a possibility that your meeting point for arrival and departure transfer may not be direct at the hotel door ``` ```xml Multiroom Expandable theme={null} Standard Room BB Breakfast SingleUse Standard Room BB Breakfast Mr Bender Bending Mrs Angelina Bending Dr John Zoidberg late arrival - flight lands at 22:55 local time Due to the local logistics infrastructure, there is a possibility that your meeting point for arrival and departure transfer may not be direct at the hotel door ``` ## Best Practices 1. Always supply a unique partner reference (`ResID_Type="36"`) and reuse it for cancel/read operations. 2. Use `ResStatus="Quote"` before `Commit` to confirm pricing, availability, and penalties. 3. Provide `NamePrefix` for all adult guests and keep guest ordering consistent across rooms and services. 4. Link rooms, guests and services using `RPH` consistently; use `CancelPenalty@Item_RPH` to map policies to rooms. 5. For multi-room bookings, include each room as a separate `RoomStay` (up to 5 rooms) so combined availability is validated. 6. When booking optional extras, include them in the request and consume them from `TPA_Extensions/Extras` in the response.