Airline content no longer comes from one place. It is split across GDS networks, airlines' own NDC connections and low-cost carriers that sit outside both. Innovate Solution aggregates those sources behind one search and one booking flow — in the ReservationHub interface, or through the TripGic API.

The problem

For years a GDS was the single window onto airline content. That is no longer true. Airlines increasingly distribute fares and bundles through their own NDC connections, and many low-cost carriers have never been fully available in a GDS at all.

An agency that searches only a GDS misses part of the market. An agency that wants everything ends up with a GDS screen, a set of airline portals and a handful of low-cost carrier websites — each with its own login, its own format and its own way of booking.

Building that coverage in-house is not a project but a permanent cost: every source has its own connection to build, certify and keep working as the airline changes it.

Why it is hard to fix

Every source speaks differently

GDS messaging, airline NDC interfaces and low-cost carrier connections each describe a flight, a fare and a booking in their own way.

Results have to be comparable

A traveller comparing two options should not have to know which channel each came from.

Pricing rules must apply everywhere

An agency's markup has to be applied consistently, whatever the source of the fare.

What we built

An aggregation layer sits between the agency and the sources. One search goes out to the connected GDS networks, NDC carriers and low-cost carriers; the responses are normalised into one structure and returned as one list.

The published coverage is 3 GDS networks, 37 NDC carriers and 100+ low-cost carriers. The same layer is available two ways: ReservationHub, a complete booking platform with its own interface, and TripGic, the API for teams building their own front end.

How it works

  1. One search request

    The agent, or the application calling the API, searches once.

  2. Fan-out to every connected source

    GDS networks, NDC carriers and low-cost carriers are queried through their own connections.

  3. Normalisation

    Responses are brought into one consistent structure, so options from different channels sit side by side.

  4. One booking flow

    The chosen option is booked through the source it came from, without the agent changing system.

What changes for the team

BeforeWith this in place
A GDS screen, airline portals and low-cost carrier websitesOne search
A separate login and booking process for each sourceOne booking flow
Content the agency does not check is content it does not sellConnected sources are searched together
Each new source is an integration project to build and maintainNew sources arrive through the aggregation layer

What it does not do

  • Coverage is the set of connected sources, not every airline in the world. Ask us about the specific carriers that matter to you.
  • In ReservationHub, GDS content is accessed with your own GDS credentials; the platform does not replace your GDS agreements.
  • Fares, availability and conditions are the airline's. The platform presents and books them; it does not set them.

Questions

What is the difference between GDS, NDC and LCC content?

A GDS aggregates many airlines' schedules and fares through one network. NDC is the standard airlines use to distribute fares and bundles directly through their own connections. Low-cost carriers often sit outside both and are reached through separate connections.

How much flight content is connected?

The published coverage is 3 GDS networks, 37 NDC carriers and 100+ low-cost carriers.

Is this available as an API?

Yes. TripGic exposes the aggregation as an API for teams building their own booking experience; ReservationHub provides it with a ready-made interface.

Related

About this page. This is a solution case study: it describes a problem and how the platform solves it. It contains no customer names and no performance figures. For measured results from a named customer, see the customer case studies.

Want to see this working on your own bookings?