API Information

What's New

• (07/13/2023) We have migrated the addition of form of payment information from legacy AddRemarkLLSRQ (capable of passing "5-" remarks only) to UpdateReservationRQ (capable of passing remarks to be stored in the modern "FOP" PNR field).
• (07/13/2023) Starting with this release, the API will let you override the default logic of halting upon encountering "NN" flight status code during booking. A number of low cost airlines (LCC) return "NN" code as a default/successful status that gets finally confirmed after ticket issuance. With this change, you can simply specify "None" at ...AirBook/HaltOnStatus/@Code which will disable the default "NN" check.
• (10/31/2023) Starting with this release, when customers specify PostProcessing/ARUNK/@keepSegments="true" the API will now adjust segment specific seat assignment requests based on the ARNK segments present in the itinerary.
• (10/31/2023) Starting with this release, you can pass tokenized card number during vehicle booking. Previously, the API only allowed digits in case of passing a credit card form of payment.
• (11/30/2023) Added capability to pass payment card holder name as well as ticketing approval request for new Form of Payment remarks. The new values are located at .../SpecialReqDetails/AddRemark/RemarkInfo/FOP_Remark/CC_Info/PaymentCard and .../FOP_Remark/CC_Info/CardHolderName
• (10/31/2023) The change introduces a new @legacyIURforCSL flag that will let you request legacy Interface User Record (IUR) to be created while booking CSL or aggregator hotel segments.
• (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
• (11/30/2023) [Part 1] Added capability to associate form of payment with its specific use type.
• [Part 2] Added new request schema element /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).
• [Part 3] You can either associate existing forms of payment or add new ones together with association.
• (11/30/2023) The API will now return the following error message when multiple FOP Remarks are sent in a single FOP_Remark node at .../SpecialReqDetails/AddRemarkRQ/RemarkInfo/FOP_Remark: "Only one form of payment can be used in a single FOP_Remark, "Check", "Cash", "PaymentCard" are mutually exclusive."
• (11/30/2023) Starting from this release, the API will validate mutually exclusive form of payment remark combinations. When .../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.
• (11/30/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
• (01/30/2024) Corrected surface segment (ARUNK) logic that involves 'keepSegments' attribute/property. Previously, surface segments which were requested to be added at the end of business process got inserted prior pricing operation - This addresses [ASTSP-477].
• (02/27/2024) Added capability to associate form of payment with its specific trip type at .../SpecialReqDetails/AddRemark/RemarkInfo/FOP_Remark_Association/Child/@tripType
• (02/27/2024) Added capability to pass new form of payment types: agency invoice and non-refundable cash/check at .../SpecialReqDetails/AddRemark/RemarkInfo/FOP_Remark/@Type
• (03/18/2024) Added capability to specify wait interval before second and subsequent pricing operations at /CreatePassengerNameRecordRQ/PostProcessing/PricingInterval@waitInterval

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 version 2.4.0). To prepare customers for the change, this new API 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

• Added capability to make passive PNR bookings. This is particularly useful when the user wishes to create Sabre PNR for bookings made outside of Sabre GDS.
• Modified .../AddRemark/RemarkInfo/Remark to unbounded. - From now on our users can send more than 98 remarks in a single CreatePNR request.
• Added support for combining .../TravelItineraryAddInfo/CustomerInfo/Corporate/ID with other ../TravelItineraryAddInfoelements/attributes. Previously such combination was not allowed.
• Introduced PostProcessing/ARUNK/@keepSegments which , when combined with ARUNK/@priorPricing="true" and segment selection pricing, will accurately apply flight segment numbering. (ASTSP-416)
• (10/28/2021) Added capability to pass or reference Strong Customer Authentication (SCA) data during a hotel booking payment card transaction. A new element 'PaymentInformation/FormOfPayment/PaymentCard/StrongCustomerAuthentication' has been added to the request schema for that purpose.
• (12/09/2021) Added capability to pass Visa special service document expiration date at .../SpecialReqDetails/SpecialServiceRQ/SpecialServiceInfo/AdvancePassenger/Document/Visa/@ExpirationDate
• (08/30/2022) The API will now return the full state of the reservation upon encountering unwanted flight segment status. This will let us see the actual flight segment status returned by the airline (such as UC,LL,NO, etc). Please note that you still need to enable reservation redisplay at .../PostProcessing/RedisplayReservation.
• (10/04/2022) Modifed flight booking price comparison to accept "0" value types. - This addresses [ASTSP-440] and from now on the users can compare amounts, percentages and expected total fare values with zero. Please be aware, that percentages will be short-circuited when compared with zeroes to avoid dividing by zero.
• (01/31/2023) Introduced a sleep mechanism which allows more time for vehicle vendor (Dollar/Thrifty) to confirm a vehicle booking. Such a scenario can be identified by the vehicle vendor returning "WAITING FOR DC RESPONSE .... RETRY IN {n} SECONDS" message upon committing the reservation.
• (02/14/2023) Added capability for Abacus customers to book passive American Airlines segments (YK).
• (02/14/2023) Modified business logic for .../AirBookRQ/RetryRebook/@Option="true" - This was implemented in order to resolve [ASTSP-433] and let you retry the UC rebooking process in case of a failure. The following fields were added: ...AirBookRQ/RetryRebook/@NumAttempts and @WaitInterval.
• (02/14/2023) Introduced code validation to prevent combining .../AirPrice/PriceRequestInformation/@Retain="true" with .../PriceRequestInformation/OptionalQualifiers/MiscQualifiers/AirExtras/SSR_Code . This combination was never supported by the system and was causing API failures.
• (04/04/2023) Added capability to assign a Secure Flight Passenger Data (SFPD) document SSR to a lap child at /SpecialReqDetails/SpecialService/SpecialServiceInfo/SecureFlight/PersonName/@LapChild
• (04/04/2023) Fixed an issue where a combination of segment select pricing and addition of a surface segment (ARNK) could prevent from correct storing of a price quote. This addresses the request described under [ASTSP-453]
• (04/04/2023) Added capability to break API processing when the newly booked hotel segment does not return confirmation number. This is controlled by a new boolean attribute @haltWhenNoHotelCF, which, when set to true, will terminate the transaction once no confirmation number is present.
• (04/04/2023) From now on the API will trim leading "+" character from the telephone numbers sent at .../TravelItineraryAddInfo/CustomerInfo/ContactNumbers/ContactNumber/@Phonenumber. - Previously, such requests generated an error message ".FRMT.NOT ENT BGNG WITH" from downline systems.
• (05/30/2023) Starting with this release the API will attempt to apply brands selected by the user when rebooking flights with unconfirmed status codes by means of ...AirBook/RetryRebook/@Option="true".
• (10/31/2023) Starting with this release, when customers specify PostProcessing/ARUNK/@keepSegments="true" the API will now adjust segment specific seat assignment requests based on the ARNK segments present in the itinerary.
• (10/31/2023) Starting with this release, you can pass tokenized card number during vehicle booking. Previously, the API only allowed digits in case of passing a credit card form of payment.
• (03/18/2024) Added capability to specify wait interval before second and subsequent pricing operations at /CreatePassengerNameRecordRQ/PostProcessing/PricingInterval@waitInterval.

API Information

What's New

• In this version defect fixes were introduced.

API Information

What's New

• Added ability to create reservations for GDS and aggregator hotel chains at …/CreatePassengerNameRecordRQ/HotelBook
• Updated internal API EnhancedAirBookRQ to version 3.10.0
• Updated internal API PassengerDetailsRQ to version 3.4.0
• Modified RQ schema to allow for flight segment booking being optional (this allows customer to create PNRs consisting of only Miscellaneous segments)

Business Value

• Starting with version 2.2.0, the API was enhanced with the ability to create reservations for GDS and aggregator hotel chains. The solution integrates multiple sources of content including the Sabre global distribution system (GDS) and non-GDS sources such as re-distributors, agency-sourced hotel content and aggregators including HotelBeds, GTA, Expedia Partner Solutions and Booking.com.

API Information

What's New

• Added ability to specify multiple pricing instructions (e.g to provide different commission amounts per PQ).
• Added ability to pass Credit Card billing information.
• Added ability to validate airline record locator returned after ending the transaction.
• Added ability to validate whether HK status for flight segments was modified by the airline after ending transaction.
• Updated schema based on the latest version of EnhancedAirBookRQv3.9.0

API Information

What's New

• Added ability to specify whether the service should stop processing upon encountering a pricing error.
• Added ability to specify whether service should stop when actual price would be greater than specified amount of percent increase.