The ticket injection process pushes the designated ti
...
| Comfort variable code | Format | Example | Injected field inside TIXnGO | Notes | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| TIXAct | start_of_season | start_of_season end_of_season 2w 22/10/23 21:15 | activationParameters.time | If not defined, nothing special happens Parts in blue will be implemented with : | ||||||||
| TIXStart | start_of_season | start_of_season | event.startTime | If comfort variable i Parts in blue will be implemented with : | ||||||||
| TIXExp | start_of_season | start_of_season | event.expirationDate | If comfort variable is not defined, then the value is taken from the end date of the performance + duration (or +24 hours if duration not defined), or the end validity date of the ticket. Parts in blue will be implemented with : |
...
Please enter here one or many of the following values, separated by commas
FIRSTNAME,LASTNAME,BIRTHDATE,ID_NUMBER,COUNTRY_CODE,BIRTH_REGION,BIRTH_PLACE
Only the tickets having those beneficiary values filled will be sent to TIXnGO.
...
If you put more than one please separete separate them by comma ",".
- Force ticket by ticket Id : id:123456789
- Force ticket by tax number : 12300123
- Skip ticket by ticket Id : id:123456789
- Skip ticket by tax number : 12300123
You can force/skip both (one by ticket id and one by tax number) like this : id:123456789, 12300123
Batch size
Recommended value: 1000