PADIS — Passenger and Airport Data Interchange Standards — is the IATA board that maintains the code lists and message standards used across passenger air travel. The code lists are the shared enumerated vocabulary that lets systems from different vendors agree on what a value means: service codes, document types, status indicators, reason codes and the rest.
IATA PADIS
PADIS is the unglamorous layer that makes air travel messages mean the same thing in two different systems. The board maintains both the EDIFACT and XML message standards for passenger travel and, more durably, the code lists — the enumerated values that populate them. Service codes, document type indicators, status codes, reason codes: the vocabulary that turns a field into a fact.
- Enumerated, shared and stable - the value of a code list is that everyone resolves the same code to the same meaning, across vendors and decades.
- Underneath both generations - PADIS code lists are referenced by EDIFACT messaging and by NDC XML alike. The transport changed; the vocabulary largely did not.
- Portable by construction - a PADIS code carries its meaning with it when a record moves between systems, which is precisely what a vendor-minted identifier does not do.
What the evidence shows
The State of Canadian Travel APIs records Air Canada publishing NDC 17.2 (EDIST) alongside IATA PADIS code lists and IATA Resolutions 762/763 — the most standards-conformant airline interface in the four-market study. The conformance is real. The access is discretionary: certification is required for production, Air Canada may audit the partner application, may change display obligations unilaterally on thirty days’ notice, and reserves the right to revoke NDC programme access at its sole discretion.
The broader finding this catalog entry exists to carry is the identifier split the travel quartet
uncovered. On the portable side sit the identifiers the industry collectively owns: IATA airline
designators and ticketing plates, ICAO codes, PNR record locators, agency accreditation numbers,
EMD and traffic documents, ATPCO fare bases, and PADIS
code lists. On the non-portable side sit the identifiers platforms mint: NDC OrderID, OfferID and
OfferItemID, vendor order numbers, and internal booking references.
A customer’s data portability in travel is decided by which column their records hang on. PADIS is
the clearest example of the portable column working as designed — and NDC’s platform-minted OrderID
is the clearest example of a modern standard moving a key out of it.
Referenced in API Evangelist papers
This standard shows up in my published research. These reports read the machine-readable evidence provider by provider — and put this standard in the context of a real sector.
The State of Canadian Travel APIs
One of the portable identifier families — PADIS code lists travel between systems, unlike the airline-minted OrderID that NDC introduced.
