Legacy Travel API Overview
3 min
\<font color="#b6c7cb">\</font> topic type concept purpose legacy travel api overview, differences, and hashing requirements audience api integrators and client developers applies to legacy travel clients implementing via api does not apply to universal apis, any other industry, or travel 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 travel api is intended for transactions where the purchase represents a travel itinerary that may include multiple components (air, lodging, rental, cruise, activities, agency, insurance), in addition to the shared core event model what makes travel different travel transactions can be future dated (book now, consume later) multi component (flight + lodging + rental + activities) third party booked (agency/ota involvement) the travel api supports optional structures for lodging reservations, guests car rental details cruise details activity/excursion details agency details insurance policy context hashing requirements the travel 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 travel fields docid\ pxwqjbej ltczkttbo9gf