Table of Contents

Sailing Availability

First step is a search for available sailing packages using the CruiseSailAvailRQ/RS message pair. The SwOta will reply with a list of available sailings or a warning to inform the requester that no sailings are available that satisfy the request.

Request Example

Below is a sample request for sailing availability within a set period of voyage dates:

POST https://bookings-stage.sw.travelhx.com/ota/rest/OTA_CruiseSailAvailRQ
Content-Type: application/xml
<OTA_CruiseSailAvailRQ Version="1" xmlns="http://www.opentravel.org/OTA/2003/05">
    <POS>
        [..]
    </POS>
    <SailingDateRange>
        <StartDateWindow EarliestDate="2015-12-01"/>
        <EndDateWindow LatestDate="2015-12-31"/>
    </SailingDateRange>
</OTA_CruiseSailAvailRQ>

Response Example

As a result a list of SailingOption is returned, each corresponding to a Seaware sailing package that is available for the agency and the search criteria specified in the request:

<OTA_CruiseSailAvailRS TimeStamp="2015-08-26T19:23:11.973-07:00" Version="1" xmlns="http://www.opentravel.org/OTA/2003/05">
    <Success/>
    <SailingOptions>
        <SailingOption>
            <SelectedSailing VoyageID="101505" Status="36" PortsOfCallQuantity="11"
                Start="2015-08-20" End="2015-08-30">
                <CruiseLine VendorCode="QQ CRUISE" ShipCode="QS" ShipName="QQ Ship"/>
                <DeparturePort EmbarkationTime="2015-08-20T21:00:00.000-07:00" 
                    LocationCode="PTL"/>
                <ArrivalPort DebarkationDateTime="2015-08-30T06:00:00.000-07:00"
                    LocationCode="ITCVV"/>
            </SelectedSailing>
            <Information>
                <Text>Summer QQ cruise "Artists &amp; Explorers" 10 nights</Text>
            </Information>
        </SailingOption>
        […]
    </SailingOptions>
</OTA_CruiseSailAvailRS>

Including Waitlisted Sailings

By default a sailing availability search only returns inventory that is available (OK) or sold on guarantee (GTY). Waitlisted sailings are omitted. To get them back, list the statuses you want in SearchQualifiers/Status/@Status inside CruiseLinePrefs/CruiseLinePref:

<OTA_CruiseSailAvailRQ Version="1.0" xmlns="http://www.opentravel.org/OTA/2003/05">
    <POS>
        <Source ISOCurrency="GBP">
            <RequestorID Type="5" ID_Context="SEAWARE" ID="242730"/>
            <BookingChannel Type="1">
                <CompanyName>DIRECT-AGENCY</CompanyName>
            </BookingChannel>
        </Source>
    </POS>
    <SailingDateRange>
        <StartDateWindow EarliestDate="2027-08-01"/>
        <EndDateWindow LatestDate="2027-09-30"/>
    </SailingDateRange>
    <CruiseLinePrefs>
        <CruiseLinePref>
            <SearchQualifiers>
                <Status Status="38"/>
                <Status Status="46"/>
                <Status Status="47"/>
            </SearchQualifiers>
        </CruiseLinePref>
    </CruiseLinePrefs>
</OTA_CruiseSailAvailRQ>

The statuses you list replace the default OK/GTY filter, so the search returns exactly the kinds of inventory you ask for — <Status Status="46"/> on its own returns waitlisted sailings only.

Status Meaning Seaware inventory result Seaware availability mode
36 Available OK OK
38 Closed NO ALL
46 Waitlisted WTL WTL
47 Guaranteed GTY GTY

Status 38 maps to the Seaware ALL availability mode, which opens the search to every kind of inventory. That is why the request above returns everything — available, guarantee and waitlisted sailings alike — and why 38/46/47 is the combination to use when you want waitlisted voyages shown alongside normal availability.

Each returned SelectedSailing reports its own status in the Status attribute, so you can tell waitlisted sailings apart from bookable ones. See OTA Code Lists for the full status list and SwOTA Shopping for further examples. The same qualifiers apply to Category Availability.

Cached Sailing Availability

For improved performance, you can request cached availability data using:

<TPA_Extensions UseCacheInd="true"/>
Note

Cached results provide faster response times but may not reflect real-time inventory changes. Use cached mode for browsing/searching, and non-cached mode when ready to book. This feature requires cache configuration in Seaware. Check with your integration team about cache refresh frequency and availability.

SOAP endpoint: https://staging.bookings.travelhx.com:8082/ota/ws