NDC for travel agents
NDCTerm gives agents a practical way to work with NDC content: multi-airline shopping, branded fares, seats, ancillaries, order servicing, and GDS-familiar commands in one terminal.
Built for the agent workflow
Most NDC products are either airline portals or developer APIs. NDCTerm is different: the primary user is the agent at the keyboard, moving from search to booking to servicing without writing code or learning another portal.
| Need | Typical NDC API | NDCTerm |
|---|---|---|
| Primary user | Developer or product team | Travel agent |
| Interface | API docs, implementation work, custom UI | Cryptic command terminal |
| Search and pricing | Build your own UI | 15NOVJFKLAX/SHOP, WP |
| Booking | Order API integration | ER or 2ER |
| Post-booking servicing | Separate workflows to implement | Retrieve, seat, service, split, cancel, refund |
| Training fit | Engineering-led | GDS-fluent agents |
What agents can do
Shop NDC offers
15NOVJFKLAX/SHOP/AA
Search live airline offers, including fare brands and NDC-specific content.
Price and compare
WP
Return priced offers with baggage, change rules, and branded fare details.
Book the order
2ER
Create the airline order from the selected priced offer.
Service after sale
*ABC123
Retrieve existing orders, then add seats, services, split passengers, or cancel with a quote.
Where NDCTerm fits
Use your GDS when…
- You need mature hotel, car, rail, queue, or back-office workflows.
- The airline or market is still mostly EDIFACT.
- Your agency has deep mid-office automation tied to an existing GDS contract.
Use NDCTerm when…
- The fare, ancillary, or servicing workflow is better through NDC.
- You want direct NDC content without forcing agents into airline portals.
- Your agents already think in cryptic and need speed, not another form-heavy UI.
FAQ
>What is NDC for travel agents?
NDC gives travel agents access to airline offers, branded fares, seats, bags, and servicing workflows through airline APIs instead of only through legacy GDS EDIFACT content. NDCTerm makes those workflows usable through GDS-familiar commands.
>Do travel agents need developers to use NDCTerm?
No. NDCTerm is an agent-facing terminal, not a developer API. Agents search, price, book, ticket, retrieve, service, and cancel bookings by typing commands.
>Does NDCTerm replace a GDS?
For NDC-heavy air workflows, NDCTerm can be used directly. For agencies with legacy hotel, car, rail, queue, or back-office workflows, it can sit alongside Sabre, Amadeus, Travelport, Apollo, or Galileo.
Try an agent-first NDC workflow
NDCTerm is in limited release for agencies and agents working with NDC content.
Request AccessRelated: NDC servicing · Seats and ancillaries · Commands