Skip to main content
The Offers & redemptions page manages redemption codes. A code grants access to one ticket type: the holder can register for that ticket even when the ticket is hidden or registration is closed. It is also the only way into a hidden guest ticket.
A code grants access, never a seat. Capacity and sale windows still apply — a valid code against a sold-out ticket is still sold out. To guarantee places, give the guest ticket enough capacity of its own.

​
Generate codes

1

Choose the ticket type

Choose Generate codes and pick the ticket type each code will redeem. Create the ticket type first — often a hidden one dedicated to invitees.
2

One custom code, or a batch

Enter a custom code (for example, VIP2024 — letters, numbers, hyphens) to create exactly one, or leave it empty and set How many to generate up to 500 random codes in one batch. A batch can carry a shared label (“VIP partners”) so campaigns can be told apart.
3

Set uses and expiry

Choose uses per code — single use, a set number, or unlimited — and optionally an expiry (local time at the event; empty means no expiry).
4

Share

Use Copy link on any code: the link is your event’s page address with ?code=… appended, for your site to pick up and pass into the checkout session. Without a page address the console offers the raw code for the visitor to type in.

​
What a valid code bypasses — exactly two things

  1. Hidden-type visibility — it reveals a hidden ticket to its holder.
  2. “Registration is closed” — the holder can register when every published ticket is closed.
Nothing else. Capacity, the sale window, and approval review all still apply.

​
Use counting

Uses are counted from live registrations that carry the code — not a separate tally. Consequences:
  • Cancelling a registration releases its use. A single-use code whose registration was cancelled works again.
  • If a pending registration is rejected by the organizer, that use is released too.
  • The list shows uses so far against the limit; a spent code stops validating.

​
What the visitor sees

Every failure looks the same. A misspelt code, a disabled code, an expired code, a fully spent code, or a code pointing at a ticket that is no longer published — the visitor sees only that the code is not valid. Which case they hit is never disclosed, so a code is never a way to probe the event’s configuration.

​
Rules to know

  • Per-event unique and case-insensitive. vip2024 and VIP2024 are the same code; two codes in one event cannot share a name.
  • Codes are disabled, never deleted. Disable stops future redemptions immediately; existing registrations stay. Re-enable later if needed.
  • A code can carry its own perks, added on top of the ticket type’s perks — the same code can grant an invitee a lounge pass the ordinary ticket does not include. See Perks.
  • Already registered? No double-booking. Someone registered who submits again with a code — even a spent one — is acknowledged as already registered, never sold a second seat and never shown an error. See Orders.
  • The code’s page keeps a history — created, redeemed, cancelled — so each redemption can be audited.
  • A code can carry a discount — a percentage or a fixed amount off the ticket it unlocks, applied on the checkout page and shown on the order. A 100% discount produces a free order.
Pattern for guest lists: create a hidden ticket type sized to the guest allocation, then generate one single-use code per guest. Capacity guards the allocation; single use guards each invitation.

Ticket types

Hidden visibility, capacity, and sale windows — what codes unlock and what they don’t.

Perks

Extra perks a code stacks on top of the ticket’s own.