--- title: Legacy Ticketing API Overview slug: legacy-fraud-apis/legacy-ticketing-api-overview createdAt: 2026-03-10T14:50:33.084Z --- ::::ExpandableHeading ### **Topic type: Concept** :::hint{type="warning"} **Purpose**: Legacy Ticketing Fraud API overview, differences, and hashing requirements. **Audience**: API integrators and client developers. **Applies to**: Legacy Ticketing clients implementing via API. **Does not apply to**: Universal APIs, any other industry, or ticketing clients who opt for a non-API integration. ::: :::: :::hint{type="info"} ******Legacy API Notice**: This API is part of the Legacy Fraud API framework and is maintained for compatibility with existing implementations. New integrations should use the **Universal Fraud APIs** instead. The Universal Fraud APIs provide: - A shared core transaction model - Consistent request and response contracts - Industry-specific extensions - Unified documentation and onboarding - Ongoing feature investment Use this Legacy API documentation only if: - You are maintaining an existing Legacy Fraud API integration. - You have not yet completed migration to Universal Fraud APIs. - Accertify has specifically directed your implementation to remain on the Legacy API framework. For new implementations, start with **Universal Fraud APIs Overview**. ::: The Ticketing Fraud 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 ::::LinkArray{contentSource="CUSTOM"} :::LinkArrayItem{headerType="IMAGE" headerImage="https://api.archbee.com/api/optimize/C_ua77kdJRrVi_Gd-0NCF/1KaZ5XArUZGzfCnDoUsDd-20260326-200546.png"} [US Ticketing Fields](docId\:YTFaQ5EYbbhUbId0IvolJ) ::: ::::