Airline API Overview
3 min
\<font color="#78b5c7">\</font> topic type concept purpose airline api overview, differences, and hashing requirements audience api integrators and client developers applies to airline clients implementing via api does not apply to any other industry or airline clients who opt for a non api integration the air api is designed for transactions where flight itinerary context materially affects fraud evaluation in addition to the shared core fields (transaction, account, payment, device, addresses, and so forth), air adds structures for pnr/itinerary, segments, and passengers what 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 api fields https //atlas accertify com/public apis/us airline path view field requirements, paths, and try it out!