Travel Extension Overview
4 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 the universal travel api extends the universal api shared transaction model for multi component travel purchases travel transactions may include combinations of flights, lodging, vehicle rentals, cruises, activities, agency information, and insurance information within a single request travel extension model the universal travel api may extend the shared transaction structure with flight information lodging information car rental information cruise information activity information agency information insurance information \<font color="#386b84"> note \</font> see travel complete request structure docid\ lozpgnfpwzglaocaouras for the full path 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 pre authorization risk score docid\ njpytoz70gavgnabx1khj travel post authorization risk score docid\ apflu nm2y8gg6ozqrjln travel authorization update docid 7wlyssovzkxptggclwnew travel fulfillment update docid\ f1xuv yfydbcgfwxcqh6y travel chargeback update docid\ yxttkjdcupc rx baqkd