Southwest Requirements
For customers that choose to use Southwest content via Universal API.
Note: As of Jun 2016, the PTC NRF has been decommissioned by Southwest. It is no longer supported by the supplier and could lead to issues if used in the workflow.
Request
Session Context
- Valid IATA # needed to be passed in the session context.
Passenger Middle Name
With Universal v42.0 and earlier, Universal API did not pass the middle name for passengers booked on Southwest via ACH. With Universal 43.0 and later, Universal API uses the protocol that identifies a Middle Name separated from the First Name by a space. Release 17.4
Note: If the first name has a space, then the second part of the first name will be considered the middle name. For example:
<com:BookingTravelerName
Prefix="Mr" First="Jean Marie" Middle="Marc Henri" Last="Singh"/>
First Name - Jean Marie
Middle Name - Marc
Last Name - Singh
<PersonName>
<NamePrefix>Mr</NamePrefix>
<GivenName>JeanMarie MarcHenri</GivenName>
<Surname>Singh</Surname>
</PersonName>
Phone Numbers
Southwest allows a phone number to be sent in the BookingTraveler element while booking. Southwest only supports one phone field per passenger. If users send in multiple phone fields, only the first one will be sent in. Valid phone fields supported by Southwest are:
| Type | Code |
|---|---|
| Home | HOM |
| Business | BUS |
| Fax | FAX |
| Mobile | CELL |
Following is an example of how this might be passed in the BookingTraveler element in Universal API:
<com:PhoneNumber Key="12345" Location="DEN" Number="3033333" CountryCode="001" AreaCode="301" Type="Home"/>
Southwest implements additional validations for phone numbers depending on whether they are domestic US or international phone numbers:
- International Phone numbers are identified using the attribute @CountryCode with a value other than 001. If the PhoneNumber element does not have this field, it is considered a domestic telephone number:
- @AreaCode is supported but optional for international phone numbers
- @Number must be at least 5 digits, and special characters are not supported
- For phone numbers in the North American Numbering Plan (NANP) area:
- @AreaCode is required for domestic phone numbers and must be 3 digits
- @Number must be exactly 7 digits. Currently Special character hyphen (-) is not currently supported
Note: Phone number of the Booking Traveler used in the Air Create Reservation Request should only be 7 digits when US is the selected country.
Holding Reservations
- Perform a UR modify to add the form of payment.
UniversalRecordModifyReq/UniversalModifyCmd/AirUpdate/AirPricingPayment/FormOfPayment
- Once the booking is modified to include the form of payment, the reservation is ticketed. When it is retrieved, the Ticketless Carrier Record (TCR) returns in the document information attribute:
AirCreateReservationRsp/universal:UniversalRecord/air:AirReservation/air:DocumentInfo/air:TCRInfo/@TCRNumber