Turkish Airlines TKCONNECT NDC Entegrasyon Rehberi

TKCONNECT, Turkish Airlines'ın NDC/direct distribution modelini agency UI, aggregator ve direct API seçenekleriyle sunar. Entegrasyon tasarımında “THY flight search API” gibi tek endpoint abstraction yerine offer/order ownership + servicing capability esas alınmalıdır.

Topology

Seller
  -> direct TKCONNECT NDC
  -> aggregator
  -> agency UI
        |
        v
Turkish Airlines offer/order lifecycle

Direct API ve aggregator aynı airline supply'a erişebilir ama auth, certification, capability ve servicing davranışı aynı olmak zorunda değildir.

Canonical boundary

Core model en az şunları ayırmalıdır:

• itinerary,
• offer,
• fare family/brand,
• baggage,
• ancillary,
• provider offer reference,
• order/booking reference,
• ticket/document state,
• servicing capability.

Airline source identity normalize edilirken kaybedilmemelidir.

Search → Offer → Order

SEARCH
 -> OFFER
 -> SELECT
 -> REVALIDATE if required
 -> ORDER/BOOK
 -> PAYMENT/TICKET
 -> RETRIEVE
 -> CHANGE/CANCEL/SERVICE

Search sonucu booking guarantee değildir. Offer expiry ve price/fare conditions booking öncesi tekrar doğrulanmalıdır.

Idempotency

Order/create timeout'u proven failure değildir:

CREATING -> CONFIRMED
         -> REJECTED
         -> UNKNOWN -> retrieve/reconcile

UNKNOWN durumda duplicate create uygulanmamalıdır.

Observability

• search latency,
• offer count,
• offer expiry,
• revalidation change rate,
• order unknown-state age,
• ticketing success,
• servicing failure,
• reconciliation drift.

Production checklist

• access/certification path doğrulandı
• direct vs aggregator source explicit
• offer/reference korunuyor
• fare family + baggage normalize ediliyor
• order UNKNOWN recovery var
• servicing capability matrix var
• ticket/document state booking state'ten ayrı