Why are we sunsetting older versions?

All CreatePassengerNameRecordRQ versions older than v2.1.0 use internal calls to TravelItineraryReadRQ (TIR) to redisplay reservation post booking. Mentioned TravelItineraryReadRQ is planned to be sunset in 1Q 2022, therefore CreatePassengerNameRecordRQ versions older than v2.1.0 must be sunset before that time. Versions 2.2.0 and 2.3.0 will be still supported and are not planned to be sunset in the short term, nevertheless this migration guide describes how to migrate to newest version of CreatePassengerNameRecordRQ.
Sunsetting TravelItineraryReadRQ is part of Sabre Technical Transformation and migration to Cloud based data centers.

What's new?

In CreatePassengerNameRecordRQ v2.4.0 we included (SOAP release notes, REST release notes):

• Added capability to book CSL/legacy hotel content (HotelBook element/object)
• Added capability to book vehicle content (VehicleBook element/object)
• Added capability to validate whether the minimum connecting time between newly booked air segments is met.