Content Comparison

If your organizer does not use S-360 to inject and manage all or part of an event 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

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:

General set-up:

CSV File Specifications:

...

Maximum tickets per CSV file: 20,000 tickets

supports injecting tickets by uploading a CSV file in Backoffice.

Note

This feature is a bit different if you are still using TIXNGO v3 or already migrated to the newest TIXNGO v4. Please be sure to refer to the corresponding section below:

Table of Contents

minLevel	2
maxLevel	2
outline	false
style	none
type	list
printable	true

TIXNGO V4

...

Steps by step

Tracking status:

On this page, you will find a comprehensive list of all CSV injection jobs sent by the organizer, along with their respective statuses (COMPLETED/FAILED/IN PROGRESS).
It is essential for organizers to review the output file to verify the actual status of each injected ticket, whether it is ACCEPTED or REJECTED
Both the uploaded CSV file and the output file are available fo
For more details on each field of the file, please check here for better understanding.

Understand each fields in CSV:

Current TIXNGO version

...

title	TIXNGO V3

online activation method is only available if allow.activation-method.online = true, by default this setting key was set to false. TIXNGO mobile app supports offline activation perfectly, and we do not recommend using this activation method that requires our spectators must stay online during the gate opening.

Use the provided CSV template if need (click on the this CSV template link)
Fill the CSV with your ticket data. Please be sure that your file comply with the following constraints:
1. The CSV file must be encoded in UTF-8.
2. All dates must follow the RFC3339 standard for date and time.

...

Template Options:

Minimal Required Fields Template (CSV Minimal Template): Contains the minimum required fields.
Complete Template (CSV Full Template): Includes all possible ticket fields to assist with CSV setup.
Multilingual Template (CSV Full Template for Multilingual): Supports injecting with multilingual option.
With these 3 templates, please exclude "injection" from the file name to avoid any error
When using the Multilingual option, please ensure that you save your CSV file with the suffix "-multilingual".

...

If you failed to inject your CSV file, check out some points below to figure out what's the rootcause:

The CSV file must be encoded in UTF-8 to make sure your data format is valid
Instead of leaving unused columns empty, please delete them from the file. These empty cells will cause the errors of wrong formatting.
When saving your CSV file using Excel, please be cautious of a common issue where quotation marks ("") may be doubled. This duplication can cause errors when uploading the file.
By ensuring that quotation marks are not doubled, you can prevent potential errors during the file upload process. To avoid this problem, follow these steps after saving the CSV file:
1. Open the CSV file using a text editor or spreadsheet software.
2. Search for a
3. Remove the duplicate quotation marks, leaving only single quotation marks (").
4. Save the modified CSV file.

1. No more than 100’000 tickets can be imported at once
2. Event(s) referenced must already exists in TIXNGO (use manual creation screen if needed before uploading)
Upload CSV file
Submit
Check the result in the table. Possible status are:
- Status
  colour Yellow
  title In progress
  TIXNGO is currently processing the file you upload. Give it a bit of time and refresh the page later.
- Status
  colour Green
  title completed
  All tickets have been injected successfully. Good job! You can the download the output file for tracking purposes.
- Status
  colour Blue
  title partial
  Some tickets have been injected successfully, but at least one failed. --> Please download the output and review the errors.
- Status
  colour Red
  title Failed
  Not a single tickets could be injected. Something most probably wrong with the format or data in your file. → Please download the output and review the errors. Make sure to use the provided template and check the Troubleshooting section below.

Past injections, including input and output files, are kept for a period of 30 days. So be sure to download the output file if you need longer traceability.

Troubleshooting & detailed information

Typical errors

In case of errors, please check out some points below:

The CSV file must be encoded in UTF-8 to make sure your data format is valid
Instead of leaving unused columns empty, please delete them from the file. These empty cells could cause errors of wrong formatting.
When saving your CSV file using Excel, please be cautious of a common issue where quotation marks ("") may be doubled. This duplication can cause errors when uploading the file.
By ensuring that quotation marks are not doubled, you can prevent potential errors during the file upload process. To avoid this problem, follow these steps after saving the CSV file:
1. Open the CSV file using a text editor or spreadsheet software.
2. Search for any instances where quotation marks are doubled ("").
3. Remove the duplicate quotation marks, leaving only single quotation marks (").
4. Save the modified CSV file.

Fields detailed documentation

ticketDetails.hidden

Expand

title	Understand each fields in CSV

Variable Name	Mandatory	Variable Type	Value length	Variable usage/description	Examples

activationParameters.groupId

ticketId

No

2023-10-05T11:19:24+01:00

event.expirationDate

No

string

Date follows RFC 3339 standard

Time at which the event expire. Expired event cannot be used anymore.

2023-10-06T11:19:24+01:00

event.bluetoothPreparationRibbonDisplayTime

No

string

Date follows RFC 3339 standard

Time at which a ribbon displays on the mobile app to notify spectator turn on Bluetooth on the phone

2023-10-05T11:21:24+01:00

event.bluetoothPreparationRibbonEndTime

No

string

Date follows RFC 3339 standard

Time at which a ribbon disappear on the mobile app

2023-10-05T13:21:24+01:00

event.metadata

No

list

list of key-value metadata

Specific "key-value" fields provided to Organizer for special information about the event.
For now we handle the reserved keys below. You can override all those keys if you put them (same name, case sensitive) in the ticket details hidden section of the ticket.

Reserved Keys :

^{BARCODE_SIZE: value = Size of the barcode display on the Ticket (16 < x < 32) [mm]}
^{BARCODE_POSITION: value = Position of the barcode on the Ticket (LEFT, CENTER, RIGHT)}
^{RESALE_TICKETSHOP_URL: value = URL of ticket shop that use to resale a ticket (must include http or https)}
^{CANCEL_RESALE_TICKETSHOP_URL: value = URL of ticket shop that use to cancel a ticket (must include http or https)}
^{prohibited_items_image: value = URL of the prohibited items image}
^{prohibited_items_link: value = URL of the prohibited items link}
^{sponsorImage: value = URL of the sponsors image}
^{sponsorLink: value = URL of the sponsors link}
^{seat_map_image: value = URL of the seat map image}
seat_map_link: value = URL of the seat map link
enable_covid_check: value = Enable or Disable COVID check functionality for given event
^{EVENT_NUMBER: value = number of the event}

[{"key": "BARCODE_POSITION", "value": "CENTER"},{"key": "CANCEL_RESALE_TICKETSHOP_URL", "value": "https://ticketshop.secutix.com/account/tickets?cancelResaleTicketId="}, {"key": "RESALE_TICKETSHOP_URL", "value": "https://ticketshop.secutix.com/account/resale/resellTickets?ticketIds="}]

event.group.id

No

string

256 char

Id of the Group. Every Event with this Group ID will be part of that Group.

GROUP-ID-101

event.group.name

No

string

128 char

Name of the Group.

CHAMPION LEAGUE

event.group.image

Yes

string

256 char

The Image of the Group (displayed on the "My Events" view).

https://r.tixngo.io/tng/Concert%20Asset%20300x240.png

purchaseDetails.price

Yes

double

The Ticket's price. (Example 30, 55.50, 120.55,..._)

45.50

purchaseDetails.currency

Yes

string

20 char

The currency used in the transaction using ISO-4217 standard (example: CHF, VND, USD).

EUR

purchaseDetails.date

Yes

string

Date follows RFC 3339 standard

The date at which the Ticket was initially bought.

2023-10-04T11:19:24Z

purchaseDetails.priceCategory

Yes

string

512 char

Examples of price category are adult, child, student, senior, VIP, etc.

ADULT, CHILD, etc

purchaseDetails.taxationNumber

Yes

string

512 char

(UUID) taxation number of the Ticket.

tax-num-1234

ticketDetails.main

No

list

list of key-value metadata

Free "key-value" fields usually used to define spectator seating information such as: gate:A, row:2, seat:7 (Displayed on the "front" of the Ticket).

[{"key": "Gate", "value": "A"},{"key": "Row", "value": "54"}, {"key": "Seat", "value": "A5"}]

ticketDetails.extra

No

list

list of key-value metadata

Free "key-value" fields usually used to define extra information (Displayed on the "back" of the Ticket).

Reserved Keys :

file_id : optional field set by the Organizer at injection.

[{"key": "File", "value": "123"},{"key": "Special Note", "value": "No Re-Entry"}, {"key": "Parking", "value": "Included"}]

Yes

string

50 char

The activation group to which the ticket belongs to. Tickets sharing the same activation id will have the same activation method & decryption code.

activation-id

activationParameters.method

Yes

string

"online"/"offline"/"beacon"

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: /wiki/spaces/TNG/pages/48627957

offline

activationParameters.time

No

string

Date follows RFC 3339 standard

If online is chosen, de

2020-10-05T11:19:24+01:00

activationParameters.instanceId

No

string

128 char

If offline is chosen, define the bluetooth instance id that the mobile app should listen to to get the decryption key.

image

No

string

256 char

The uri to the image that will be displayed to the user with its ticket. It must have a width:length ratio of X:Y (to be defined). (displayed on the "Ticket" view).

https://r.tixngo.io/tng/Concert%20Asset%20300x240.png

event.id

Yes

string

256 char

ID representing the event (unique).

event-id-101

event.address.site

Yes

string

200 char

Name of the site the Event will take place.

TIXNGO Stadium

event.address.line1

No

string

200 char

Address line 1

event.address.line2

No

string

200 char

Address line 2

event.address.line3

No

string

200 char

Address line 3

event.address.city

Yes

string

200 char

City where the event takes place

Lausanne

event.address.countryCode

No

string

200 char

Country code for the Address

CH, FR, DE, etc

event.address.region

No

string

200 char

Region where the Event takes place

Bavaria

event.address.zip

Yes

string

50 char

Zip code where the Event takes place

event.address.longitude

No

double

Longitude where the Event takes place

event.address.latitude

No

double

Latitude where the Event takes place

event.name

Yes

string

128 char

Name of the Event

“Team A vs Team B”

event.startTime

Yes

string

Date follows RFC 3339 standard

Time at which the event starts. Used for app logic such as reminders etc...

Date Format: 2022-12-12T16:11:00Z

Unique identifier of this ticket in the organizer's ticketing system (typically technical ID)

PLAY-12345678901234

eventId

Yes

string

Unique identifier of the event

PLAY-123456789012

ticketNumber

Yes

string

Business, human readable, unique identifier of the ticket

12345678901

ticketCode

Yes

string

Code for access control that will rendered as a QRcode

123456789012345678901234

activationRule

No

string

Name of the activation rule to use for this ticket. If not provided or not matching a rule associated with the event, will use the one named 'DEFAULT'.

DEFAULT

dataCollectionRule

No

string

Name of the data collection rule to use for this ticket. If not provided or not matching a rule associated with the event, will use the one named 'DEFAULT'.

DEFAULT

designRule

No

string

Name of the design rule to use for this ticket. If not provided or not matching a rule associated with the event,

DEFAULT

emailRule

No

string

Name of the email rule to use for this ticket. If not provided or not matching a rule associated with the event, will use the one named 'DEFAULT'.

DEFAULT

usageRule

No

string

Name of the usage rule to use for this ticket. If not provided or not matching a rule associated with the event, will use the one named 'DEFAULT'.

DEFAULT

purchaseDetails.fileNumber

Yes

string

Purchase reference number in the ticketing system.

1122

purchaseDetails.purchaseDate

Yes

date time

Date follows RFC 3339 standard

Purchase date and time

2025-11-22T11:22:33.000Z

purchaseDetails.price

Yes

number

Price of the ticket

500

purchaseDetails.currency

Yes

string

Currency following the ISO 4217 format

CHF

purchaseDetails.seatCategoryId

No

string

Unique identifier of the seat category corresponding to this ticket.

1234567890

purchaseDetails.contingentId

No

string

Unique identifier of the contingent from which this ticket is coming.

1234567890

purchaseDetails.tariffId

No

string

Unique identifier of the tariff applied to this purchase.

ADULT, CHILD

ticketDetails.main

Status

colour	Yellow
title	V3-compatible

No

List

If it’s not empty, the key, and it’s value are r

Not recommend to use this setting key
please using V4 properties:

seatingDetails.area
seatingDetails.level
seatingDetails.externalEntrance
seatingDetails.gate
seatingDetails.block
seatingDetails.row
seatingDetails.seat

to have better look & feel on Back-office

Image Added

Code Block

language	json

[{"key":"Seat","value":"13", "lang":"en"}]

ticketDetails.extra

No

List

If it’s not empty, the key, and it’s value are required

Code Block

language	json

[{"key":"re_entry","value":"Please be informed you cannot leave the stadium and then re-enter.", "lang":"en"}]

ticketDetails.hidden

No

List

If it’s not empty, the key, and it’s value are required

Code Block

language	json

[{"key":"hosp_room","value":"VIP1", "lang":"en"}]

seatingDetails.seated

Yes

Boolean

Set to true if the seating details below are available and can be displayed to the spectator on the ticket.

true

seatingDetails.numbered

Yes

Boolean

True when the ticket gives access to a numbered seat.

true

seatingDetails.area

With condition

Area to which the ticket gives access.

Condition: This field is required if value of seatingDetails.seated is true

Area 1

seatingDetails.level

No

Level to which the ticket gives access.

1

seatingDetails.externalEntrance

No

Name of the external entrance the spectator should use to access the venue.

West

seatingDetails.gate

No

Name of the gate the spectator should use to access the venue.

A

seatingDetails.block

No

Block to which the ticket gives access.

AA

seatingDetails.row

No

When seated, row in which the seat is located.

2

seatingDetails.seat

With condition

Seat number

Condition: This field is required if value of seatingDetails.seated is true and seatingDetails.numbered is true

24Spectator's email

spectatorDetails.firstName

Yes

Spectator's first name

John

spectatorDetails.lastName

Yes

Spectator's last name

Doe

spectatorDetails.email

Yes

Spectator's email

jd@tixngo.io

spectatorDetails.appLanguage

Yes

Spectator's preferred language. In ISO 639-1 format.

en

ticketHolder

No

Ticket holder data, optionnally submitted. If present, must provide at least firstName and lastName. All other values are saved as is and NOT validated against data collection rules

Code Block

language	json

{
  "firstName": "John",
  "lastName": "Doe"
}

Version	Old Version 24	New Version 25
Changes made by	Thanh HUYNH	François BOCHATAY
Saved on	May 06, 2025	Jun 03, 2025

Versions Compared

Key

Inject tickets by CSV file

What you should know:

General set-up:

TIXNGO V4

Steps by step

Tracking status:

Understand each fields in CSV:

Current TIXNGO version

Troubleshooting & detailed information

Typical errors

Fields detailed documentation

TIXNGO V3 (old)
Status
colour Yellow
title deprecated

Inject tickets by CSV file

What you should know:

General set-up:

Tracking status:

More details

New version of TIXNGO
Status
colour Green
title Coming soon

Content Comparison

Versions Compared

Key

Inject tickets by CSV file

What you should know:

General set-up:

TIXNGO V4

Steps by step

Tracking status:

Understand each fields in CSV:

Current TIXNGO version

Troubleshooting & detailed information

Typical errors

Fields detailed documentation

TIXNGO V3 (old) StatuscolourYellowtitledeprecated

Inject tickets by CSV file

What you should know:

General set-up:

Tracking status:

More details

New version of TIXNGO StatuscolourGreentitleComing soon

TIXNGO V3 (old)
Status
colour Yellow
title deprecated

New version of TIXNGO
Status
colour Green
title Coming soon