Instance · Events
Event Tickets Introduction
Last updated 1 November 2026
Tickets for your events: types, pricing, attendees, statuses, PDFs and QR codes.
Tickets are how people get into your events. Each ticket belongs to an event and is sold against one of its pricing divisions and tiers. It can be assigned to a person and carries a QR code for check-in. Its PDF can be printed or shown on a phone.
Where to find tickets
In the admin, open Events and choose Tickets to see tickets across every event. Tickets for one event are also on that event.
What a ticket holds
| Part | Examples |
|---|---|
| Type | Individual or group. Group tickets share a group ID |
| Price | The pricing division and tier it was sold under |
| Attendee | A CRM contact, or a name, email, job title and phone typed in |
| Status | Allocation, confirmation and attended status |
| Extras | Dietary notes, who bought it and for which company |
| Order | The Ecommerce order it was bought in |
How tickets are created
Creating tickets lowers the remaining count of the pricing division and generates each ticket's PDF. It also sends one event_ticket_added webhook for the batch. The Events API creates tickets in batches at /events/api/v2/events/:uuid/tickets; if any one ticket in a batch is rejected, the whole response is an error that lists the reason for each ticket.
Assigning a person to a ticket regenerates its PDF, so the attendee's name is on it.
Note
The docs instance has no tickets, so none was read. The fields come from the Events module reference in the Insites Logic Engine.
Common mistakes
- Creating tickets before the event has pricing divisions and tiers. Each ticket needs both.
- Forgetting the group ID on group tickets. They are refused without it.
- Sending a ticket PDF before assigning the attendee. The PDF is regenerated on assignment.