An App Key is what is entered into each of the devices you intend to use for scanning tickets. It is what will tell the device which tickets to validate and what permissions to lock or unlock. In order to easily scan attendees in at your event, you'll first want to create an app key.
You can create multiple app keys and assign certain ticket levels to some scanning devices, but not others. For example, maybe you have a VIP entrance where you'd only like VIP tickets to be validated and other scanning devices that you'd like to validate General Admission and VIP.
You can also limit access when creating an App Key. Maybe you have some admins you'd like to grant full access vs some volunteers who you'd only like to be able to search and scan tickets. We'll walk you through all of the options below.
If you need to download the TicketSpice scanning app, you can do so here:
Jump to...
FAQs
NOTE: If you are using an apple device, the TicketSpice scanning app is compatible with iOs 13 and above.
Create an app key
From the Pages screen, click the pencil icon on the page you'd like to create an app key for
Hover your mouse over the Onsite tab at the top
Select Ticket Scanning from the dropdown
Click the Create App Key button
Name your app key - This is just for internal reference and will not show publicly. It will show in reports and in your app key listing. This can be descriptive like "General Admission Entrance", "Volunteers only", etc.
Limit Volunteer Access
App key for volunteers with limited access - When this is enabled, it will limit the access these volunteers will have. Instead of having full access to reports and the full list of attendees, this feature will limit anyone logged in with this app key to only be able to search and scan tickets.
Full access vs Volunteer access
Edit orders in-app
Allow team to edit orders from app - When this is enabled, anyone logged in with this app key will be able to edit an order while scanning people in. This is useful if someone brings a friend and they need to add a ticket to their order. Or, if they'd like to add on and pay for a merchandise item, etc.
How editing an order looks in-app
# of Scans
# of Scans - This is how many times a ticket is able to be scanned. This number is per ticket, not for your scanning device total. For example, if you have sold 500 tickets and you set # of Scans to be 1, then each of those 500 tickets can be scanned 1 time. It will show invalid if someone tries to have their ticket scanned a second time. # of Scans is most commonly set to 1.
Frequency
Frequency - The Frequency can be set to Total or Per Day. Total means the total number of times the ticket can be scanned. So if the # of Scans is set to 1 the ticket will only be able to be scanned in 1 successful time. Another example would be, you allow people to attend 3 times in a month. You can set the # of Scans to be 3 and Frequency would be set as Total. Then that person could scan in a total of 3 successful times.
If the Frequency is set to be Per Day and the # of Scans is set to 1, then that person could scan in successfully once per day. This is often used If someone purchased a week pass to an event.
Sample Scenarios
# of Scans | Frequency | Result |
1 | Total | Attendees can successfully scan into your event a single time. (This is the most common setup) |
1 | Per Day | Attendees can successfully scan into your event one time per day. (Maybe you sell a weekend pass and you'd like people to successfully scan in once each day) |
2 | Total | Attendees can scan in two successful times to your event. (Maybe you allow people to pick two days to attend your week-long event) |
2 | Per Day | Attendees can scan in twice per day. (Maybe you have a morning and an afternoon session and want people to be scanned in successfully at the start of each session) |
Additional Options
Require a Photo
Requiring a photo can be handy if you offer season tickets, or often have people exiting and re-entering the event. Maybe you snap a photo and then they don't need to show ID each time they return. The photo will now appear each time you scan their ticket in the future, validating it is indeed the ticket holder. This also helps prevent people from sharing their ticket with others.
Limited Availability by Date
Limiting availability by date in the app key will set a timeframe in which this app key applies. Maybe you have a month-long event, but the VIP pass is only valid for the first week. You can create an app key that validates VIP until the end of the first week for VIP, but allows for General Admission to be validated through the rest of your event.
Mobile Pay Pass
Mobile Pay Pass is our app that allows you to to make cashless sales on-site at your event! Sell things like merchandise, upgrades, experiences and more! It allows your attendees to use the same ticket they entered the event with. When that ticket is scanned, they will enter a 4 digit passcode and can charge the card on-file. Learn more here.
Once you have your app key configured how you'd like it, click the Save button.
Once you save your app key, you will see a screen that looks like this. It will display the app key (you will type that into the app), the name and configuration details.
FAQ's
Q: What iOs is the TicketSpice ticket scanning app compatible with?
A: If using an apple device, the TicketSpice app is compatible with iOs 13 and above.
Q: What Android version is the TicketSpice ticket scanning app compatible with?
A: If using an Android device our ticket scanning app is compatible with version 8 or above.
Q: Can I create multiple app key's for the TicketSpice ticket scanning app?
A: Yes, you can create multiple app keys. This can be necessary if you want an app key for volunteers that offers limited access and another app key for admins that has full access. Or, if you'd like one app key for the VIP only entrance and another app key for General Admission for example. NOTE: One scanning device can hold up to 5 app keys.