/
Understand S-360 variables for tickets Inje

Understand S-360 variables for tickets Injection

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:

TIXNGO V4

Variable Name

Variable Type

Variable usage/description

Visible in TIXNGO app / ticket (Yes/No)

Required by TIXNGO API?
(Mandatory fields)

 

Set in S-360 (Injection Batch)?

Overwritable by SecuTix's Ticket Template Editor?

Variable Name

Variable Type

Variable usage/description

Visible in TIXNGO app / ticket (Yes/No)

Required by TIXNGO API?
(Mandatory fields)

 

Set in S-360 (Injection Batch)?

Overwritable by SecuTix's Ticket Template Editor?

event.id

String

Unique identifier of the event

No

Yes

Set systematically by Injection Batch

No

event.name

String

Name of the Event

Yes

Yes

Set systematically by Injection Batch

Yes

event.address.site

String

Name of the site the Event will take place.

Yes

Yes

Set systematically by Injection Batch

Yes

event.address.city

String

City where the event takes place

No

Yes

Set systematically by Injection Batch

Yes

event.address.countryCode

String

Country code for the Address

No

Yes

Set systematically by Injection Batch

Yes

event.address.zip

String

Zip code where the Event takes place

No

Yes

Set systematically by Injection Batch

Yes

event.startime

Date follows RFC 3339 standard

Time at which the event starts.

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

Yes

Yes

Set systematically by Injection Batch

no

event.expirationDate

Date follows RFC 3339 standard

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

No

Yes

Set systematically by Injection Batch

no

event.website

String

Website URL of the Event.

No

No

Set systematically by Injection Batch

Yes

event.metadata

List

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.

 Resale

  • 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)

Exchange

  • EXCHANGE_TICKETSHOP_URL: value = URL of ticket shop that use to exchange a ticket (must include http or https)

Event schedule

  • EVENT_SCHEDULE: value = List of JSON objects with the pair of Crowdin label and time

add EVENT_SCHEDULE as an event metada key

image-20250829-025606.png

Put this JSON as a static value

[ { "label": "e_gateOpening", "time": "18:30" }, { "label": "e_ceremony", "time": "19:30" }, { "label": "e_startTime", "time": "19:45" }, { "label": "e_gateClosing", "time": "22:30" } ]
image-20250829-025758.png

You can adjust the time and remove unnecessary information if need

Current supported Crowdin labels for the event schedule: e_gateOpening, e_ceremony, e_startTime, e_gateClosing

And make sure you have already provide the translation fo

image-20250829-062712.png

Event semantics https://go.confluence.secutix.com/wiki/x/hAAjDw

  • Can be defined at TIXNGO Backoffice or can be injected from S-360 by defining a value for the following metadata: event_type, team_home_name, team_home_logo, team_away_name, team_away_logo, competition_name, competition_logo, event_number

Minimum match event semantics can be injected by setting the following variables in the injection template:

  • event.metadata.1.key = "event_type"

  • event.metadata.1.value = "MATCH"

  • event.metadata.2.key = "team_home_name"

  • event.metadata.2.value = "Manchester United"

  • event.metadata.3.key = "team_home_logo"

  • event.metadata.3.value = "https://team-logos.org/manunited.png"

  • event.metadata.4.key = "team_away_name"

  • event.metadata.4.value = "FC Barcelona"

  • event.metadata.5.key = "team_away_logo"

  • event.metadata.5.value = "https://team-logos.org/barca.png"

Ticket Layout - Overriding at event-level https://go.confluence.secutix.com/wiki/x/rIQnDw

  • ticket_image_myticket: My Tickets screen

  • ticket_image_thumbnail: Ticket screen Image

  • ticket_image_fullsize: Ticket sreen Full-Size Image

  • prohibited_items_image: Prohibited items Image URL

  • prohibited_items_link: Prohibited items Redirect URL

  • sponsorImage: Sponsors Image URL

  • sponsorLink: Sponsors Redirect URL

  • seat_map_image: Seat map Image URL

  • seat_map_link: Seat map Redirect URL

  • ticket_secure_backgroundcolor: Event-day secure display Background color

  • ticket_secure_image : Event-day secure display Image

  • ticket_manual_activation_gs_footer_color: Footer color

  • ticket_manual_activation_gs_footer_image: Footer image

Yes

No

Set systematically by Injection Batch

Yes

ticketId

String

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

No

Yes

Set systematically by Injection Batch

No

ticketNumber

String

Business, human-readable, unique ticket identifier (i.e., tax number)

Yes
(changeable)

Yes

Set systematically by Injection Batch

No

ticketCode

String

Barcode of the Ticket.

Yes

Yes

Set systematically by Injection Batch

No

activationRule

String

Name of the activation rule to use for this ticket.

If no value is provided or no matching rule

No

No

 

Yes

dataCollectionRule

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'

No

No

 

Yes

designRule

String

Name of the design rule to use for this ticket.

If not provided or not matching a rule associated with the event, will use the one named 'DEFAULT'

No

No

 

Yes

emailRule

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'

No

No

 

Yes

usageRule

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'

No

No

 

Yes

purchaseDetails.fileNumber

String

Purchase reference number in the ticketing system.

Yes
(changeable)

Yes

Set systematically by Injection Batch

No

purchaseDetails.purchaseDate

date time - Date follows RFC 3339 standard

Purchase date and time

Yes
(changeable)

Yes

Set systematically by Injection Batch

No

purchaseDetails.price

number

Price of the ticket

Yes
(changeable)

Yes

Set systematically by Injection Batch

No

purchaseDetails.currency

String

Currency following the ISO 4217 format

Yes
(changeable)

Yes

Set systematically by Injection Batch

No

purchaseDetails.seatCategoryId

String

Unique identifier of the seat category corresponding to this ticket. This identifier should have a matching translation in the event metadata in order to be displayed properly on the mobile

Yes
(changeable)

Yes

Set systematically by Injection Batch

No

purchaseDetails.contingentId

String

Unique identifier of the contingent from which this ticket is coming. For reference and display in Backoffice only, this is not visible on the mobile ticket.

Yes

No

Set systematically by Injection Batch

No

purchaseDetails.tariffId

String

Unique identifier of the tariff applied to this purchase.

Yes
(changeable)

Yes

Set systematically by Injection Batch

No

ticketDetails.main

List

Free main ticket metadata "lang-key-value" fields display essential custom information in the first section.

https://go.confluence.secutix.com/wiki/spaces/TIXNGO/pages/202867749/V4+Ticket+Layout+Classic#Ticket-metadata-display

Format: ticketDetails.main.$index$.[lang|key|value] = ‘xyz’
Example:

ticketDetails.main.1.lang = 'en' ticketDetails.main.1.key = 'my key' ticketDetails.main.1.value = 'xyz'

Yes
(changeable)

No

No

Yes

ticketDetails.extra

List

Free ticket metadata "key-value" fields display less important custom information in a dedicated "More info" section at the bottom of the ticket, just above the sponsors' footer.

https://go.confluence.secutix.com/wiki/spaces/TIXNGO/pages/202867749/V4+Ticket+Layout+Classic#Ticket-metadata-display

Format: ticketDetails.main.$index$.[lang|key|value] = ‘xyz’

Yes

No

No

Yes

ticketDetails.hidden

List

Free "key-value" fields are used for specific per-ticket customhttps://go.confluence.secutix.com/wiki/spaces/TIXNGO/pages/134088452/Introduction+to+V4+Design+rules#Specific-per-ticket-customization.

Keys:

  • hosp_room: Optional field set by the Organizer at injection to define the hospitality room for the ticket.

  • show_price: Optional field set by the Organizer at injection to indicate whether to display the price on purchase details.

  • at_icon: Optional field set by the Organizer at injection to show an extra icon in the top-left corner of the ticket layout.

You can also visit this page to understand how to set up the https://go.confluence.secutix.com/wiki/spaces/TIXNGO/pages/313491696

-

No

No

Yes

ticketDetails.flow

 

Navigation flow with "key-value" fields to display custom information in the “box” section instead of the Seating Details when presented

For more details, visit https://go.confluence.secutix.com

Format: ticketDetails.flow.$index$.[key|value] = ‘Z1’
Example:

ticketDetails.flow.1.key = 'Zone' ticketDetails.flow.1.value = 'Z1'

 

 

 

 

seatingDetails.seated

Boolean

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

Set to false for cases like parking tickets for instance.

No

Yes

Set systematically by Injection Batch

Yes

seatingDetails.numbered

Boolean

True when the ticket gives access to a numbered seat.

No

Yes

Set systematically by Injection Batch

Yes

seatingDetails.area

String

Area to which the ticket gives access.

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

Yes
(changeable)

Condition

Set systematically by Injection Batch

Yes

seatingDetails.level

String

Level to which the ticket gives access.

Yes
(changeable)

No

Set systematically by Injection Batch

Yes

© TIXNGO 2023 - Login