UpdatePassengerNameRecordRQ
UpdatePassengerNameRecordRQ
Update Passenger Name Record - REST
Update Passenger Name Record - SOAP
UpdatePassengerNameRecordRQ allows client applications to:
- Simplify the process of updating a Passenger Name Record (PNR) in a single API call (removes the need to use an individual/granular API)
- Update reservations in a stateless way
- Update reservation via session-based (ATH) or session-less (ATK) tokens
- Define the API behavior when encountering the most common errors at time of booking. For example, halt the modification of a reservation if an error is returned during a price check, or retry the booking to the next available class of service if the initial booking attempt fails.
- Specify a different target city (PCC) for the modification of a PNR
UpdatePassengerNameRecordRQ performs different steps based on the provided criteria. This is managed by orchestrating different calls to specific APIs:
- Adds general passenger and details (names, contact details, etc.)
- Performs air booking and pricing
- Performs hotel booking via a booking key
- Adds miscellaneous segment information, special service details (SSRs, Remarks, TSA-related details, etc.)
- Adds seats for air bookings
- Finalizes the transaction (commits the changes)
General guidelines related to update operations
- To ensure the successful execution of this API, the request should specify a valid PNR record locator at:
/Itinerary/@id
. - If you plan to provide agency and/or traveler information, a miscellaneous segment or special request details in a reservation, your request should contain
../PostProcessing/EndTransaction
in order to commit the changes. -
Additionally, if you plan to add air segments to a reservation that did not previously contain air segments, the request should contain the below information:
- Ticketing time limit:
/TravelItineraryAddInfo/AgencyInfo/Ticketing/@TicketType
- Details of the air segments to be booked:
/AirBook/OriginDestinationInformation/FlightSegment
- Request to price the successfully booked segments:
/AirPrice/PriceRequestInformation
- Request to commit the transaction:
/PostProcessing/EndTransaction
/PostProcessing/EndTransaction/Source/@ReceivedFrom
- For reservations departing to/from the US, or flying over the US, it is mandatory to pass Secure Flight Passenger Data (required by TSA):
/CreatePassengerNameRecordRQ/SpecialReqDetails/SpecialService/SpecialServiceInfo/SecureFlight
- If you plan to add hotel segments to a reservation that did not previously contain hotel segments, the request should contain the below information:
- Travel agency address:
/TravelItineraryAddInfo/AgencyInfo/Address
- Hotel booking key:
/HotelBook/BookingInfo/BookingKey
- Request to commit the transaction:
/PostProcessing/EndTransaction
and/PostProcessing/EndTransaction/Source/@ReceivedFrom
- Ticketing time limit: