RatePlanToken Search RQ

The Search functionality for our RatePlanToken product is directly based on our original OTA_HotelAvailRQ/RS. The request message is essentially the same.

Purpose

This message is used to:

Search for available hotel rooms based on specific criteria.
Request rate information for available accommodations.
Query inventory across multiple properties or a single hotel.
Filter results based on guest requirements and preferences.
Retrieve both pre-aggregated hotel contracts and real-time market access.

Details and Structure

All the details regarding this message can be found at OTA_HotelAvailRQ. This message works exactly the same. The RatePlanToken room stays will be returned with a RatePlanToken in the search RS, which will be needed at the booking step.

Differences with classic Hotel Search

The structure of the message is exactly the same, but the available optional features are less for these searches.

What’s not included

Multi-Room logic is not yet available for RP Token Search.
Searching by Hotel Name is not available.
Enrichment via InfoSource. Every response will be displayed as per InfoSource = 0.
Area Search is not supported.
CalendarView Search is not supported.
Upfront Filtering is not supported.
Search by Location is still not available.

Complete Examples

<OTA_HotelAvailRQ MaxResponses="200" EchoToken="4144d7ff-9ae4-46b2-90a2-a85856b5d65f" Version="2008.1" PrimaryLangID="EN"
    xmlns="http://www.opentravel.org/OTA/2003/05">
    <POS>
        <Source>
            <RequestorID Instance="MF001" ID="TEST" Type="22"/>
        </Source>
        <Source>
            <RequestorID ID="TEST" Type="88"/>
        </Source>
    </POS>
    <AvailRequestSegments>
        <AvailRequestSegment InfoSource="14">
            <StayDateRange Start="2027-07-17" End="2027-07-24"/>
            <RoomStayCandidates>
                <RoomStayCandidate RPH="0">
                    <GuestCounts>
                        <GuestCount Age="30" Count="1" AgeQualifyingCode="10"/>
                        <GuestCount Age="30" Count="1" AgeQualifyingCode="10"/>
                    </GuestCounts>
                </RoomStayCandidate>
            </RoomStayCandidates>
            <HotelSearchCriteria>
                <Criterion ExactMatch="true">
                    <HotelRef HotelCode="AESPMI5L46"/>
                </Criterion>
            </HotelSearchCriteria>
        </AvailRequestSegment>
    </AvailRequestSegments>
</OTA_HotelAvailRQ>

<OTA_HotelAvailRQ xmlns="http://www.opentravel.org/OTA/2003/05" MaxResponses="200" Version="2008.1">
  <POS>
    <Source>
      <RequestorID Instance="MF005" ID_Context="AxisData" ID="TEST" Type="22"/>
    </Source>
    <Source>
      <RequestorID Type="88" ID="TEST"/>
    </Source>
  </POS>
  <AvailRequestSegments>
    <AvailRequestSegment InfoSource="12">
      <StayDateRange End="2027-07-24" Start="2027-07-17"/>
      <RoomStayCandidates>
        <RoomStayCandidate>
          <GuestCounts>
            <GuestCount Age="30" Count="2" AgeQualifyingCode="10"/>
          </GuestCounts>
        </RoomStayCandidate>
      </RoomStayCandidates>
      <HotelSearchCriteria>
        <Criterion ExactMatch="true">
          <HotelRef HotelCode="AESPMI5L46"/>
        </Criterion>
      </HotelSearchCriteria>
    </AvailRequestSegment>
    <AvailRequestSegment InfoSource="12">
      <StayDateRange End="2027-07-24" Start="2027-07-17"/>
      <RoomStayCandidates>
        <RoomStayCandidate>
          <GuestCounts>
            <GuestCount Age="30" Count="2" AgeQualifyingCode="10"/>
          </GuestCounts>
        </RoomStayCandidate>
      </RoomStayCandidates>
      <HotelSearchCriteria>
        <Criterion ExactMatch="true">
          <HotelRef HotelCode="AESPMI1234"/>
        </Criterion>
      </HotelSearchCriteria>
    </AvailRequestSegment>
    <AvailRequestSegment InfoSource="12">
      <StayDateRange End="2027-07-24" Start="2027-07-17"/>
      <RoomStayCandidates>
        <RoomStayCandidate>
          <GuestCounts>
            <GuestCount Age="30" Count="2" AgeQualifyingCode="10"/>
          </GuestCounts>
        </RoomStayCandidate>
      </RoomStayCandidates>
      <HotelSearchCriteria>
        <Criterion ExactMatch="true">
          <HotelRef HotelCode="AESPMI5678"/>
        </Criterion>
      </HotelSearchCriteria>
    </AvailRequestSegment>
  </AvailRequestSegments>
</OTA_HotelAvailRQ>

<OTA_HotelAvailRQ xmlns="http://www.opentravel.org/OTA/2003/05" MaxResponses="200" Version="2008.1">
  <POS>
    <Source>
      <RequestorID Instance="MF002" ID_Context="AxisData" ID="TEST" Type="22"/>
    </Source>
    <Source>
      <RequestorID Type="88" ID="TEST"/>
    </Source>
  </POS>
  <AvailRequestSegments>
    <AvailRequestSegment InfoSource="12">
      <StayDateRange End="2027-07-24" Start="2027-07-17"/>
      <RoomStayCandidates>
        <RoomStayCandidate>
          <GuestCounts>
            <GuestCount Age="30" Count="2" AgeQualifyingCode="10"/>
		  </GuestCounts>
        </RoomStayCandidate>
      </RoomStayCandidates>
      <HotelSearchCriteria>
        <Criterion ExactMatch="true">
          <HotelRef HotelCode="AMTSTR1UQ4"/>
          <HotelRef HotelCode="AMTSTR139E"/>
          <HotelRef HotelCode="AMTSTR13D0"/>
        </Criterion>
      </HotelSearchCriteria>
    </AvailRequestSegment>
  </AvailRequestSegments>
</OTA_HotelAvailRQ>

Getting started

Authentication

Accommodation

Transfer

Excursion & Activities

Other Products

Booking management

General Concepts

Glossary

Push Model

Purpose

Details and Structure

Differences with classic Hotel Search

What’s not included

Complete Examples

​Purpose

​Details and Structure

​Differences with classic Hotel Search

​What’s not included

​Complete Examples

Purpose

Details and Structure

Differences with classic Hotel Search

What’s not included

Complete Examples