1 V4 Interface
- 1.1 General Configuration
- 1.2 Interface custom parameters
2 V4 interface functions
3 Injection templates
4 Retrieve Tickets Changes (aka Feedback interface) details
- 4.1 Understand business ticket status and the alignment between S-360 and TIXNGO systems
  - 4.1.1 Terminology
  - 4.1.2 Mobile ticket history
    - 4.1.2.1 Mobile statuses & possible transitions

V4 Interface

To avoid confusion, regression and other misunderstandings, we developed a brand new interface named TIXNGO v4. In order to inject V4 tickets, this new V4 only interface must be provisioned.

Interface has been provisioned, the configuration can start.

General Configuration

Field	Mandatory	Description

Field	Mandatory	Description
Internal name	Yes	Name for this interface
URL	Yes	TIXNGO API URL
Login	No	Not used for Authentication with TIXNGO Back-End By convention, please use the e-mail address of the TIXNGO Organizer ADMIN account
Password	Yes	API Key of your TIXNGO Organizer ADMIN account
Email notification to recipients	No	List of emails (comma separated) to be notified in case a function from this interface raises an error
Custom parameters	No	See below

Interface custom parameters

The interface is intended to be used without any custom parameters. For some specific cases, the following parameters can be used.

Custom parameter	Purpose

Custom parameter

Purpose

maxLengthDumpedCallsInKbs

In order to save the payloads exchanged between S-360 & TIXNGO, you can use maxLengthDumpedCallsInKbs=5000

RECOMMENDATION: Use for troubleshooting ONLY.

V4 interface functions

This interface hosts 5 functions:

Inject Event Tickets for the injection of Performances/Events tickets
Inject Simple Products Tickets for the injection of Open Passes and other simple products
Invalidate Tickets formerly known as “Push Cancelled”
- The following parameters are no longer used in Ticket V4 due to changes in ticket visibility rules:
  - Notify spectator
  - overrideVisibilityFlagForInvalidationReasons
- Updated Rules
  - Ticket visibility is now determined by TIXNGO based on the deletion reason and displayed on the relevant screens.
    1. Deleted Items screen
      - Shows all deleted tickets, except those with deletionReason in (RESALE_PENDING, RESOLD).
      - Prerequisite: Application setting deleted-tickets-visibility = true.
    2. Resale Pending screen
      - Shows only deleted tickets where deletionReason = RESALE_PENDING.
      - Prerequisite: Application setting Ticket resale via S-360 ticketshop (enable-resale-ticket-shop-s360 = true).
    3. Resale Resold screen
      - Shows only deleted tickets where deletionReason = RESOLD.
      - Prerequisite: Application setting Ticket resale via S-360 ticketshop (enable-resale-ticket-shop-s360 = true).
    If none of the above conditions are met, the deleted tickets will not be displayed in any screen.
Control Tickets formerly known as “Push Controlled”
Retrieve Tickets Changes formerly known as “Retrieve Ticket status”
- You can now re-sync all tickets for a specific event from TIXNGO back to S-360 (requires TIXNGO’s support).
- The new approach no longer supports the additionalDiffParameters test parameter.

Why Inject Event Tickets VS Inject Simple Products Tickets ?

In V3 injection, users could inject either performance/event tickets or simple product tickets from the same screen, but this led to a long list of mutually exclusive and conflicting filters.

To enhance the user experience, the injection function has been split into two distinct functions, each with a dedicated screen displaying only the filters relevant to the type of product being injected.

Inject Event Tickets	Inject Simple Products Tickets

Inject Event Tickets	Inject Simple Products Tickets

Injection templates

Current V3 templates can be reused as a base for V4 injection.
Existing activation/transfer/design groups will be ignored and

We recommend using the introduction of the rule name as an opportunity to remove obsolete and unnecessary elements, such as activation/transfer/design groups and duplicated keys/values (now that standard properties regarding purchase details and seating details are automatically injected).

Understand all S-360 variables for Ticket V4 Injection at Understand S-360 variables for tickets Injection

Retrieve Tickets Changes (aka Feedback interface) details

Understand business ticket status and the alignment between S-360 and TIXNGO systems

Terminology

S-360 Mobile ticket status

This is the latest business status of a ticket, and it’s always equal to the last status in the Mobile ticket history

TIXNGO ticket status

It indicates whether a ticket is currently in the app (DOWNLOADED) or not (NOT DOWNLOADED), awaiting a new owner (PENDING TRANSFER), or no longer valid (DELETION PENDING and DELETED)

Mobile ticket history

On S-360

On TIXNGO

Mobile statuses & possible transitions

image-20251014-015832 (1)-20251112-074421.png

Status	Additional information message format	Sample message

Status	Additional information message format	Sample message
INJECTED	<empty>	-
DOWNLOADED	<empty>	-
PENDING TRANSFER	In case forward transfer: Transfer to: $recipient.email In case backward transfer: Transfer to: $recipient.email (Return) In case Admin transfer: TIXNGO Backoffice transfer to: $recipient.email	In case forward transfer: Transfer to: spectatorB@tixngo.io In case backward transfer: Transfer to: spectatorB@tixngo.io (Return) In case Admin transfer: TIXNGO Backoffice transfer to: spectatorB@tixngo.io
TRANSFERRED	Ticket transferred from: $previousOwner.email	Ticket transferred from: spectatorA@tixngo.io
FAILURE TRANSFER	In case, it has been rejected: Transfer rejected by $recipient.email In case, it has been canceled by sender: Transfer cancelled by the sender. In case, it has been auto-canceled by system: Transfer cancelled by the system.	In case, it has been rejected: Transfer rejected by spectatorB@tixngo.io In case, it has been canceled by sender: Transfer cancelled by the sender. In case, it has been auto-canceled by system: Transfer cancelled by the system.
ASSIGNED	Ticket assigned to: $holder.firstName + $holder.lastName(if exist)	Ticket assigned to: John Doe OR Ticket assigned to: John
ACTIVATED	Ticket activated ($activationMethod) on $deviceModel.	Ticket activated (offline) on iPhone 17.
DEACTIVATED	System deactivate: You require spectators to assign a ticket holder to view the QR code. If the QR code has been revealed, and you also allow ticket transfers after activation. Our system deactivates the ticket upon transfer and requires the new owner to assign a ticket holder to view the QR code. Ticket deactivated by the system Manual deactivate: Ticket manually deactivated	System deactivate: Ticket deactivated by the system Manual deactivate: Ticket manually deactivated
CONTROLLED	<empty>	-
DELETION PENDING	In case the deletion is triggered by S-360: Ticket deleted by the Ticketing system. Reason: $deleteReason In case the deletion is triggered by TIXNGO: Ticket deleted from the TIXNGO BackOffice by $backofficeUserEmail, Reason: $deleteReason	In case the deletion is triggered by S-360: Ticket deleted by the Ticketing system. Reason: REPRINT In case the deletion is triggered by TIXNGO: Ticket deleted from the TIXNGO BackOffice by operator1@tixngo.io, Reason: BLACKLIST
DELETED	In case ticket is deleted when it’s not delivered yet (direct transition from INJECTED to DELETED) In case the deletion triggered by S-360: Ticket deleted by the Ticketing system. Reason: $deleteReason In case the deletion triggered by TIXNGO: Ticket deleted from the TIXNGO BackOffice by $backofficeUserEmail, Reason: $deleteReason Other cases (transition from DELETION_PENDING to DELETED) Ticket deleted on all devices.	In case ticket is deleted when it’s not delivered yet (direct transition from INJECTED to DELETED) In case the deletion triggered by S-360: Ticket deleted by the Ticketing system. Reason: REPRINT In case the deletion triggered by TIXNGO: Ticket deleted from the TIXNGO BackOffice by operator1@tixngo.io, Reason: BLACKLIST Other cases (transition from DELETION_PENDING to DELETED) Ticket deleted on all devices.

S-360 <-> TIXNGO V4 Interface