Skip to content
Blog

NDC API providers: three different things under one name

Tekravel Editorial
Written with the help of AI

The request usually arrives as one line from the commercial side: "we need NDC content, find us a provider." You search for NDC API providers, and the results put an airline's developer portal, an aggregator's sales page and a booking platform's API reference in the same list, as if they were three quotes for the same job. They are not. Each one leaves a different amount of work on your desk, and a different party on the phone when a passenger wants to change a flight.

This piece is for the developer or technical lead who has to turn that one line into a decision. It assumes you know REST and JSON and nothing about airline distribution. It does not repeat the comparison of the two channels, which is in NDC API vs GDS; it starts after you have decided you want airline-direct offers and need to know whom to get them from.

What the standard gives you, and what it leaves open

NDC is a messaging standard published by IATA. It describes how a seller asks an airline for offers and turns one into an order: AirShopping returns offers, OfferPrice confirms one, OrderCreate books it, and a family of order messages retrieves, changes and cancels it afterwards. The airline builds the offer itself, which is why fare bundles, seats and bags can arrive as part of the answer instead of being assembled by an intermediary from filed fares.

What the standard does not give you is uniformity. Each airline implements the schema version it chose, the messages it chose, and its own rules for payment and ticketing time limits. Two airlines that both "support NDC" can differ on whether an order may be held unpaid, whether a change is made through the API or by email to a support desk, and whether you are told when the airline moves the flight. So "NDC API" is never one integration. It is one integration per airline, unless someone else has already absorbed the differences. That someone is what the word provider is really pointing at.

The three kinds of NDC API providers

Sort every result on your list into one of these before reading its feature page.

The airline itselfAn aggregatorA booking platform
What you connect toThat airline's own NDC endpointOne API that fronts many airlines' NDC endpoints, often next to other sourcesA flight API whose results may include NDC offers among other content
Who holds the agreement with the airlineYou, or the accredited agency you build forIt varies: sometimes you still need your own agreement per airline, sometimes the aggregator's covers youThe platform or its suppliers
What you buildEverything, once per airlineOne integration, plus handling for whatever the aggregator did not normaliseSearch, book and service against one model
Who settles with the airlineYouYou or the aggregator, depending on the contractThe platform; you settle with the platform
Who answers a servicing problemThe airline's agency supportThe aggregator first, then the airlineThe platform
What you give upNothing, except timeSome airline-specific features, flattened into a common shapeThe direct relationship, and any private deal you hold with an airline

The last row is the one to argue with. A team with one dominant home carrier and a negotiated deal may find the first column cheaper than it looks, because one airline is one integration. A team selling many airlines to walk-in customers will not.

Search is the easy half

Every provider demo shows shopping. Offers come back, they have brand names and baggage icons, the price holds through OfferPrice, the order is created. That path works almost everywhere, because it is the path every airline built first.

The cost is in what happens to an order after it exists. A passenger wants to move to the next day. A passenger cancels and expects the refund the fare rules allow. The airline retimes the flight and somebody has to tell the passenger and accept or reject the new time. A name was typed wrong. In the older channel, an agent could do most of this from one screen for most airlines. Through NDC, each of these is a separate capability that each airline may or may not have exposed, and that each provider may or may not have passed through.

Where a capability is missing, the fallback is a human: an email or a call to the airline's support desk, or a form on a portal, handled by your client's staff. This is not a failure of the provider; it is the state of each airline's implementation. But it decides how many people your client needs on the service desk, and a sales page will not tell you.

There is a second, quieter consequence. An order created through an airline's NDC channel generally has to be serviced through the same channel. If your client's agents are used to opening any booking in their existing system and changing it there, an NDC order may not appear there at all, or may appear read-only. Ask where the order lives before you ask how fast the search is.

Ask for the servicing matrix, per airline

The single most useful document a provider can give you is a grid: airlines down the side, operations across the top, and in each cell whether it works through the API, works by a manual route, or does not work. If the provider cannot produce it, you will be producing it yourself in production. The columns to insist on:

  • Hold without payment. Can an order be created and paid later, and how is the time limit returned?
  • Forms of payment. Which ones the airline accepts through this route, and whether the agency's usual settlement method is among them.
  • Voluntary change. Is repricing a change (OrderReshop) and committing it (OrderChange) available, or is it a manual request?
  • Cancel and refund. Is the refund amount quoted before the cancel is committed, and is the refund issued through the API?
  • Airline-initiated changes. Are schedule changes pushed to you as a notification, or do you have to poll every order to find them?
  • Ancillaries after booking. Can a seat or a bag be added to an existing order, or only at creation?
  • Name corrections and special service requests. Through the API, or manual.
  • Test environment. Does each airline have one reachable through the provider, and does it behave like production for servicing, not only for shopping?

Get this in writing and dated. Airline implementations move, and a cell that was manual when the grid was drawn may since have changed in either direction.

Who settles, and whose accreditation it rides on

This is the part a developer is tempted to leave to the commercial team, and should not, because it changes the build. If the agency you are building for is IATA-accredited and has its own agreement with the airline, orders can be settled the way its tickets already are, and your code carries the agency's identifiers in each request. If it is not accredited, somebody else's accreditation stands behind every order: the aggregator's, a consolidator's, or the platform's. Then the money moves differently, the agency is extended credit or prepays a balance, and your integration needs to know about limits and balances as well as offers and orders.

Neither arrangement is better. What goes wrong is finding out which one you are in after the build.

Where this platform sits

We are in the third column of the table. The platform exposes flight and hotel APIs, and access starts as a conversation rather than a self-serve key: the first exchange is about what you sell and where, because flights, hotels, tour packages and attractions are each activated per tenant, and the supplier content a tenant sees is the content its supplier groups grant it. Sub-agent credit limits and settlement invoicing are part of the platform rather than a spreadsheet beside it.

What we do not publish here: a list of airlines, a count of sources, or a statement of which content reaches you through NDC and which through other channels. If that matters for your case, and for a team with a private airline deal it does, ask it in the first conversation and ask for the answer per airline. The travel APIs page is where that conversation starts. If you are still deciding what sits behind any provider's endpoint, look behind the API covers the contract questions this piece left out.

What choosing on the shopping demo costs

The bill arrives late, which is why it is easy to ignore. Shopping and booking go live, the first weeks look fine, and then the changes start. Each change that the API cannot carry becomes a ticket for the client's staff, handled by email with an airline desk that keeps its own hours. Refunds that were never quoted through the API get promised to passengers from memory of the fare rules, and the difference between what was promised and what the airline returns comes out of the agency's margin. A retimed flight that nobody was notified about is discovered by the passenger at the airport.

None of that shows in a demo, and all of it is knowable before you sign. The grid tells you. A provider of any of the three kinds that hands you an honest grid with gaps in it is a better choice than one that says every airline is fully supported, because the first has told you where your client's staff will be needed and the second has left you to find out.

Tekravel Editorial

Travel technology desk

The Tekravel travel-technology desk writes for the trade: agency owners, consolidators and the developers who integrate them. Every article is checked against the platform it describes before it is published.