Reach without a new build per agency
You integrate once. Every TMC, corporate desk, distributor and OTA on the platform can sell your offers as soon as you agree access with them.
TravviseConnect puts your NDC content on the screens of travel management companies, corporate travel desks, distributors and their sub-agent networks in Qatar, Saudi Arabia, the UAE, Pakistan, India, Egypt and Nigeria — shown the way you built it, and serviced end to end.
Why connect
Each business on TravviseConnect runs its own branded portal. Once your NDC is connected, it can be switched on for any of them — and for the sub-agents they serve on their B2B portals.
You integrate once. Every TMC, corporate desk, distributor and OTA on the platform can sell your offers as soon as you agree access with them.
Each agency connects with its own airline credentials, kept in a managed key vault. Bookings sit under the agency’s own commercial agreement with you.
Your NDC offers appear in the same search as Amadeus, Travelport and low-cost carriers, so agents compare you fairly instead of opening another portal.
We connect to your NDC API directly or through the aggregator you choose — Qatar Airways, for example, is connected through Farelogix.
Merchandising
NDC exists so airlines can sell richer offers. We keep that richness all the way to the agent’s screen.
Order lifecycle
Agents don’t drop to your portal or a terminal to service a booking. Every step works on the order you hold.
Offers stream into one results list as you answer.
The chosen offer is re-priced with you before booking.
Your order is created and held; the agency record stays in sync with it.
An agent issues each ticket deliberately — never automatically.
Exchanges show your penalty and fare difference before confirming.
Eligibility checked first; refunds quoted, then confirmed.
Services are enabled per airline once they pass testing against your environment.
Clean transactions
A PNR never turns into a ticket on its own. Agents review and issue, so a ticket exists only when they mean it to.
Each request and response to your API is logged per session, which shortens certification and makes any query traceable.
Your offers stay priced in your currency; each agency sees and settles in its own selling currency.
Every agency has its own database on Microsoft Azure, and every user signs in with multi-factor authentication.
How we integrate
Adding an airline is one new adapter on our platform. Nothing else changes, so your integration doesn’t wait on anyone else’s.
API documentation, schema version and test credentials.
An adapter to your published schema, against your test system.
We run your certification cases with your team.
Switched on for a first agency with its own credentials.
Opened to more agencies as you agree access.
Connected today
FAQ
We build each adapter to the airline’s own published schema and version — Ethiopian Airlines, for example, is integrated on IATA NDC 17.2. Tell us what you publish and we work to it.
Each agency’s own. Credentials are stored per agency in a managed key vault, so every booking is made under that agency’s commercial agreement with you.
Yes. Exchanges, voids and refunds are handled on the order inside TravviseConnect, with your penalties and amounts shown before the agent confirms. Each service is switched on once it passes testing with you.
No. Ticketing is always a manual agent step and never happens automatically after the order is created.
Yes. We connect directly to your NDC API or through your chosen aggregator; Qatar Airways is connected through Farelogix today.
Your API guide, test credentials, your certification cases and a technical contact. We take it from there and keep your team updated through certification.
Talk to our distribution team in Doha.