Intro to PNRs
Learn the required fields and workflows needed to sequence a passenger name record.
A Passenger Name Record (PNR) is a reservation created with a travel industry vendor (e.g. an airline or a hotel) on behalf of a traveler. You must complete a passenger name record to book a reservation in the Sabre GDS (including via Sabre APIs). Every PNR has required fields to identify the travel agency and the traveler.
What the PNR requirements are for the traveler
The bare minimum requirements for a passenger name record are referred to as PRINT:
- Phone number
- Received from
- Ticketing time limit
Which workflows you can use for sequencing
There are a few different ways to sequence the creation of a PNR into your application. You have the following options:
- Iteratively: A few pieces at a time, possibly initially using test values for some incomplete fields.
- All at once: once you have all of the required information.
- by using the information from a traveler profile.
To get you started, we've compiled basic workflows to create a passenger name record:
- For flights, start with the low fare search and book workflow.
- For cars, start with the car reservation workflow.
- For hotels, start with the book hotel reservation workflow.*
*NOTE: A traveler name and agency address are required to create a PNR for a hotel.
What scenarios you can use for inspiration
For more information on the third sequencing option using information from a traveler profile to create a PNR, see our example scenario for Texas Fares in How to manage a token.
- Learn about the Sabre work area. The Sabre work area is where you build a PNR. See Intro to the Sabre work area.
- Learn about the different ways to use Sabre APIs. Peruse our use cases to learn more about how you can use Sabre APIs to complete your common travel workflows in Sabre APIs: workflows.
- Optimize your workflows. Did you know using a sessionless token can reduce the number of calls you make to Sabre? See Optimize workflows for more tips.