Passenger Details

3.5.0
Air
Reservation
SOAP API
Travel Agency
Airline Carrier

v3.5.0 | October 1, 2022

  • (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.
Read more

API Information

Response Format
XML
Service Action Code
PassengerDetailsRQ
Current Version
3.5.0
Target Audience
Both TN and AS
Environment
Production

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.

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.

Functional Updates And Enhancements

In the Request

Optional

Parameter: FOP_Remark

Type: element

Description: Used to pass form of payment information to be stored in the new *FOP PNR field

Sample Value:

...
<SpecialReqDetails>
<AddRemarkRQ>
<RemarkInfo>
<FOP_Remark>
<CC_Info>
<PaymentCard AirlineCode="YY" CardSecurityCode="123" Code="VI" ExpireDate="2025-12" ExtendedPayment="12" ManualApprovalCode="123456" Number="4123412341234123"/>
</CC_Info>
</FOP_Remark>
</RemarkInfo>
</AddRemarkRQ>
</SpecialReqDetails>
...
Note: Previously the element could not be repeated. Currently, up to 10 different forms of payment can be stored.

Relase note ID: 17580

v3.4.0 | September 23, 2021

  • 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.
Read more

API Information

Response Format
XML
Service Action Code
PassengerDetailsRQ
Current Version
3.4.0
Target Audience
Both TN and AS
Environment
Production

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.

Resolved Issues

In the Response

N/A

(04/28/2022) The API will now recover from error "UNABLE TO PROCESS AT THIS TIME - PLEASE RETRY". This may occur during addition of itinerary remarks. When this happens, the API attempt to retry the remark adding process after a delay.

Relase note ID: 15764