What is the difference of using OrderDetail API and TicketIssuanceNotify API

High-level difference

• TicketIssuanceNotifyis a push/webhook callback from PKFARE to the buyer partner.
• OrderDetail  is a query API that the buyer partner calls to fetch order details from PKFARE.

What they have in common

• Both are order-centric and use orderNum as a core identifier.
• Both can carry ticketing-related information such as pnr, passenger details, and ticket numbers.
• Both support post-booking lifecycle data rather than only simple booking creation.
• Both are POST-based and use structured request payloads.

Main differences

• Direction
  • TicketIssuanceNotify_V2: PKFARE actively sends the data to the partner’s webhook URL.
  • OrderDetail V13: the partner actively requests data from PKFARE.
• Purpose
  • TicketIssuanceNotify_V2: event notification after ticket issuance, reissue, change, or rejection.
  • OrderDetail V13: retrieve the current order snapshot, including journey, passenger, ancillary, and post-booking service order information.
• Trigger timing
  • TicketIssuanceNotify_V2: sent when ticketing is completed or when a request is rejected.
  • OrderDetail V13: can be called at any time to inspect the order state.
• Payload style
  • TicketIssuanceNotify_V2: notification-style payload with fields like status, rejectReason, informType, permitVoid, lastVoidTime, voidServiceFee, and detailed pnrList / passengers.
  • OrderDetail V13: query-style payload with includeFields and includeOrderTypes so the caller can choose what to retrieve.
• Scope of returned data
  • TicketIssuanceNotify_V2: focused on issuance result, mapping between PNRs and passengers/segments, and rejection reasons.
  • OrderDetail V13: much broader, including order status, journeys, passengers, solutions, ancillary bookings, schedule change history, check-in info, and related parent/post-booking orders.
• Status model
  • TicketIssuanceNotify_V2: uses a narrower business status set such as ISSUED, CHANGED, and REJECTED.
  • OrderDetail V13: exposes a richer order status model, including issuing, change, refund, void, review, and cancellation states.

Practical interpretation

• Use TicketIssuanceNotify_V2 when you want to receive ticketing results immediately and update your system proactively.
• Use OrderDetail V13 when you want to look up the latest authoritative order state or fetch detailed order information on demand.