If your organizer does not use S-360 to inject and manage tickets, TIXNGO provides another solution which is CSV injection to allow the organizer to inject up to 20'000 tickets at a time.
Inject tickets by CSV file
- Get an example template
Go to CSV Injection > Click CSV template at section 02
The minimal template contains all mandatory values that you need to inject tickets successfully to TIXNGO.
The full template contains all possible values that you can provide when injecting tickets to TIXNGO.
- Upload CSV file
Go to CSV Injection > Choose file > Submit
What you should know:
- Maximum tickets injected per CSV file: 20000 tickets
- This page list all CSV injection jobs that were sent by the organizer and its status (COMPLETED/FAILED/IN PROGRESS)
- Two templates are available, a minimal required fields template and a complete template with all possible ticket fields to help with the CSV setup.
- Organizers must check the output file to make sure the actual status of each ticket injected (ACCEPTED/REJECTED)
- Both uploaded CSV and output files are downloadable. Output file contains the details of ticket injected status as well as any error associated with its failure.
- The CSV file must be UTF-8 encoded
- All Dates must follow the RFC3339 standard for date & time
- For more details on each field of the file, please check here for better understanding.
Understand each fields in CSV:
| Variable Name | Variable Type | Value length | Variable usage/description |
| Gender | string | 1 char | M (male), F (female), U (unknown), X (other) |
| First Name | string | 50 char | Spectator's first name |
| Last Name | string | 100 char | Spectator's last name |
| string | 256 char | Spectator's email address | |
| Main Applicant | string | Boolean | Indicates if the spectator is the main applicant (SecuTix) for this ticket (default false). |
| Ticket ID | string | 256 char | Ticket ID in the TIXNGO system (a-z|A-Z / numbers / spaces / some special characters: *.-_+/()) |
| Barcode | string | 512 char | Plain text ticket barcode |
| Sorting Key | string | 256 char | Key used to order the tickets for the spectator following the alphabetical order. |
| Price | number | float | Price of the ticket |
| Currency | string | 20 char | Currency of the ticket's price |
| Category | string | 512 char | Purchase category (e.g. ADULT, CHILD, VIP, etc...) |
| Tax. Number | string | 256 char | Purchase taxation number |
| Ticket Image URL | string | 256 char | Display image as per URL on following ticket views: Ticket View, Ticket Detailed View |
| File ID | string | 256 char | SecuTix File ID (or any file ID that would list groups of ticket, e.g. injection file) |
| Event ID | string | 256 char | Event ID in the TIXNGO system |
| Event Name | string | 128 char | Name of the match |
| Site | string | 200 char | Site name displayed at the Ticket View and Ticket Detailed View under Address title |
| City | city | 200 char | City where the event takes place |
| Country Code | string | 200 char | country code for the address |
| Zip | string | 200 char | zip code for the address |
| Event Image URL | string | 256 char | Display image as per URL on following ticket views: My Tickets - "Group Image" |
| Start Time | string | must follow RFC 3339 date format | Displays Match date and kick-off time at the Ticket View and Ticket Detailed View |
| Ribbon Display Time | string | must follow RFC 3339 date format | Time at which a ribbon is displayed on the mobile app to notify spectator turn on Bluetooth |
| Transfer Group Id | string | 256 char | Transfer rules can technically be different for every ticket. Organizer might want to chose to have different transfer rules for different types of ticket (ex: Adult, child, VIP, etc…). This GroupID is the Transfer rules group ID representing a group of transfer rules applied to certain tickets. If Organizers want to apply the same rules to every tickets, by default this groupID is set to the EventID and every ticket will be in this group. |
| Max number of Ticket per receiver's Phone | integer | integer | Maximum amount of tickets per phone for this Transfer rules group id |
| Max Resell Price increase (in %) | integer | smallint | Maximum profit (price increase in %) of the original ticket price for a resell between spectator. |
| Max number transfer per Phone | integer | integer | Total amount of transfers per Phone (-1 feature is disabled). Counter is increased for every new transfer, but decrease on a Return. |
| Max number transfer per Ticket | integer | integer | Total amount of transfers per Ticket (-1 feature is disabled). Counter is increased for every new transfer, but decrease on a Return. |
| Assign Limit | integer | integer | Upper bound amount of transfer before the Assign function is disable (-1 means unlimited) |
| Allow Transfer | Boolean | Boolean | Enables or Disables transfer functionality for given match (Send menu item in the ticket view hidden or displayed) |
| Allow Transfer after Activation | Boolean | Boolean | Enables or Disables transfer functionality for given match for Activated Tickets (Send menu item in the ticket view hidden or displayed) |
| Allow Transfer after Control | Boolean | Boolean | Enables or Disables transfer functionality for given match for Controlled Tickets (Send menu item in the ticket view hidden or displayed) |
| Allow Return To Organizer | Boolean | Boolean | Enables or Disable allow everyone to release ticket to resale. |
| Allow Return To Organizer For Initial Spectator | Boolean | Boolean | Enables or Disable only Initial Spectator can release ticket to resale. |
| Resale Group Id | string | 256 char | Resale rules can technically be different for every ticket. Organizer might want to chose to have different resale rules for different types of ticket (ex: Adult, child, VIP, etc…). This GroupID is the Resale rules group ID representing a group of resale rules applied to certain tickets. If Organizers want to apply the same rules to every tickets, by default this groupID is set to the EventID and every ticket will be in this group. It is editable or used only if organizer resale setting is enabled |
| Allow Resell | Boolean | Boolean | Enables or Disables resale functionality for given match for all Tickets (Send menu item in the ticket view hidden or displayed) It is editable or used only if organizer resale setting is enabled |
| Allow Resell after Activation | Boolean | Boolean | Enables or Disables resale functionality for given match for ActivatedTickets (Send menu item in the ticket view hidden or displayed) It is editable or used only if organizer resale setting is enabled |
| Keep one Ticket Overall | Boolean | Boolean | Force ALL ticket wallet holders to keep at least 1 ticket per given Match |
| Keep one Ticket at Injection | Boolean | Boolean | Force ticket wallet holder to whom tickets were originally injected to keep at least 1 ticket per given Match. E.g. all his transfer guests will be able to forward all the tickets they received |
| string | 100 char | Support organizer define the resale price with three options A, B and C per Transfer Group Id:
It is editable or used only if organizer resale setting is enabled | |
| Min resale price decrease | number | float | Enable when Resale option A is selected. Min resale price decrease (in % of the initial price) of the ticket to be resold It is editable or used only if organizer resale setting is enabled |
| Min resale price amount | number | float | Enable when Resale option A is selected. Min resale price amount of the ticket to be resold It is editable or used only if organizer resale setting is enabled |
| Max resale price increase | number | float | Enable when Resale option A is selected. Max resale price Increase (in % of the initial price) of the ticket to be resold It is editable or used only if organizer resale setting is enabled |
| Max resale price amount | number | float | Enable when Resale option A is selected. Max resale price amount of the ticket to be resold |
| Specific resale price decrease/increase | number | float | Enable when Resale option B is selected. Specific resale price decrease/increase (in % of the initial price) of the ticket to be resold
It is editable or used only if organizer resale setting is enabled |
| Specific resale price amount | number | float | Enable when Resale option B is selected. Specific resale price amount of the ticket to be resold
It is editable or used only if organizer resale setting is enabled |
| The Resale & Purchase Agreement URL | string | 512 char | The Resale & Purchase Agreement URL in P2P resale It is editable or used only if organizer resale setting is enabled |
| Ticket Terms & Conditions URL | string | 512 char | Ticket Terms & Conditions URL in P2P resale It is editable or used only if organizer resale setting is enabled |
| Activation Id | string | 50 char | Activation group ID. Different tickets could have different activation method, this group ID make the distinction between them. |
| Activation Time | string | Date Time RFC3339 standard | Activation time at which the system will activate the ticket (display barcode) |
| Activation Method | string | "online"/"offline" | The method using to activate the ticket. online : when activationTime is reached (backend clock), the backend activates the tickets and sends push notifications to trigger a GET /spectator/tickets on the app. offline: the mobile application activates the tickets when time is reaches (mobile clock). Online requires the user to be online, Offline does not. More on Ticket activation: 5-Understanding TIXNGO Activation flow |
| Purchase Date | string | Date Time RFC3339 standard | Date & time at which the ticket was bought |
| Main Ticket Details | string | key (32 char) - value (4096 char) | Ticket details shown on the ticket's front (usually used to set entrance & seat details) |
| Extra Ticket Details | string | key (32 char) - value (4096 char) | Ticket extra details shown on the back of the ticket (usually used to set extra information about the ticket or the event) |
| Hidden Ticket Details | string | key (32 char) - value (4096 char) | Ticket hidden details (not displayed), used for different technical or business purposes, i.e. reserved key such as Seat Map, Sponsors details, etc... |
| Hold (only CSV injection for now) | Boolean | Boolean | Activate ticket holder (ticket is hold for someone else) |
| Holder email (only CSV injection for now) | string | 256 char | Ticket holder email |
| Holder date of birth (only CSV injection for now) | string | rfc3339 standard | Ticket holder date of birth |
| Holder first name (only CSV injection for now) | string | 50 char | Ticket holder first name |
| Holder last name (only CSV injection for now) | string | 100 char | Ticket holder last name |
| Holder gender (only CSV injection for now) | string | 1 char | Ticket holder gender (M, F or U) |
| Holder card number | string | 200 char | Ticket holder ID card number |
| Holder nationality | string | 2 char | Ticket holder nationality |
| Holder passport number | string | 200 char | Ticket holder passport number |
| mobileAppId | string | 256 char | Optional Mobile Application App Id to use associated invitation email template (used by organizer using their own app or branded apps). |
| lang | string | 5 char ISO 639‑1 format | The default language for the Ticket. Injection communications will be sent in this language. Example: fr, en, de, it, es |
| Design Id | string | 256 char | This Design Id representing a design applied to certain tickets in an Event |
| Background Color | string | 7 char hexadecimal color | The background color of the Ticket and the corresponding Design Id (If the Design Id is set). Example: #bbccdd |