TicketType

Values are powers of two (bit flags), so multiple types can be combined.

Value	Name	Description
1	`VisitorTicket`	Visitor ticket
2	`ExhibitorTicket`	Exhibitor ticket
4	`ServiceTicket`	Service ticket
8	`OnsiteTicket`	On‑site / cash‑desk ticket
16	`PressTicket`	Press ticket
32	`ParkingTicket`	Parking ticket
64	`SpecialParkingTicket`	Special parking ticket

Exampel (bit combinations):

Visitor + Press ⇒ 1 | 16 = 17
Exhibitor + Parking ⇒ 2 | 32 = 34

SaleLegitimationStatus

(States for the sale‑related legitimation process)

Value	Name	Meaning
0	`New`	New
1	`Accepted`	Accepted
2	`Denied`	Denied
3	`InProgress`	In progress
4	`Shelved`	Shelved
5	`Questionable`	Questionable
6	`Incomplete`	Incomplete

SalePaymentStatus

(Payment state of the sale/transaction)

Value	Name	Meaning
0	`NotRequired`	No payment required
1	`NotPaid`	Not paid / payment outstanding
2	`Paid`	Paid
3	`NotRefunded`	Not refunded after cancellation
4	`Refunded`	Refunded
5	`RefundPending`	Refund is being processed by the payment provider (callback expected)
6	`PaymentProcessing`	Payment is being processed by the payment provider (callback expected)

DistributionChainType

Identifies the sales or distribution channel through which a ticket was sold. Values are powers of two (bit flags) and can be combined to represent multiple channels.

Value	Name	Meaning
0	`None`	No distribution channel assigned
1	`Internet`	Sold via an online shop or web-based sales channel
2	`OnSiteSale`	Sold directly at the venue or event location (box office)
4	`PreSelling`	Sold through an authorised pre-sale partner or advance ticket outlet
8	`OBS`	Sold via the Online Order System (OBS) / ESC integration
16	`Intern`	Issued internally, e.g. for staff, organisers, or complimentary purposes
32	`Direct`	Sold directly by the organiser without an intermediary
64	`DirectDistribution`	Distributed directly to the recipient without a formal sales transaction

TicketValidityType

Defines the temporal validity scope of a ticket — i.e. on how many days of a multi-day event the ticket grants access.

Value	Name	Meaning
0	`None`	No validity type defined; typically used for sub-event or session-based tickets
1	`OneDay`	Valid for a single specific day of the event
2	`MultipleDays`	Valid for a defined set of days, but not all event days
4	`MultipleDaysInSeries`	Valid for consecutive days within a defined series or block
8	`AllDays`	Valid for all days of the event (season / permanent ticket)

VoucherCampaignQuotaMode

Specifies how the usage quota of a voucher campaign is enforced — either without restriction, by limiting the number of redemptions, or by capping the total redeemed value.

Value	Name	Meaning
0	`Unlimited`	No quota restrictions apply; the voucher can be redeemed an unlimited number of times
1	`UsageLimit`	The campaign is capped by a maximum number of redemptions (`VoucherCampaignQuotaValue` defines the limit)
2	`ValueLimit`	The campaign is capped by a maximum total redeemed value (`VoucherCampaignQuotaValue` defines the monetary ceiling)

Typs