Legacy Airline API Overview
3 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 \<font color="#386b84"> legacy api notice \</font> this api is part of the legacy fraud api framework and is maintained for compatibility with existing implementations new integrations should use the universal fraud apis instead the universal fraud apis provide a shared core transaction model consistent request and response contracts industry specific extensions unified documentation and onboarding ongoing feature investment use this legacy api documentation only if you are maintaining an existing legacy fraud api integration you have not yet completed migration to universal fraud apis accertify has specifically directed your implementation to remain on the legacy api framework for new implementations, start with universal fraud apis overview 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 us airline fields docid\ mwidaxbrrjspxvu16qraz