Skip to main content

Create Passenger Name Record

2.4.0
Air
Reservation
SOAP API
Travel Agency
Airline Carrier
  • 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

API Information

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

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

Functional Updates And Enhancements

In the Request

Optional

Parameter: AirlineRefId

Type: string

Description: Passes an airline reference for a booking made outside of Sabre system. When you combine "AirlineRefId" with other flight segment details, system will create a passive PNR segment.

Sample Value:

 
Note: Only "YK" flight segment status code is supported.

Relase note ID: 15761


API Information

Response Format
XML
Service Action Code
CreatePassengerNameRecordRQ
Current Version
2.3.0
Target Audience
TN
Environment
Production

What's New


Resolved Issues

In the Request

N/A

With the change our users will be able to book vehicles using vouchers without any issues.

Relase note ID: 14849


  • 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)

API Information

Response Format
XML
Service Action Code
CreatePassengerNameRecordRQ
Current Version
2.2.0
Target Audience
TN
Environment
Production

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.

Functional Updates And Enhancements

In the Request

Optional

Parameter: AirBook

Type: N/A

Description: Element used to book air segments

Sample Value:

 
Note: Previously this element was mandatory

In the Request

Optional

Parameter: HotelBook

Type: N/A

Description: element used to book GDS or Aggregator hotel segments

Sample Value:

 
Note:

Relase note ID: 12832


  • 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

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

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

Functional Updates And Enhancements

In the Request

Optional

Parameter: AirPrice

Type: N/A

Description: Element used to specify pricing instruction

Sample Value:

 
Note: The repeat factor was changed from "0" to "10"

In the Request

Optional

Parameter: CreditCardData

Type: N/A

Description: used to pass the credit card billing information

Sample Value:

<CreditCardData>
  <BillingInformation cardHolderName="SWS TEST" streetAddress="123 1ST AVE" city="NEW YORK" stateOrProvince="NY">
    <PostalCode>H3G4CJ</PostalCode>
    <Zip>12345</Zip>
  </BillingInformation>
</CreditCardData>
Note:

In the Request

Optional

Parameter: PostBookingHKValidation

Type: N/A

Description: Used to specify wait interval to validate whether after booking is ended codeshare flights keep the holding confirmed status

Sample Value:

<PostBookingHKValidation waitInterval="1000" numAttempts="2"/>
Note:

In the Request

Optional

Parameter: WaitForAirlineRecLoc

Type: N/A

Description: Used to specify wait interval to wait for airline record locators to be returned

Sample Value:

<WaitForAirlineRecLoc waitInterval="1000" numAttempts="2"/>
Note:

Relase note ID: 12926


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

API Information

Response Format
XML
Service Action Code
CreatePassengerNameRecordRQ
Current Version
2.0.0
Target Audience
TN
Environment
Production

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.

Functional Updates And Enhancements

In the Request

Optional

Parameter: haltOnAirPriceError

Type: boolean

Description: used to specify whether the service should stop processing upon encountering a pricing error

Sample Value:

 
Note:

In the Request

Optional

Parameter: HaltOnNonAcceptablePrice

Type: boolean

Description: used to specify whether service should stop when actual price would be greater than "AmountSpecified" percent or amount increase

Sample Value:

 
Note:

Relase note ID: 12964