Setting up an event

Events → New event opens a three-tab form: Event information, Event description, and Tickets. Save lives in the top bar — it 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 date, each with its own time label (e.g. 7:30 PM) and location label. Stops can pull a venue from your Venues directory — 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.
  • 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.
• Reminder — optionally email ticket-holders a reminder a chosen number of days (0–30) before the event.

The public page URL comes from the title and date (e.g. /t/nbt/events/the-long-run-2030-04-05). Once you publish, the URL is locked — retitling later doesn't break links you've already shared.

Event description

A rich-text editor for the full pitch — formatting and inline images are fine (up to 20,000 characters). It's shown on the event's public page and returned via the API, so keep it self-contained.

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.
• 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, if you want to prevent bulk purchases.
• 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 to all dates to fan a type out across every performance.

Type names must be unique per date.

Before it can sell

A published event with published ticket types still needs your Stripe connection before the Buy tickets button appears. Everything else — the event page, the listing, embeds — works without it.