What NDC (New Distribution Capability) is, how airline direct distribution works, and how flight data APIs like AirLabs fit into the picture after the NDC booking is complete — for tracking, alerts, analytics and traveller support.
NDC — the New Distribution Capability — is an XML-based data transmission standard developed by IATA that lets airlines distribute their content directly to travel sellers, without the traditional Global Distribution System sitting between them. Since it was first published in 2012, NDC has moved from a technical proposal to the mainstream of how airline content reaches the market: the major carrier groups now transact a substantial share of their traffic through NDC channels, and travel management companies, corporate booking platforms and online travel agencies have been building NDC integrations to keep up.
The value NDC unlocks is richer content. A traditional GDS booking exposes the essentials — fare, seat, taxes — with limited scope for the airline's differentiated products. An NDC booking can include ancillary services (bags, seats, meals) priced and offered as part of the same transaction, branded fare families with clear feature differences, personalised offers based on the traveller profile, and richer media (branded fare descriptions, images, upsell options). Airlines get to tell their commercial story; sellers get more to sell and less friction between what they display and what the airline actually operates.
Building an NDC integration means implementing the airline's IATA NDC schema for search, offer management, order creation, servicing and post-ticketing — the full commercial lifecycle from "what does this cost" to "here is your ticket." That commercial lifecycle is the NDC platform's domain. This guide is about what comes next: everything a working travel product needs after the NDC booking is complete, where a flight data API like AirLabs is a natural fit.
"NDC is the booking. The booking is not the whole product. Between the booking and the traveller returning home lies the operational layer — tracking, delay alerts, disruption response, duty of care, post-trip analytics — and that layer is not what an NDC pipeline is designed to solve. It sits on top."
An NDC integration handles the transactional pipeline: shopping, offer management, seat selection, ancillary bundling, payment, ticket issuance, subsequent servicing (exchanges, refunds, void), and — at the end of the trip — reconciliation and reporting. Every one of those steps is anchored to the commercial contract between airline and customer.
What NDC does not typically handle is the operational layer of the trip itself. That is not a deficiency of the standard — it is a different problem domain. Once a ticket is issued, the questions become operational rather than commercial:
These are questions about flight operations, not about the booking. They map cleanly to a flight data API — real-time positions, live schedules, delay signals, alternate airport searches and historical performance metrics — and this is where AirLabs sits in a modern NDC-based travel product stack.
The most immediate use of aviation data after an NDC booking is flight status monitoring. Every ticketed flight has a state that evolves — from scheduled through boarding to active, ultimately to landed — with delays, gate changes and estimated-time revisions along the way. Surfacing that state to the traveller and to the seller's operations team is what keeps the post-booking experience feeling professional rather than transactional.
The AirLabs Flight Information API accepts a flight identifier and returns the current status:
GET https://airlabs.co/api/v9/flight?flight_iata=BA117&api_key={KEY}
{
"flight_iata": "BA117",
"airline_iata": "BA",
"dep_iata": "LHR",
"arr_iata": "JFK",
"dep_time": "2026-07-22 10:00",
"dep_estimated": "2026-07-22 10:47",
"dep_terminal": "5",
"dep_gate": "A22",
"arr_time": "2026-07-22 13:15",
"arr_estimated": "2026-07-22 14:02",
"arr_terminal": "7",
"status": "active",
"delayed": 47,
"aircraft_icao": "B77W"
}For every ticketed flight in your NDC booking record, the same lookup applies. The flight_iata from the NDC ticket record is the join key; the AirLabs response provides everything a traveller-facing status view needs — scheduled and estimated times, delay in minutes, current gate and terminal, aircraft type — with no additional integration per airline.
For proactive notifications, the AirLabs Flight Alert API provides webhook-based subscriptions per flight identifier. When a tracked field changes — a delay is announced, a gate is reassigned, a status transitions — the endpoint receives a notification without your system having to poll. This is the pattern that supports "your flight has been delayed" alerts to the traveller and simultaneously routes the same signal to the customer service team so they can respond before the traveller has to call.
When flights are disrupted, an NDC-based platform's commercial layer handles the rebooking transaction, but the operational context — which flights are affected, what alternatives exist, what the current situation looks like at the affected airport — comes from flight operational data.
The AirLabs Flight Delays API filtered by airport returns the current disruption picture in one call:
GET https://airlabs.co/api/v9/delays?dep_iata=JFK&type=departures&api_key={KEY}For a JFK ground stop or a weather event, this immediately shows every currently delayed departure, letting the operations team identify which of their booked travellers are exposed to the disruption. The NearBy API accepts coordinates and a distance and returns alternative airports within range, useful for identifying rebooking options during airport-level disruptions:
GET https://airlabs.co/api/v9/nearby?lat=40.6413&lng=-73.7781&distance=200&api_key={KEY}The rebooking transaction still runs through the NDC integration — new offers, new tickets, new orders. But the decision about which flights to attempt to rebook onto, and the operational reality that informs it, comes from the flight data layer.
For corporate travel platforms, TMC operations desks and any product where the seller has ongoing responsibility for the traveller during the journey, the NDC booking is the beginning of the relationship rather than the end. Duty of care — the obligation to know where travellers are and to help them when disruption strikes — is answered operationally, not commercially.
The AirLabs post-booking data layer supports this directly:
Our deeper treatment of the duty-of-care compliance framework — ISO 31030, TMC architecture patterns, audit trail requirements — is covered in our Corporate Travel Risk Management guide.
Beyond real-time operations, aviation data enriches the NDC booking record for analytics, reporting and post-trip context that the NDC transaction itself does not carry.
For each flight in a booking, the Fleets Database queried by tail number returns the aircraft's model, manufacturer, age and manufacturer serial number. This turns a "Boeing 737" flag on the ticket into a specific airframe with a known service history — useful for reporting on which aircraft types are actually operating the travel programme, which airlines are flying newer versus older fleets, and how fleet composition affects the on-time record.
The Airlines Database provides carrier context — full airline name, country, fleet size, average fleet age, IOSA safety registration status, operational scope. Joining this to the airline IATA code from every NDC booking produces the enriched view of "which carriers are we actually flying" that a raw booking record does not provide.
The Airports Database provides airport context — full name, city, country, timezone, runway count, connections. For programmes analysing route performance, terminal preferences or geographic distribution of travel, this reference layer is what makes booking data queryable at the analyst level.
For historical performance analysis — was this route reliable last quarter, which carriers hit their scheduled times, where did delays cluster — the AirLabs endpoints support the on-time performance metrics that inform contract renegotiations, preferred carrier programmes and travel policy design. The framework for these metrics is covered in our Flight Performance Data guide.
Even inside the NDC integration itself, there are aviation reference data needs that are cleaner to source from a maintained API than to build and maintain internally. Airport codes, city codes and their metropolitan groupings, airline codes and callsigns, aircraft type designators, IATA and ICAO code correspondences, timezone identifiers and country reference data all change over time — new low-cost carriers launch, airports open, IATA codes are reassigned, airline branding changes.
The AirLabs reference databases — Airports, Airlines, Cities, Countries and Timezones — are refreshed centrally, so an NDC integration can rely on them for the standing reference layer rather than maintaining local tables that go stale. The Name Suggestion API provides autocomplete for airport, city and country names in the user-facing input fields that precede any NDC search.
For a platform combining NDC-based booking with post-booking operational support, the data flow typically looks like this:
Each step has a clear owner. The NDC layer owns the commercial transaction. The AirLabs layer owns the operational context. Together they cover the full lifecycle from search to post-trip reporting without duplicating each other's scope.
Several product categories run this pairing in production:
Corporate travel platforms and TMC systems. The NDC integration handles the booking; the aviation data layer handles status tracking, duty-of-care compliance, disruption response and post-trip reporting for the corporate client.
Online travel agencies with post-booking service features. OTAs increasingly offer their customers real-time flight tracking, delay alerts and rebooking assistance as differentiators. The NDC layer handles the transaction; the aviation data layer supports the ongoing customer relationship.
Corporate booking platforms serving mid-market enterprises. Platforms building on top of airline direct connections need operational context — where are our travellers, what is delayed, what alternatives exist — that the booking layer does not provide.
Business travel analytics teams inside enterprises. Aggregate reporting across the travel programme requires enriched data — full airline names, aircraft context, on-time performance — that the raw NDC booking record does not carry.
Travel insurance and disruption compensation platforms. Insurance and compensation products depend on validated flight status data to assess claims eligibility, and on delay signals to trigger payouts. The AirLabs delay and status data is the operational input that supports these workflows.
cs_airline_iata and cs_flight_iata fields identifying operating versus marketing carriers, matching the way NDC bookings can carry marketing airline codes that differ from the operator._fields parameter keeps AirLabs responses focused on the specific fields your traveller notifications and internal dashboards actually consume.If you are building a corporate travel platform, an OTA, a TMC system or any product that combines airline direct distribution with a live customer relationship, the NDC integration is one layer and the aviation data feed is another. AirLabs supplies the aviation data layer — real-time status, alerts, disruption context, historical enrichment and standing reference data — through documented REST endpoints and a single API key, so the operational side of your product runs on the same reliable foundation as the transactional side.
Our Developer API allows you to create a custom experience for your users and increase the value of your product:
_fields for lean, targeted responsesYou can try it right now without any obligation! Get a free flight API plan and see for yourself that we have exactly the data you need!
If you need more information, don't hesitate to contact us. We are always happy to chat with our customers and are sure to find a customized solution for each request.
Explore AirLabs, or create an account instantly and start using API.
Get FREE API Key