PNR passenger data: when it is created and how it differs from API

A PNR, or Passenger Name Record, is passenger data generated during the booking or buying of an air ticket. It may contain as little as a name, an itinerary and a ticket indicator. It is distinct from Advance Passenger Information (API), which ICAO says is generated during check-in.

What a PNR is

ICAO describes PNR data as data generated during the booking or buying of an air ticket. IATA says that PNR contains data supplied by travellers at booking and is held in airline reservation systems until check-in. In this article, PNR is therefore discussed as passenger data connected with booking, rather than as a standalone travel document.

The supplied sources do not say that every PNR has the same content. ICAO specifically says that a PNR can contain as little as a name, an itinerary and a ticket indicator. That minimum matters: a PNR may be limited in detail. The sources also do not set out a universal format for PNR data, so this article does not assume one.

**Editorial inference:** Because ICAO says that a PNR may contain only a ticket indicator and that its accuracy is not guaranteed, a PNR alone should not be presented as independently verified proof that an electronic ticket was issued. For that separate subject, see the dedicated electronic-ticket article.

When PNR and API are generated

PNR and API both concern passenger information, but ICAO places their generation at different points. PNR is generated during booking or buying of an air ticket. API is generated during check-in. This is the evidence-based distinction: they are not described as the same data created at the same moment.

IATA also says that PNR is held in airline reservation systems until check-in. This describes the period stated by IATA. It is not a promise about the completeness, accuracy or availability of any particular set of data.

The supplied evidence does not describe technical screens, data fields, display practices or check-in procedures. It is better not to fill those gaps with assumptions. For a traveller, the useful starting point is simply to identify whether the information being discussed concerns PNR created at booking or purchase, or API generated at check-in.

Minimum content, accuracy and sensitive data

ICAO says a PNR can contain as little as three elements: a name, an itinerary and a ticket indicator. “Can” is important. It establishes a possible minimum, not a required list for every record.

ICAO also says PNR accuracy is not guaranteed. This does not mean that every item is inaccurate. It means the source provides no general assurance that PNR data is accurate. **Editorial inference:** where accuracy is not guaranteed and content may be minimal, a single PNR detail should not be treated as a broad conclusion by itself.

ICAO further notes that PNR can contain sensitive personal data. This makes careful handling important. **Editorial guidance:** share only the information needed for the specific conversation or task, and avoid circulating personal details that are not needed. This is a practical caution, not a statement of universal law, carrier policy or system capability.

The evidence provided here does not specify which sensitive data may appear, who may receive it, or what legal duties apply in a particular country. Such questions may depend on applicable jurisdiction-specific law and circumstances, which are outside this general article.

A practical reading workflow

Start by separating supported facts from assumptions. The supported facts are that PNR is generated at booking or purchase; contains traveller-supplied booking data; can contain a name, itinerary and ticket indicator; may contain sensitive personal data; and has no guaranteed accuracy.

Next, distinguish PNR from API by timing. Information generated during check-in is described by ICAO as API. Information generated during booking or purchase is described as PNR. Do not assume that one label answers questions that the evidence does not address.

Then keep the scope narrow. **Editorial guidance:** if the purpose is to understand passenger data, focus on creation timing, possible minimum content, accuracy limits and privacy sensitivity. Do not turn a limited data point into a claim about matters not established by the record.

Common mistakes

One mistake is assuming that every PNR is extensive. ICAO says it can contain very little information.

Another is treating PNR and API as interchangeable. ICAO distinguishes them by when they are generated.

A third is assuming that information appearing in PNR is necessarily correct. ICAO expressly says accuracy is not guaranteed.

A fourth is sharing PNR-related information casually. ICAO says PNR can include sensitive personal data, so unnecessary sharing can expose information that deserves care.

Traveller checklist

- Is the information being discussed PNR created at booking or purchase? - Is it instead API generated at check-in? - Have you allowed for the possibility that PNR content may be minimal? - Have you avoided assuming accuracy merely because a detail appears in PNR? - Are you limiting the sharing of personal information to what is needed?

Guidance for travel agents

Agents can explain the basic distinction without making promises that the evidence does not support. State that PNR is generated during booking or buying, while API is generated during check-in. Explain that PNR may contain limited information and that ICAO does not guarantee its accuracy.

When personal information is involved, **editorial guidance** is to keep communication limited to the relevant information and to remind travellers that PNR may contain sensitive personal data. Do not infer carrier rules, ticket conditions, supplier capabilities or legal rights from these general facts. Those matters, where relevant, depend on the carrier’s rules, ticket conditions and applicable law.

Frequently asked questions

What does PNR mean? PNR means Passenger Name Record. ICAO says PNR data is generated during the booking or buying of an air ticket, and IATA says it contains traveller-supplied booking data.

What is the least a PNR can contain? ICAO says a PNR can contain as little as a name, an itinerary and a ticket indicator. It does not say every PNR has identical content.

Is PNR the same as API? No. ICAO says PNR is generated during booking or buying, while API is generated during check-in.

Is PNR data guaranteed to be accurate? No. ICAO states that PNR accuracy is not guaranteed. That is not a finding that every item is wrong; it is a limit on any general assurance of accuracy.

Why should PNR information be handled carefully? ICAO says PNR can contain sensitive personal data. Editorial guidance is to share only what is needed for the relevant purpose.