Release Notes 25.3

Schema Version and Retirement

The latest schema, version 54.0, released with Universal API 25.2.

Important!

Effective January 23, 2025, the Travelport Universal API schema retirement process is being put on hold temporarily. See the Schema Retirement page for further details.

Functional Updates

N indicates content for the upcoming or recent releases.

Update Provider Detailed Description Associated Transactions Schema Change Schema Location/XPATH
Defect Fixes

  • DA 1080 Defect Fixes for Release 25.3.1

  • DA 1085 Defect Fixes for Release 25.3.2

      
Universal API Release 25.3.2

Default Setting Change when AirPrice Includes Fare Basis Code.

 1G

The rules validation default setting is being changed when an AirPrice request including a fare basis code is sent. By validating the rules of the fare when a fare basis code is included in the AirPrice request, users can expect the fare in the AirPrice response to be applicable to the input criteria. This will be enabled after August 21, 2025.

For example, when sending an AirPrice request that includes a FareBasis code but no FareRuleValidation indicator is included, the system defaults to validating the rules of the fare and fails with NO VALID FARE FOR INPUT CRITERIA, because, for example, the fare is not valid for the flight, date or booking code in the request.

See DA-1081 for further information.

Air Pricing No

Air.xsd

AirPriceReq/FareRuleValidation="true" or "false"

Support quantity for C type bags sold by weight.

 1G

This enhancement provides the ability to book multiple quantities of extra bags when they can be sold by weight. In AirMerchandisingFulfillment, when booking C type extra bags that are sold by weight, if the quantity field is set to more than 1, then Universal API calculates the total weight amount and adds the SSR according to the total weight entered based on the carrier filing.

 

Air Merchandising Fulfillment

Air Booking

No

Air.xsd

AirCreateReservationRsp/UniversalRecord/AirReservation/OptionalServices/OptionalService

@SSRFreeText
Universal API Release 25.3.1

Segment Status Change for NDC Bookings Retrieved via SOAP XML API Services.

 1G

Universal API (SOAP XML API Services) can retrieve NDC bookings with segments containing both ZK and HK status.

Notes:

  • Users who want to retrieve NDC bookings with ZK or HK status returned on NDC segments should reach out to their Travelport Account Representative and Opt-In for NDC bookings.

  • If a booking has NDC segments, the warning: "PNR has NDC segments - <seg list>. Modifications are restricted on this PNR." E.g., <common_v53_0:ResponseMessage Code="101018" Type="Warning">PNR has NDC segment(s) QF|403,QF|402,QF|401,QF|402. NDC segment(s) cannot be modified or cancelled using UAPI.</common_v53_0:ResponseMessage>

  • An error message returns from a PNR Modify attempt, "<faultstring>PNR has NDC segment(s) AA|2364. NDC segment(s) cannot be modified or cancelled using UAPI.</faultstring>:

  • See DA-1065 for more details.

UR Retrieve

UR Modify

No

UniversalRecord.xsd

  • UniversalRecordRetrieveRsp

  • UniversalRecordModifyRsp