UN/EDIFACT is the United Nations standard for electronic data interchange for administration, commerce and transport, defining internationally agreed message structures for cross-border trade documents. It is also, less visibly, the transport layer of global airline distribution — the messaging that carries fares, availability and bookings between airlines, GDSs and agencies, and the incumbent that IATA’s NDC was written to replace.
EDIFACT
EDIFACT — UN/EDIFACT, the United Nations rules for Electronic Data Interchange for Administration, Commerce and Transport — is the international standard that lets trading partners exchange structured business documents without a shared application. Ratified in 1987 and maintained by UN/CEFACT, it defines a compact, rigidly formatted syntax for purchase orders, invoices, shipping notices, and customs declarations. For decades it has been the backbone of cross-border commerce and supply-chain messaging.
- Standard message types - Named messages like
ORDERS,INVOIC, andDESADVgive every common trade document a fixed, agreed structure. - Segment-and-element syntax - Data is packed into terse segments and data elements rather than the verbose markup of modern formats.
- Cross-industry, cross-border - A single UN-governed vocabulary spans retail, logistics, healthcare, and customs worldwide.
- Partner agreements - Interchanges run over agreed transports and message profiles negotiated between trading partners.
In today’s API landscape EDIFACT is the legacy that modern integration has to meet halfway — platforms like Stedi wrap EDI in REST APIs and webhooks so that a decades-old message format becomes a modern, event-driven OpenAPI workflow. It remains mandatory in large stretches of global trade, so translating between EDIFACT and JSON is a recurring integration job, and it is a reminder that the API economy is often about giving proven, entrenched data standards a programmable, agent-consumable surface.
The other EDIFACT: airline distribution
Outside supply chain, EDIFACT has a second life almost nobody outside the industry sees. Air travel distribution runs on it. Fares, availability, bookings and ticketing move between airlines, Global Distribution Systems and travel agencies as EDIFACT messages, maintained on the passenger side by IATA’s PADIS board. When an agency books a seat through a GDS, an EDIFACT interchange is usually what actually happens.
That makes EDIFACT the incumbent IATA NDC was written to displace — and the four State of Travel APIs Sector Reports found the displacement being driven by price rather than capability.
The State of Australian Travel APIs records Qantas surcharging A$11.50 per segment on EDIFACT against A$4.50 on Standard NDC, while its own distribution portal, Certified Technology Partners and an invitation-only Premium NDC tier are surcharge-free. The State of Canadian Travel APIs records WestJet applying a US$20–22 Distribution Cost Recovery surcharge to non-NDC EDIFACT bookings — while its NDC channel, certified since 2017, is stated for a Q4 2026 rollout and is not yet live. The penalty for using the old transport arrived before the new one did.
The transferable reading: a legacy message format does not retire on technical merit. EDIFACT persists in air distribution because it works, because settlement and accreditation are built around it, and because the alternative is gated behind certification and commercial agreement. It recedes only where somebody prices it out — which is a commercial decision dressed as a migration.
Referenced on the API Evangelist blog
Where this standard shows up across sixteen years of my writing at apievangelist.com — how it fits into API design, governance, and the agentic turn.
Stedi and EDI as Modern API Workflows
2026-07-08
