...
Variable Name | Variable Type | Value length | Variable usage/description |
---|---|---|---|
ticketId | string | 256 char | ID of the ticket to update |
ticketDetails.main | list | list of key value metadata in JSON format | Ticket details shown on the ticket's front (usually used to set entrance & seat details) |
ticketDetails.extra | list | list of key value metadata in JSON format | Ticket extra details shown on the back of the ticket (usually used to set extra information about the ticket or the event) |
ticketDetails.hidden | list | list of key value metadata in JSON format | Ticket hidden details (not displayed), used for different technical or business purposes, i.e. reserved key such as Seat Map, Sponsors details, etc... Available hidden fields: prohibited_items_image, prohibited_items_link seat_map_image, seat_map_link sponsorImage, sponsorLink at_icon specialColor background_color ticketDetailMainNotInBoxes show_price |
What you should know:
- Organizer should only update maximum 50 tickets per batch (Max 50 rows per CSV)
- The CSV delimiter must be ";".
- The Data format must be the same as the template gets from CSV template or Export Ticket Details.
- The data in CSV file will replace fully the ticket details that initially injected to each ticket.
- The update result will be available in the OUTPUT column once the input file is submitted successfully, but not saved in the system. (which is disappeared after you refresh the page)