Travelport NDC Integration Guide

Travelport JSON Air exposes GDS and NDC content through the same API family while preserving source identity. Search can explicitly request source types and responses identify content through Offer/ContentSource.

Search source selection

{
  "contentSourceList": ["GDS", "NDC"]
}

NDC access requires provisioning by both Travelport and the airline.

Offer lifetime

Travelport documents different search-reference lifetimes for GDS and NDC, while NDC offer time limits can vary by carrier. Preserve expiry state in the core model.

Booking

Search
 -> AirPrice
 -> Workbench
 -> Add Offer
 -> Commit
 -> Reservation
 -> Ticket/Service

A workbench is a short-lived mutable context, not booking identity.

GDS/NDC servicing differences

NDC fulfillment, ticketing and post-booking servicing are more directly controlled by the airline. Void/exchange/refund workflows should not be assumed identical to GDS.

Identity

Travelport passive PNR and carrier NDC reservation locator can coexist. Do not collapse both into one field.

Failure modes

• expired search reference,
• expired NDC offer,
• wrong content source,
• workbench expiry,
• passive/carrier locator confusion,
• unsupported carrier servicing.

Observability

Track GDS/NDC offer mix, offer expiry, workbench age, commit unknown state, ticketing latency and servicing errors.