TIXNGO is designed to be a standalone product to ensure mobile delivery, but we provide advanced integration with S-360.
In case of S-360 integration, S-360 is the Master for tickets issuing, meaning that once a ticket is issued and injected to TIXNGO, we must insure that, at any time, tickets statuses are aligned between both tools.
Summary of the possible actions to a ticket in a S-360 integrated TINXGO context
Organizer activities | Customers activities | |
---|---|---|
S-360 | Event management (sales, rescheduling, relocating, cancellation, …)
→ S-360 Back-Office | Tickets management
→ S-360 Ticketshops & S-360 Back-Office |
TIXNGO | Tickets management :
→ TIXNGO Back-Office | Tickets management :
→ TIXNGO Mobile App / TIXNGO Wallet |
Overview of the interface
The interface provides 4 functions :
- Tickets external printing pushes the designated tickets to the TIXNGO aka "Tickets injection".
- Retrieve ticket status from TIXNGO retrieves information from TIXNGO about the ticket (status, holder) and stores it inside S-360 aka "Feedback interface".
- Push cancelled and invalidated tickets pushes tickets that have been cancelled or invalidated since the last execution to TIXNGO in order to remove them from the spectator's Mobile Wallet.
- Push controlled tickets pushed tickets that have been controlled since the last execution to TINXGO in order to hide the QR code from the spectator's Mobile Walle
Configuration of the interface
For extensive documentation about the interface, please refer to the official page : SecuTix 360 to TIXnGO interface
Global / Custom Parameters
The interface behaviour can be tweaked by using Custom Parameters. These parameters are defined in the General tab of the interface
For the full list of available parameters, please refer to the section "Customer parameters" of the official page or click here.
Injection
S-360 is able to customize the json data sent to TIXNGO using a specific ticket template that contains all the formatted data.
Through the ticket template editor’s predefined syntax, configure custom variables which will then be mapped to TIXNGO Ticket Injection JSON variables and overwrite the data previously set via the comfort variables and the ticket injection batch interface.
For more details on the available variables, see the page Variable Details