Skip to main content

Read-only PNR/booking history lookup, for an agency agent looking up an existing booking. Not part of the purchase flow.

POST 
/api/v1/FlightBooking/History

Ticketing strangler Phase 3 (2026-09-02, docs/MICROSERVICES_DECOMPOSITION.md) -- booking history/PNR lookup, a secondary support feature (an agency agent looking up an existing booking), not part of the active purchase flow. Ports legacy's CraneReadBookingHistory only: confirmed by direct read to be the one real, read-only, live-consumed history operation. FlightTicketHistory is confirmed dead-response (dispatched by the frontend but no reducer/selector reads its success payload) and CraneFlightPNRHistory is confirmed dead code (zero frontend callers) -- neither ported. Deliberately NOT replicated: FlightTicketHistory's Videcom branch, which isn't a history read at all -- it fabricates and POSTs a live segment-sell command against real inventory, then the frontend that calls it discards the result. Videcom items in this batch therefore never reach ondgo.gds at all -- there is nothing safe to call -- and are simply omitted from the response, exactly mirroring legacy's own CraneReadBookingAsync (which only appends an entry to its response list on a real success, never a placeholder for a skipped/failed item).

Pure passthrough like Search/Extras's Crane leg: no wallet, no persistence, no orchestrator/Hangfire involvement -- this is a read, not a purchase step.

Request​

Responses​

OK