Conny

Ticketing sites

Bringing your attendees in from where you sell tickets.

Conny never sells tickets. People book wherever you already sell them, and Conny reads who has booked, so everyone on your list gets their invitation and badge without you typing a name.

There are two ways in. If your ticketing site gives you a read-only key, an organisation admin saves it once on Host, Ticketing, links each event, and Conny brings in new bookings every hour. Otherwise, export your attendee list as a CSV file and upload it on Invites, as often as you like.

What Conny reads, and keeps

  • Each attendee's name and email address. Nothing else: no phone numbers, addresses, answers or payments.
  • Only people who aren't on the event's list already. Everyone else is left exactly as they are.
  • Nothing is emailed when people come in. Invitations go when they're sent from Invites.
  • Your key is encrypted before it's stored, nobody can read it back in Conny, and only the last four characters are shown so you can tell which key is saved. Remove it on Host, Ticketing whenever you like.

Sites you can connect

Humanitix

You'll need: Public API key

  1. Sign in to Humanitix as the account that runs your events.
  2. Open the account menu at the top, then Account, then Advanced.
  3. Under Public API key, generate a key and copy it.

The key only reads: it can't change or sell anything. Generating a new one stops the old one working, so if you use the key somewhere else too, paste the new one into Conny as well.

Humanitix: public API, opens in a new tab

TryBooking

You'll need: API key and secret key

  1. Sign in to TryBooking and open your Dashboard.
  2. Go to Integration Tools, then API Key Management.
  3. Choose Generate API Key, give it a name such as Conny, and copy both the API key and the secret key.
  4. In Conny, choose the region your TryBooking account is in (New Zealand for most of us).

TryBooking's reporting API only reads bookings.

TryBooking: API, opens in a new tab

Ticket Tailor

You'll need: API key

  1. Sign in to Ticket Tailor and open the box office you sell from.
  2. Go to Box office settings, then API.
  3. Generate a new key, and give it access to reading events and issued tickets only.
  4. Copy the key.

A Ticket Tailor key reads only the box office it was made in.

Ticket Tailor: connecting to the API, opens in a new tab

Eventbrite

You'll need: Private token

  1. Sign in to Eventbrite as the organiser.
  2. Go to Account Settings, then Developer Links, then API Keys.
  3. Create an API key if you don't have one, then copy its Private token.

Eventbrite has no read-only token: its private token can do anything your account can. Conny only ever reads with it, but if that's more than you'd like to hand over, export your attendee list instead and upload it on Invites.

Eventbrite: API keys, opens in a new tab

Then, on Conny: Host, Ticketing, choose the site, paste the key, and save. Conny checks the key works before it keeps it. On Invites, link each event to its event on the ticketing site.

Sites with no key: upload the list instead

These don't offer organisers a key Conny can read with, as far as we know. Upload the export on Invites, Add people. Conny finds the name and email columns itself.

  • iTICKET. Download your attendee or sales report, save it as CSV, and upload it.
  • Eventfinda. Download your attendee or sales report, save it as CSV, and upload it.
  • Flicket. Download your attendee list, save it as CSV, and upload it.
  • Ticketek, Ticketmaster, Moshtix. Ask your account manager for the attendee list as a spreadsheet, save it as CSV, and upload it.
  • A form or a spreadsheet of your own. Save it as CSV with a name column and an email column, and upload it.

Using a site that isn't here, or one of these has a key now? Tell us from the feedback tab and we'll look at adding it.