Setting up an event

Events → New event opens a three-tab form: Event information, Event description, and Tickets. Save sits in the top bar and only appears once you've changed something.

Event information

• Title and category — the category is your own label (e.g. Drama, Comedy, Kids) shown on the listing.
• Date mode — one date or several:
  • Single: one date and start time.
  • Multiple: add a stop per performance (two stops can share a date for a matinee and an evening show), each with its own time label (e.g. 7:30 PM) and location label. Stops can pull a venue from your Venues directory (shown when your venue produces shows across more than one location) — picking one snapshots its details onto the stop. Up to 100 stops.
• Location — the venue/location line shown to visitors (single-date events).
• Event image — JPG/PNG/GIF/WebP up to 500 KB, shown on the listing and detail page. Uploading the same image twice reuses the stored copy.
• Visibility:
  • Publish status — draft keeps the event invisible to the public; published puts it on your listing. Once a published event has sold tickets, the toggle is replaced by a notice: the event must now be cancelled rather than reverted to draft.
  • Private event — published but unlisted: reachable only by its link, with an optional event password. Private events never appear on your public listing or in the API.
  • Over 18 — flags age restriction on the public page.
• Audience — the event's mailing-list tags, applied to buyers who opt in so you can target campaigns later, plus a reminder email to ticket holders — on by default, one day before the event; set it anywhere from 0–30 days or switch it off.

The public page URL comes from the title and date (e.g. /t/nbt/events/the-long-run-2030-04-05); a private event gets a random number in place of the date, so its link can't be guessed. The URL is editable next to the title until first publish. After that it locks, so retitling later doesn't break links you've already shared.

Event description

A rich-text editor for the full pitch (up to 20,000 characters, formatting included). It's shown on the event's public page and returned via the API, so keep it self-contained. The toolbar gives you:

• Text formatting — bold, italic, underline, strikethrough, headings, block quotes, and left/centre/right alignment. Undo and redo live on the toolbar too (or Ctrl/Cmd+Z).
• Lists — numbered and bulleted, and they nest: press Tab in a list item to indent it, Shift+Tab to bring it back. Nesting is saved exactly as you see it.
• Links — select text and use the link button; paste or type a URL. Typing a bare URL links it automatically.
• Inline images — click the image button, drag a file into the editor, or paste one (JPG/PNG/GIF/WebP up to 10 MB; large photos are resized automatically for the web, so phone photos are fine as-is). You'll be asked for a short description of the image for screen-reader users. Leave it blank only if the image is purely decorative; the description can be edited later with the image selected.
• Image size and placement — select an image and drag its corner handles to resize it. The toolbar's placement buttons float it left or right (text wraps around it), centre it, or stretch it full width; click the active option again to clear it. Drag an image to move it elsewhere in the text.
• YouTube — paste a video URL to embed the player on the event page.

What you see in the editor is what the public page shows. Anything the editor can't produce (scripts, embeds from other sites, pasted-in exotic styling) is stripped when you save.

Tickets

Tickets are sold in ticket types (batches) you define per event — for example General admission $25 and Child $15, or a free ticket. Each type carries:

• Price (AUD, or mark it free) and an optional surcharge — buyers see the combined price. A free ticket type is claimable through the public checkout with no card step: buyers choose how many, confirm, and get their tickets by email like any paid order. Free tickets carry no per-ticket platform fee, and capacity limits apply exactly as for paid types.
• Capacity (ticket limit) — the number available. Checkout enforces it: once they're gone, they're gone, including while unpaid orders briefly hold seats.
• Order limit — the most one order can buy. Required, and it must be lower than the ticket limit.
• Publish status — a draft type is invisible to buyers; publish it when you're ready to sell. Publishing the event prompts you about still-draft ticket types so nothing stays accidentally unsellable.
• On multi-date events, each type belongs to a specific stop — use Copy batches to all dates to fan a type out across every performance (stops that have already sold are left alone).

Type names must be unique per date.

Discounts

Once tickets are enabled, a Discounts tab appears next to Tickets — the home for this event's discounts and voucher codes. On a saved event it lists the discounts this event carries, with each one's uses and the dollars it has given customers on paid orders. From there you can create a new discount with the wizard, edit or deactivate one, remove one from this event (the discount itself is kept), or opt into a discount another event already has via Add an existing discount. On a brand-new event the tab explains that discounts attach after the first save.

Discounts apply per event. A discount this event doesn't carry never applies here: its voucher code is refused at this event's checkout, and if no active discount is carried the voucher field doesn't appear at all. When the field does appear, buyers can Apply their code on the first checkout step to see the discounted total before reserving. Duplicating an event copies no discounts.

Before it can sell

A published event with published paid ticket types still needs your Stripe connection before anyone can buy them. Free ticket types don't wait for Stripe: an event with free capacity shows its Buy tickets button even before payments are set up, offering the free types only. Everything else (the event page, the listing, embeds) works without Stripe too.

Once it's published and selling, Tickets and delivery covers what buyers receive, and Cancelling & restoring covers changing your mind.