CodeREADr Ticket Scanner App
IWannaTicket supports multiple ways of integrating with CodeREADr. CodeREADr is a ticket scanning app for Android and Apple. When you start CodeREADr to scan some tickets, it connects to a particular service on the CodeREADr site. The service represents your event / event date.
Postback Integration
In a postback integration, we create a service in CodeREADr. When you scan using the app, the scan request goes to the IWannaTicket server which responds with "yes let them in", "no that ticket has already been used", "yes that's a membership card", or any of a myriad of different responses. Upon a successful scan, an "admit" scan is recorded against the ticket.
IWannaTicket needs to set up postback for you. Postback won't work if you don't have internet connectivity at your event.
Database Integration
In a database integration, IWannaTicket sends tickets to CodeREADr's servers as they are sold, and CodeREADr stores them in a database. We will normally set it up so there is one database for each event date. IWannaTicket creates a service against each database, and the app connects to the appropriate service. Then the app downloads the database and can check tickets against that database without internet connectivity.
The service may optionally be configured so that when a ticket is admitted IWannaTicket is notified using a mechanism very much like postback. That allows admit scans to be recorded.
Lookup
Sometimes customers arrive at the event without their tickets. IWannaTicket's CodeREADr integration has a facility to look someone up by information other than their ticket.
John's car broke down on the way to the event and he is late. His sister has the tickets, but she entered without waiting for him. When John arrives at the gate he tells the scanning person his sister's name, and as that name is on the sale and there is an unadmitted ticket, everyone figures that's John's ticket and he is admitted using it.
The lookup system tries to be as clever as it could possibly be. If you look someone up and they have tickets for some other event date, it will tell you. If they have a ticket but it's actually for last year's event, it will tell you. If someone theoretically should not be admitted, but you want to admit them anyway, you can do that. The scan will be recorded against the event date with the ticket that was used for admission no matter where it came from.
Advanced Features
By default, CodeREADr databases and services are created in IWannaTicket's CodeREADr account. If you have your own CodeREADr account, IWannaTicket can create databases and services in your account. We just need to know your API key.
IWannaTicket has the ability to support an unadmit service via postback. This is just like a regular service, except when a ticket is scanned we record an "unadmit" scan against it. And of course, we don't check that it's allowed to be admitted, as it's not asking to be admitted. This is useful if you need to monitor when people leave the event. Note that you can't do both admit and unadmit on one device - one device connects to one service, which must be either admit or unadmit.
IWannaTicket can also provide a population URL for an event date. You can look at this URL to see how many people are currently admitted to the event. This may be used to comply with venue restrictions.