Reservation Types

This page details how to properly compose the reservation upload messages for the main reservation upload scenarios. Following these specific reservationID guidelines is essential to maximise the data enrichment value of these reservations within the SiteMinder Ecosystem.

Other elements and attributes in XML samples have been omitted for brevity

POS Reservation Header

For all reservation upload messages the RequestorID needs to be set to 10 to identify whether the requests are coming from a PMS.

Reservations/Modifications and Cancellations that originate from the PMS, we would expect BookingChannel @Type to be 4 and the CompanyName and Code to be populated with the PMS details.

<POS>
   <Source>
     <RequestorID Type="10" ID="PMS"/>
     <BookingChannel Primary="true" Type="4">
        <CompanyName Code="PMS">PMS</CompanyName>
     </BookingChannel>
   </Source>
</POS>

Walk-in Reservation

To represent a walk-in reservation in addition to the POS element as shown above, there are 2 key items to consider.

• WalkInIndicator attribute flag set to true on the HotelReservation element. This attribute is only required to be present to identify walk-in reservations.

• ResID_Type="14" to identify the ResID_Value is the reservation ID from your PMS

<OTA_HotelResNotifRQ>
  <HotelReservations>
    <HotelReservation ResStatus="Reserved" WalkInIndicator="true">
      <POS>
        <Source>
          <RequestorID Type="10" ID="PMS"/>
          <BookingChannel Primary="true" Type="4">
            <CompanyName Code="PMS">PMS</CompanyName>
          </BookingChannel>
        </Source>
      </POS>
      <RoomStays>...</RoomStays>
      <ResGlobalInfo>
        <HotelReservationIDs>
          <HotelReservationID ResID_Type="14" ResID_Value="123456789"/>
        </HotelReservationIDs>
      </ResGlobalInfo>
    </HotelReservation>
  </HotelReservations>
</OTA_HotelResNotifRQ>

Reservations from a Direct Booking Channel

These are reservations that originate from a direct booking channel directly connected to the PMS. As opposed to reservations sent by SiteMinder.

There are 2 sections that are key for these kinds of reservations.

The first is sending the booking channel information in the POS reservation header. In this case, we would expect BookingChannel @Type to be 7 and the CompanyName and Code to be populated with details of that channel.

If the booking channel is one that is connected to SiteMinder, please use the SiteMinder booking agent code. The full list can be found on this page Booking Agent Codes (OTAs)

For more information about the different Booking Channel Types, you can refer to the OpenTravel Code List (Booking Channel Types)

<POS>
  <Source>
    <RequestorID Type="10" ID="PMS"/>
    <BookingChannel Primary="true" Type="7">
      <CompanyName Code="DBT">Direct Booking Tool</CompanyName>
    </BookingChannel>
  </Source>
</POS>

We also require two types of reservation IDs.

• ResID_Type ="14" to identify the ResID_Value is the reservation ID from your PMS

• ResID_Type ="29" to identify the ResID_Value is the reservation ID from the Booking Channel

• For more information about the different ResID_Type Codes, you can refer to OpenTravel Code List (Unique ID Types).

<OTA_HotelResNotifRQ>
  <HotelReservations>
    <HotelReservation ResStatus="Reserved">
      <POS>
        <Source>
          <RequestorID Type="10" ID="PMS"/>
          <BookingChannel Primary="true" Type="7">
            <CompanyName Code="DBT">Direct Booking Tool</CompanyName>
          </BookingChannel>
        </Source>
      </POS>
      <RoomStays>...</RoomStays>
      <ResGlobalInfo>
        <HotelReservationIDs>
          <HotelReservationID ResID_Type="14" ResID_Value="123456789"/>
          <HotelReservationID ResID_Type="29" ResID_Value="987654321"/>
        </HotelReservationIDs>
      </ResGlobalInfo>
    </HotelReservation>
  </HotelReservations>
</OTA_HotelResNotifRQ>

Reservations from a CRS, GDS or Wholesaler

These are reservations that have a secondary source. They would follow the same makeup as Reservations from a Direct Booking Channelbut they would have a secondary source element in the POS.

The Primary BookingChannel element would have the @Type of 5 to identify that it is from the CRS.

For more information about the different Booking Channel Types, you can refer to the OpenTravel Code List (Booking Channel Types)

The second Source element would contain the details of the booking agent channel the reservation was originally made.

<POS>
    <Source>
        <RequestorID Type="10" ID="PMS"/>
        <BookingChannel Primary="true" Type="5">
            <CompanyName Code="CRS">Central Reservation System</CompanyName>
        </BookingChannel>
    </Source>
    <Source>
        <BookingChannel Primary="false" Type="7">
            <CompanyName Code="BAC">Booking Agent Channel</CompanyName>
        </BookingChannel>
    </Source>
</POS> 

Modification or Cancellation of a reservation originally delivered to the PMS via SiteMinder

In this case, we use 2 types of reservation ID

• ResID_Type ="14" to identify the ResID_Value is the reservation ID from your PMS

• ResID_Type ="25" to identify the ResID_Value is the reservation ID from SiteMinder

For more information about the different ResID_Type Codes, you can refer to OpenTravel Code List (Unique ID Types).

<OTA_HotelResNotifRQ>
  <HotelReservations>
    <HotelReservation ResStatus="Cancelled">
      <POS>
        <Source>
          <RequestorID Type="10" ID="PMS"/>
           <BookingChannel Primary="true" Type="4">
              <CompanyName Code="PMS">PMS</CompanyName>
           </BookingChannel>
        </Source>
      </POS>
      <RoomStays>...</RoomStays>
      <ResGlobalInfo>
        <HotelReservationIDs>
           <HotelReservationID ResID_Type="14" ResID_Value="123456789"/>
	   <HotelReservationID ResID_Type="25" ResID_Value="BDC-123456789"/>
	 </HotelReservationIDs>
      </ResGlobalInfo>
    </HotelReservation>
  </HotelReservations>
</OTA_HotelResNotifRQ>