Ticketing API Overview

\<font color="#78b5c7">\</font> topic type concept purpose ticketing api overview, differences, and hashing requirements audience api integrators and client developers applies to ticketing clients implementing via api does not apply to any other industry or ticketing clients who opt for a non api integration the ticketing api is built for transactions involving ticketed events , where event metadata and seat/ticket context may influence risk evaluation it uses the shared core model and adds event/ticket specific structures what makes ticketing different ticketing commonly relies on event identity and timing (event id, type, name, start time) venue context (venue identifiers and related address references) seat/ticket details (section, row, number of seats, contiguous seat blocks) these fields provide important context about what is being purchased and when it will be used hashing requirements the ticketing 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 ticketing api fields https //atlas accertify com/public apis/us ticketing path view field requirements, paths, and try it out!