Skip to content
- Venue (also “promoter” or “org”): the entity that sells tickets. It has a public name, a URL slug, and a Stripe account attached to receive the money.
- Team: the people who can manage your venue. Three roles:
owner (you), admin (manages events and credits) and staff (reads reports and registers validators).
- Event: a show with date, location, banner, description and ticket types. You create it as
draft, work on it as long as you want, and publish when ready.
- Ticket type: each ticket variant (
entry, combo, seat, consumption) with its own price, capacity, visibility and translations. An event needs at least one visible type before it can be published.
- Order: a purchase of one or more tickets by a single buyer. Each ticket inside the order becomes its own rotating QR.
- Credit: what Boletra charges you per issued ticket. 1 credit = 1 ticket. Credits never expire. Your account starts with 50 free credits every month that are consumed before any purchased balance.
- Balance vs free monthly: the Credits dashboard shows both separately. The system spends from the free monthly first and only touches the purchased balance once the free pool runs out. The free pool resets on the 1st of every month UTC.
- Rotating QR: the code your buyer sees. It refreshes every 30 seconds so screenshots don’t work.
- Validator / Scanner: the mobile app your staff uses at the door to scan QRs. Works offline if pre-synced before the event.
- Public discovery (
/discover): the open listing of events available on Boletra. The moment you publish an event, it appears there automatically.
- UTM attribution: every public link understands
utm_source, utm_medium and utm_campaign. We store them on the order and the Sales page aggregates them by channel.
