Sessions: Add Booking Traveler
SharedBookingReqRsp.xsd
Session > Booking Start > Add Booking Traveller
The Booking Traveler Add request enables the addition of Booking Traveler names and related data (including address, email, frequest flyer numbers, etc.). The Session Token is passed by the Universal API Customer in the header and body of the request.
- Booking Traveler name is added similarly to unsessioned Universal API.
- Restrictions for the booking traveler names are applied.
Samples
See the samples associated with Add Booking Traveler:
Schema
See the Booking Traveler Add transactions:
Request
When adding an Booking Traveler in a sessioned state, the element and attribute structure is similar to the request in a standard Air Booking or Modify request, except that a session must have been established (Booking Start), and a session key must be sent in the header and body of the request.
In the header and the body, the session key (SessTok and SessionKey) must be included:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:shar="http://www.travelport.com/schema/sharedBooking_v34_0" xmlns:com="http://www.travelport.com/schema/common_v34_0">
<soapenv:Header>
<h:SessionContext xmlns:h="http://www.travelport.com/soa/common/security/SessionContext_v1" xmlns="http://www.travelport.com/soa/common/security/SessionContext_v1">
<SessTok id="4a5fa17b-3cd0-46f4-b33f-af4d24a541c2"/>
</h:SessionContext>
</soapenv:Header>
<soapenv:Body>
<shar:BookingTravelerReq TraceId="357476620" AuthorizedBy="TVPT" SessionKey="4a5fa17b-3cd0-46f4-b33f-af4d24a541c2">
<com:BillingPointOfSaleInfo OriginApplication="UAPI"/>
<shar:AddTraveler>
<com:BookingTraveler Key="de45QF6QQcmduLgVQWr+VQ==" TravelerType="ADT" Age="51" DOB="1964-10-10" Gender="F">
...
The Add Traveler request is similar to what is sent in a standard Air Create Reservation request. For more information see Booking Traveler Information).
Optional Request Data
Optional data can be added to further refine the request.
Response
The Booking Traveler Response returns a universal record structure with all details for the current state of the session.
SessionBooking v53.xsd expands on the existing Routehappy flight amenity content returned in the AirCreateReservation, UniversalRecordRetrieve, and the Session Booking transactions BookingPricing, BookingTraveler, and BookingEnd, by extending the data to each leg of a direct flight. U
Note: This is limited release functionality. Contact your Travelport representative for further information.
Exceptions
The exceptions for Booking Air Traveler is the same as can be found in Air Create or Air Modify. There are no known exceptions specific to the Booking Air Traveler transaction.