Ticketing Extension Overview
The Universal Ticketing API extends the Universal Fraud API shared transaction model with event, venue, and ticket information.
Ticketing transactions combine a shared transaction foundation with event-specific structures that describe what is being purchased and when it will be used.
Ticketing Extension Model
The Universal Ticketing API adds:
- Event Information
- Ticket Information
- Agency Information
- Insurance Information
- Activity Information
Note: See Ticketing Complete Request Structuremm for the full path.
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 RequirementsHashing Requirements (Constraint) and Accertify Hash AlgorithmAccertify Hash Algorithm (Reference).