Why are we sunsetting older versions?

All PassengerDetailsRQ versions older than v3.4.0 use internal calls to TravelItineraryReadRQ (TIR) to redisplay reservation post booking. Mentioned TravelItineraryReadRQ is planned to be sunset in 1Q 2022, therefore PassengerDetailsRQ versions older than v3.4.0 must be sunset before that time.

Sunsetting TravelItineraryReadRQ is part of Sabre Technical Transformation and migration to Cloud based data centers.

What's new?

In PassangerDetailsRQ v3.4.0 we included:

• Modified .../RemarkInfo/Remark to unbounded. - This allows for more than 98 remarks in a single PassengerDetailsRQ call.
• Added an additional TravelItineraryAddInfoLLSRQ call for Corporate ID - From now on /PassengerDetailsRQ/TravelItineraryAddInfoRQ/CustomerInfo/Corporate can be combined with other qualifiers, because the ID will be sent in the initial TravelItineraryAddInfoLLSRQ call, before adding other information to the session state.