Locked tickets

How to lock ticket types behind an access code or secret link

Jonny White avatar
Written by Jonny White
Updated over a week ago

Let’s say you have a number of VIPs who get discounted or free entry to your event, but you don’t really want the non-VIPs to know about it. Locked tickets allows you to lock tickets away so they are only visible to those who have the access code, or secret link.

How to set up locked tickets

1) When creating or editing a  ticket type, click the Advanced settings checkbox and you should see a Status dropdown.

2) From the Status dropdown select Access code required. A new text box will appear labelled Access code.

3) Enter an access code of your choice. This is the code that will protect your tickets so try to make it unguessable. (Note: The code is case sensitive).
4) Click Save on the ticket type.

That's it, it's all configured. You can create as many locked tickets as you like, and you can have them use the same code, so that a single code unlocks multiple ticket types.

How it looks for ticket buyers

On ticket selection a new option will appear for ticket buyers, labelled Do you have an access code? as shown below:

When they click this, they will be prompted to enter an access code. If they submit a valid access code then the relevant locked tickets will appear as shown here:

How to create a secret link that automatically unlocks ticket types

You may want to just send out a secret link, instead of a code, to save time. You can create a link to your event which will automatically apply the access code. Here's how:

Simply get your event link, and add ?a=code on to the end of it.

For example, if my event link was https://buytickets.at/jazzclub/317555 and my access code was letmein, then my secret link would be:

If you get stuck, let us know and we will be able to help.

How to password protect a whole event

If you would like to password protect your whole event, then we have a different setting for this. Please see this article: How do I make my event private?

Did this answer your question?