PNRproPNRPro

← Articles

SSR DOCS & APIS: the passport data airlines require

For most international flights, an airline must hold passport details before departure. Here's what that requirement is, how the DOCS entry encodes a passport, and what each field means.

What APIS is

Advance Passenger Information System (APIS) is the framework by which airlines transmit passenger identity and travel-document data to the authorities of the countries being flown to or from, before the aircraft departs. It exists for border security and immigration pre-clearance. In practical terms, for a booking to be "document-complete" the airline needs the traveller's passport details attached to the PNR — and if they are missing, the passenger can be stopped at check-in.

How the data is stored: the SSR DOCS entry

Passport details live in the PNR as a Special Service Request of type DOCS. It is a single structured line, and the fields are separated by slashes in a fixed order. A typical entry looks like this:

SR DOCS YY HK1/P/GBR/999237144/GBR/18SEP99/F/13MAR27/TEST/ANGELA ZOE/P1

Reading the slash-separated fields in order:

FieldMeaning
PDocument type — P for passport
GBRIssuing country (ISO 3-letter code)
999237144Passport number
GBRNationality
18SEP99Date of birth
FSex — M / F / X
13MAR27Passport expiry date
TESTSurname
ANGELA ZOEGiven name(s)
P1Passenger association — links the data to passenger 1

Where the data comes from: the MRZ

Every one of those fields already exists, in a standard machine-readable form, at the bottom of the passport's photo page — the two-line Machine-Readable Zone (MRZ) defined by ICAO Doc 9303. The MRZ is a checksum-protected encoding of the document number, nationality, date of birth, sex, expiry and name. Because it carries its own check digits, the data can be validated mathematically — a strong signal that it was read correctly. That is exactly what the PNRpro passport tool does: it reads the MRZ and builds the DOCS entry for you, in the format your host system expects.

Three systems, three formats

The same passport produces three slightly different entries depending on the GDS. The fields are identical; the prefix and passenger-association syntax differ:

Always verify a generated DOCS entry against your own desk's format line before sending it into a live PNR — market and office configuration can enforce their own punctuation and keywords. Treat any generated entry as a correctly-ordered draft.

A note on privacy

Passport data is sensitive. A tool that reads it should do so on your own device, without uploading the image or the extracted fields anywhere — which is how the PNRpro passport reader is built. Nothing is sent to a server; the reading happens entirely in your browser.

Open the passport tool →