Airline Extension Overview
4 min
\<font color="#78b5c7">\</font> topic type concept purpose legacy airline api overview, differences, and hashing requirements audience api integrators and client developers applies to legacy airline clients implementing via api does not apply to universal apis, any other industry, or airline clients who opt for a non api integration the universal airline api extends the universal api shared transaction model with flight itinerary, segment, and passenger context airline specific information is supplied through the flightinformation structure while all core transaction data remains consistent with other universal fraud apis airline extension model the universal airline api adds the following to the shared transaction structure flight information flight segments passenger information \<font color="#386b84"> note \</font> see airline complete request structure docid\ ekwdysuxpcnrt7nyjkm1l for the full path makes airline different air risk assessment often depends on data that is specific to airline transactions, such as pnr / itinerary characteristics (ticket type, third‑party booking indicators) segment level context (route info, departure/arrival airports and timestamps, award ticket indicators) passenger level context (names, dob, loyalty, passport where applicable) these structures help the platform evaluate the event with the appropriate domain signals hashing requirements the air api follows the platform hashing rules fields designated as hash required must be hashed before submission, including giftcardnumber hashedpassword see hashing requirements docid\ yughwvl8eon7vcgswpcd3 (constraint) and accertify hash algorithm docid\ rkik1lb6euuwsz3sxpce (reference) field reference airline preauth risk scoring docid\ isnmplbjcrepqhtckcvd airline postauth risk scoring docid\ lygqehgccmngg y71rzql airline authorization update docid 5fijwaaqn khazvguyk3q airline authorization update docid 5fijwaaqn khazvguyk3q airline fulfillment update docid j l60hdksg 59noi49mf