Site · Events
Events Overview
Last updated 18 November 2026
Plan and sell events: events, tickets, venues, fields, webhooks and QR check-in.
Insites Events helps you plan and sell events, in person or online. You set up each event with its venue, pricing and content, sell tickets, check people in with QR codes, and track revenue against expenses. Events works with the CRM for attendees and with Ecommerce for orders.
What is in Events
| Area | What it holds |
|---|---|
| Events | Each event, with dates, venue, pricing, speakers, sponsors, FAQs and expenses |
| Tickets | Tickets across every event |
| Venues | Places, with their areas |
| System fields | Dropdown options such as event category, industry and venue type |
| Custom fields | Your own fields on events |
| Webhooks | Addresses told when an event, ticket or expense is added |
| QR check-in | Scan tickets at the door |
Webhooks
Events sends three webhooks, all on create only: event_added, event_ticket_added and event_expense_added. Each is a plain JSON POST with no signature, so keep the receiving address private or check where requests come from.
From code
The Events API at /events/api/v2/ covers events, expenses, FAQs, speakers, sponsors, tickets, system fields and venues. Pricing divisions and tiers, venue areas, imports, exports and QR check-in are in the admin only. Send the raw site API key in the Authorization header.
On the docs.insites.io site, a read-only query on 1 November 2026 found no events, venues or tickets.
Common mistakes
- Expecting a webhook when an event changes. Events sends them only when something is added.
- Relying on the Events API for pricing. Pricing is set in the admin.
- Selling tickets outside Ecommerce and expecting them on an order. Ticket records link to the Ecommerce order they were bought in.