Travel API Overview
3 min
\<font color="#b6c7cb">\</font> topic type concept purpose travel api overview, differences, and hashing requirements audience api integrators and client developers applies to travel clients implementing via api does not apply to any other industry or travel clients who opt for a non api integration 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 travel api fields https //atlas accertify com/public apis/us travel path view field requirements, paths, and try it out!