Event ticket purchase entity Represents purchased event tickets.Documentation Index
Fetch the complete documentation index at: https://memberpulseptyltd.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Fields
Field Registry (from workspace/sources/entity-registry.csv)
| Field | Type | Notes |
|---|---|---|
| memberProfile | ManyToOne | target: MemberProfile |
| event | ManyToOne | target: Event |
| status | ManyToOne | pending, confirmed, checked_in, cancelled; target: EventRegistrationStatus |
| registrationDateTime | datetime | - |
| paymentStatus | ManyToOne | pending, paid, failed; target: PaymentStatus |
| ticketType | string | - |
| checkedInAt | datetime | - |
| cancelledAt | datetime | - |
Relationships
| Relation | Type | Target Entity |
|---|---|---|
| event | ManyToOne | Event |
| purchaser | ManyToOne | Member |
Business Rules
- QR code generated on purchase
- Status changes: valid → used (on check-in)
- Refunded tickets cannot check in
Features
Event Ticket
Acceptance Criteria
Frontend
- Admin/client UI can view and manage
Event Ticketrecords where applicable.
Backend / API
- CRUD operations exist for
Event Ticket(create, read, update, delete/archive).
Permissions
- Access is restricted to appropriate roles (tenant-scoped).
Business Rules
- Fields and relationships documented on this page are enforced for
Event Ticket.
Error Handling
- Invalid payloads return field-level validation errors.