SwOTA SOAP Testing Guide

Quick Setup for SOAP Testing with SSL Client Certificates

1. Certificate Configuration

Before testing, you must install your SSL client certificate in Postman:

Go to Postman Settings & Certificates
Click Add Certificate
Configure:
- Host: dev.bookings.travelhx.com:8082
- CRT file: Your client certificate (.crt or .pem)
- KEY file: Your private key (.key)

2. Import Environment

Create a Postman environment with these variables:

{
  "name": "SwOTA Development",
  "values": [
    {
      "key": "soap_url",
      "value": "https://dev.bookings.travelhx.com:8082/ota/ws",
      "enabled": true
    },
    {
      "key": "agency_id", 
      "value": "YOUR_AGENCY_ID",
      "enabled": true
    },
    {
      "key": "booking_source",
      "value": "OPENTRAVEL", 
      "enabled": true
    }
  ]
}

3. SOAP Request Headers

All SOAP requests should include:

Content-Type: text/xml; charset=utf-8
SOAPAction: (leave empty)

4. Sample SOAP Requests

Ping Test

POST {{soap_url}}
<?xml version="1.0" encoding="UTF-8"?>
<Envelope xmlns="http://schemas.xmlsoap.org/soap/envelope/">
<Header/>
<Body>
<OTA_PingRQ xmlns="http://www.opentravel.org/OTA/2003/05" Version="1.0" TimeStamp="2025-01-01T12:00:00Z">
<EchoData>Test connection</EchoData>
</OTA_PingRQ>
</Body>
</Envelope>

Sailing Availability

POST {{soap_url}}
<?xml version="1.0" encoding="UTF-8"?>
<Envelope xmlns="http://schemas.xmlsoap.org/soap/envelope/">
<Header/>
<Body>
<OTA_CruiseSailAvailRQ xmlns="http://www.opentravel.org/OTA/2003/05" Version="1.0" TimeStamp="2025-01-01T12:00:00Z">
<POS>
<Source>
<RequestorID ID="{{agency_id}}" Type="5" ID_Context="SEAWARE"/>
<BookingChannel Type="1">
<CompanyName>{{booking_source}}</CompanyName>
</BookingChannel>
</Source>
</POS>
<SailingDateRange>
<StartDateWindow EarliestDate="2025-06-01"/>
<EndDateWindow LatestDate="2025-12-31"/>
</SailingDateRange>
</OTA_CruiseSailAvailRQ>
</Body>
</Envelope>

5. Certificate Verification

If certificate is properly configured, you should see:

SSL Handshake: Completed successfully in Postman console
Connection: No certificate-related errors

6. Expected Responses

Ping: with echo data wrapped in SOAP response
Availability: Error Code 168 (expected if used with test credentials - confirms format is correct)

Table of Contents