Theme Parks API Overview

\<font color="#b6c7cb">\</font> topic type concept purpose theme parks api overview, differences, and hashing requirements audience api integrators and client developers applies to theme parks clients implementing via api does not apply to any other industry or theme parks clients who opt for a non api integration the theme parks api supports transactions involving theme park admissions and packages , built on the shared core model and extended with admissions/ticket package context what makes theme parks different theme parks transactions often rely on venue context (park/venue identifiers) ticket counts and pricing (number of tickets, total ticket price, ticket currency) package context (package id/class/description) per ticket guest context (guest name, age classification, ticket class, annual pass flags) these structures allow admissions and package purchases to be evaluated with the right contextual signals hashing requirements the retail 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 theme parks api fields https //atlas accertify com/public apis/us theme parks path view field requirements, paths, and try it out!