NDC connection: why direct integration is not just a technical issue
I was recently talking to a colleague who is thinking about direct NDC integration for his travel agency. The question he asked was completely logical: why use an aggregator or other distribution channel if the agency can connect directly with the airline?
On paper, that approach sounds appealing. The agency gains greater control over content, can display branded fares and ancillary services directly, and is not completely dependent on the capabilities of the intermediary platform.
However, the conversation quickly got round to a more important issue. What happens after a ticket has been sold?
Can an agent simply change the date? Can it automatically calculate the price difference, issue a partial refund, or add baggage? How is a flight schedule change handled? What happens to accounting data and payment?
It is precisely on these issues that it becomes clear that NDC integration is not just about connecting to yet another API.
NDC is not one universal API
IATA defines New Distribution Capability as an open data-exchange standard based on offer and order management. The goal is airlines enable them to offer richer content, additional services and more precisely tailored products through various sales channels.
However, the term „NDC standard” may create the false impression that all airlines use the same technical interface and the same business processes.
In practice, numerous generations of NDC schemes exist simultaneously. In addition, airlines decide for themselves which features to implement. Two carriers can use the same version yet have completely different processes for purchasing ancillary services, rebooking or refunds.
Therefore, the „NDC enabled” label does not tell you much about the agent's actual user experience. The connection may support searching and booking, while at the same time requiring manual processing for almost every more complex post-sale action.
From upselling to order management
Version 17.2, released in 2017, became the first widely adopted operational foundation of NDC. It more clearly separated searching, verification, and final booking creation. It improved seat display, the sale of ancillary services, and the processing of changes and cancellations.
Although more advanced versions were released later, 17.2 is still present among a number of airlines and technology providers. The reason is not necessarily technological backwardness. For many carriers, that version still covers the majority of commercial needs, while transitioning would require changes across a larger number of connected systems.
Generations 18.x, 19.x and 20.x gradually expanded NDC towards structured fare rules, payments, accounting and financial reporting. As a result, the standard began to move beyond the scope of merely purchasing a flight ticket.
A major structural shift arrived with versions 21.x. Common data elements reduced some of the inconsistencies between quotes and orders, while the OrderQuote function made it possible to calculate the financial impact of a change before confirming it. Version 21.3 became an important new baseline for more complete servicing processes and the future development of the Offers and Orders model.
Versions 24.x have further linked order items, payments, penalties and the residual value of unused services. This is important for agencies because it provides a more precise understanding of how much a passenger needs to pay extra or how much the airline owes them after a change.
The newest version is not always the most important
On 16 March 2026, IATA published the 26.1 standards package. Among the more important new features were payment for a single order item using multiple payment methods, fee simulation prior to transaction confirmation, and more detailed exchange of data on VAT, GST and other consumption taxes.
Version 26.2 was released on 4 June 2026, but its main changes were focused on baggage-related messaging. This clearly demonstrates why a higher version number does not automatically mean a major change for every travel agency.
For the agency, it is more important whether a specific integration supports its processes than whether it uses the technically newest scheme.
Direct integration brings control, but also obligations
Direct connection may make sense for an agency that generates a large volume of traffic with a smaller number of strategically important airlines. It can also be justified when an agency is developing its own platform, wants to shape a special user experience, or needs content that is not equally available through other channels.
However, every direct connection requires development, testing, monitoring and maintenance. It is necessary to handle different response formats, errors, authentication methods, rate limits and version changes. Along with this come payments, refunds, traffic disruptions, financial data reconciliation and agent support.
The problem becomes even more complex when an airline uses a newer search and booking scheme, and an older process for servicing. Such hybrid implementations are not uncommon as they allow carriers to introduce new functions without completely replacing existing infrastructure.
An aggregator or GDS does not remove this complexity. It takes it on itself and tries to turn various integrations into a more uniform process for the agency. In return, the agency may have less control over individual functions or depend on the speed with which the intermediary introduces a particular airline's content.
Therefore, the decision is not a simple choice between „direct” and „via an intermediary”. For many agencies, a hybrid model will work best: direct connections with a few key carriers, while other NDC and traditional content is accessed through an aggregator or GDS.
In the end, I didn't advise my colleagues from the beginning of the story to ask first which version of NDC the airline is using. More useful questions were: which processes can we complete from start to finish, how much will their maintenance cost us, and what happens when a passenger needs post-purchase assistance?
It is precisely then that the true value of NDC integration is revealed. Not at the moment when the offer appears on the screen, but when the booking needs to be changed, serviced and financially settled without manual work and calls to customer support.
