API Information

What's New

• (04/04/2023) 3.4.0 and 3.5.0 - From now on the API will trim leading "+" character from the telephone numbers sent at .../TravelItineraryAddInfoRQ/CustomerInfo/ContactNumbers/ContactNumber/@Phonenumber. - Previously, such requests generated an error message ".FRMT.NOT ENT BGNG WITH" from downline systems.
• (04/04/2023) - Fixed an issue where the addition of payment card information (.../SpecialReqDetails/AddRemarkRQ/RemarkInfo/FOP_Remark) without manual approval code caused API failures.
• (04/04/2023) - Modified repeat factor at ...PostProcessing/QueuePlace/QueueInfo/QueueIdentifier from 3 to 10. This allows sending a PNR to up to 10 PNR queues.
• (05/30/2023) [Part 1] Added capability to associate form of payment with its specific use type.
• (05/30/2023) [Part 2] Added new request schema element /PassengerDetailsRQ/SpecialReqDetails/AddRemarkRQ/RemarkInfo/FOP_Remark_Association to pass all supported use types (allowed values are "AZ" - All, "AN" - Ancillary, "AL" - Airline, "BU" - Bus/Ground Transportation, "CR" - Car, "CS" - Cruise, "HL" - Hotel, "IN" - Insurance, "LC" - Low-Cost Carrier, "OT" - Other, "RL" - Rail, "SS" - Specialty Service, "TR" - Tour, "IR" - Interface Record).
• (05/30/2023) [Part 3] You can either associate existing forms of payment or add new ones together with association.
• (09/12/2023) The API will now return the following error message when multiple FOP Remarks are sent in a single FOP_Remark node at /PassengerDetailsRQ/SpecialReqDetails/AddRemarkRQ/RemarkInfo/FOP_Remark: "Only one form of payment can be used in a single FOP_Remark, "Check", "Cash", "PaymentCard" are mutually exclusive."
• (10/31/2023) Starting from this release, the API will validate mutually exclusive form of payment remark combinations. When /PassengerDetailsRQ/SpecialReqDetails/AddRemarkRQ/RemarkInfo/FOP_Remark/@Type is sent, it cannot be combined with ../FOP_Remark/CC_Info, if You wish for these two payment types to be saved in the reservation, You need to send them as two different form of payment remarks
• (10/31/2023) Starting from this release you can associate card holder information to newly added form of payment at .../SpecialReqDetails/AddRemarkRQ/RemarkInfo/FOP_Remark/CC_Info/CardHolderName
• (11/30/2023) Added capability initiate ticketing approval request for new Form of Payment remarks at .../SpecialReqDetails/AddRemarkRQ/RemarkInfo/FOP_Remark/CC_Info/PaymentCard/@GenerateApprovalAtTicketing. Please note, that if you expect the "*" character visible in front of your PNR Form Of Payment Field, then consider this attribute as mandatory
• (02/27/2024) Added capability to associate form of payment with its specific trip type. Please check design documentation or help guide on the API page for more information.
• (02/27/2024) Added capability to pass additional form of payment types: agency invoice and non-refundable cash/check.

Business Value

• As per Sabre Advance Notification (SAN) 16643, in 1Q 2025 Sabre is retiring the ‘5-‘ form of payment remarks PNR field. This has been the traditional method of adding and storing form of payment information (supported in PassengerDetailsRQv3.4.0). To prepare customers for the change the new version introduces support of the updated method of adding form of payment data. In order to take advantage of this capability you can self-activate it by enabling PNAPNR TJR setting on your PCC level.

API Information

What's New

• Modified .../RemarkInfo/Remark to unbounded. - This allows for more than 98 remarks in a single PassengerDetailsRQ call. This is an update to existing service version 3.4.0.
• 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. This is an update to existing service version 3.4.0.
• Modified the limit for splitting Add Remark requests - Abacus remark limit is 779 characters, INFINI is 799 so we lowered the limit to 750 characters. The logic is still approximate but this functionality will now serve a broader base of customers. This is an update to existing service version 3.4.0.
• (10/18/2021) Integrated the latest version of TravelItineraryAddInfoLLSRQv2.2.1 - With this change the response for addition of Address lines on airline Partitions will be interpreted as successful.
• (10/28/2021) The API will return Strong Customer Authentication information saved in sessions and reservations when re-displaying the reservation at /PassengerDetailsRS/TravelItineraryReadRS/TravelItinerary/OpenReservationElements/OpenReservationElement/FormOfPayment/PaymentCard/StrongCustomerAuthentication
• (12/09/2021) Added capability to pass Visa special service document expiration date at .../SpecialReqDetails/SpecialServiceRQ/SpecialServiceInfo/AdvancePassenger/Document/Visa/@ExpirationDate
• (02/14/2023) Added capability to pass Secure Flight document information (SFPD) for infants not occupying a seat (lap infant). The following was added to the request schema: /PassengerDetailsRQ/SpecialReqDetails/SpecialServiceRQ/SpecialServiceInfo/SecureFlight/PersonName/@LapChild
• (04/04/2023) 3.4.0 and 3.5.0 - From now on the API will trim leading "+" character from the telephone numbers sent at .../TravelItineraryAddInfoRQ/CustomerInfo/ContactNumbers/ContactNumber/@Phonenumber. - Previously, such requests generated an error message ".FRMT.NOT ENT BGNG WITH" from downline systems.
• (04/04/2023) - Fixed an issue where the addition of payment card information (.../SpecialReqDetails/AddRemarkRQ/RemarkInfo/FOP_Remark) without manual approval code caused API failures.