An event group is the top level to which event dates are connected. If you have a production of 30 dates you create 1 event group and 30 event dates. Always start by creating the event group and after that create the date. This guide covers all settings that can be configured in an event group. In most cases it is enough to only use the settings under the Information and Images tabs. Other tabs are for advanced settings. TABLE OF CONTENTS Create event group Images Advanced  Translations Finance Payment types Queue-IT Create event group To create a new Event group navigate to Administration > Events > Groups and click Add event group in the upper right corner. Information Name Name of the event group, usually the same as the event date. Subtitle Only used in Iceland for Tixly market place. Should follow the example: Venue || Month/Year - Lorensbergsteatern || September - December 2020. It also appears in the Tixly Event API. Organisation If working with multiple organisations, the right organisation can be selected. Available online Choose whether the event date can be found on the Tixly marketplace (Iceland only) and through the Tixly Event API. Display coloured availability Choose if availability should be displayed as colours in the online buying process. Green for seats available in the best sections (based on the ranking on the hall) or no ticket status. Yellow for lesser quality seats or few tickets status. Red for lower ranked seats or sold out/cancelled status. Show event filter Activates filter in the online buying process. The customer can then filter events in the list by amount of tickets and the day of the week. Description Set a description of the event that will appear on Tixly marketplace and in the Tixly Event API. This text is also visible in the Box Office sales view under the i. Skin Brand used for the online buying process. It's possible to have multiple brands. The skin does not save on the event group, so select the correct skin before copying the weblink. Weblink Link to the online buying process showing all event dates that are connected to the event group.  Images Upload an image for the event group. The image is usually the same for Event and Featured. These images are used in several places throughout the buying process, for example in subscription and package sales, the landing page for special offers, in customer order pages for events that you might be interested in and more. Featured Image used on the front page of the Tixly marketplace / on the pdf ticket / subscription sales / suggestions in basket / landing page of special offer. Event Image used on the event page of the Tixly marketplace / mobile ticket / online exchanges / My Pages The maximum file size is 5.5 MB. If the image exceeds this size, loading a mobile ticket will result in an error message. There are no recommended image sizes other than that they should be in landscape mode and should preferably not include any text. Advanced  Recurring Define if the event dates should be hidden on dashboards or not. Usually used when there are many of the same event dates which overflows the sales dashboard. E.g. guided tours. The event dates can still be found when searching for events. Heading text online Text shown in the online buying process. Hello in the example below. Note text online Text shown in the online buying process. Is it me you're looking for? in the example below. The note text is only shown if there's also a heading. Text for product sale Extra text show in the online buying process when adding products. Redirect to Event Group (Iceland only) Select another event group that customer will be redirected to. Used when old links are still circulating on the internet. Allow changes Define if customers that bought tickets to this event group should be allowed to exchange tickets to another event after purchase. Allow change to this group If Yes, it's possible to exchange tickets to this event group from other event groups, provided that exchanges have been allowed on the other event group. Read Allow date change for more information. Translations Add translations for online and ticket elements to the available languages. These will also be shown in the API. Finance If required, add an external reference number, department, account and/or dimensions to the events. These numbers will show up in several reports and the finance export. Payment types Activate if only specific payment types should be available in Box Office for the event dates connected to the event group.  Queue-IT Queue-IT is a virtual queue that can be setup for events where traffic is expected to be very high. Customers will be directed to the queue and then the queue admits a limited amount of customers into the buying process continuously.  If you want to setup a queue, contact your local Tixly Support. 

The Tixly ticketing system is used in combination with a website from the venue. This article describes the possibilities and best approach to integrate the venue website and Tixly. There are multiple methods to do this, from simple manual links to a fully automated setup. Manual links Automated setup Webhook User login status and basket information Data in the session information Using personalised information to give pre-sale access and different ticket types to some customers Skins Manual links It is possible to use direct links to the production, event or subscription sales pages and place these on your website by hand. These links can be found in the Box Office sales screens in Tixly and also on the Internet tab of the event edit screens. Of Course, this depends on the cms how this is done. Link to a production https://tix.theatreexample.com/en/buyingflow/tickets/1290/ Link to an event in this production https://tix.theatreexample.com/en/buyingflow/tickets/1290/18417/ Link to an subscription https://tix.uk/en/theatreexample/buyingflow/subscription/15/ The first two examples show a Tixly setup on the subdomain of the venue, the last one uses the Tixly domain. Automated setup The website database holds the events or subscriptions with all information that the venue wants to publish on their website. There can be a calendar page, a page per production. A common approach is to have a setup that does the following: The website periodically imports all future events into their database with help of the Tixly Event API. This ensures that the event information from Tixly is present in the website database. add new events to the local database update existing events  mark the local events the are not in the output anymore as deleted.  The more information is used the better, the PurchaseURL's, OnlineSaleStart, OnlineSaleEnd and SaleStatus are probably needed. The cms is used to add more information, videos, reviews etc to the event groups (productions) or to individual event dates. The website publishes the event. From now it is visible to the visitors. A [buy tickets] button is shown with the Purchase url when the current date is between OnlineSaleStart and OnlineSaleEnd When the user clicks on [buy tickets] the Tixly flow is opened in the same browser window. A reasonable interval for the import in step 1 depends on the situation, once every hour is reasonable. You can add minimized=  true to the event api url to get an output with the minimal version, this only has SaleStatus. You can use this to sync the status more frequently, and build a lighter script the does not need to check if other properties of events are changed.  Webhook It seems a bit of a waste to do the import very often, when most of the time nothing has changed. But on the other hand, you don't want to wait 2 hours for a change in Tixly to be visible on your website. This is when you can use the webhook functionality to solve this. Tixly will call a url on your website, the webhook url, every time in Tixly a change to an event has been made. As a response to the webhook request your website can start an import job. There is no information in the webhook on what event has been changed and Tixly does no do anything with the data the webhook may return. Valid webhook url examples are: https://www.theaterxyx.nl/import/trigger https://username:[email protected]/admin/tix-importer.php Pro tip: The webhook is called whenever something changes. If the venue staff is editing prices, genres etc. this can result in your webhook being called several times a minute. And then for hours, when nothing changes it is not called at all. Instead of running your import routine every time the webhook is called, it is better to wait a minute or two, and if no more webhook calls have been made during this period, then do the import. To start using this, contact Tixly support and give them your website webhook url and we configure this to be used. User login status and basket information Important: Due to restrictions of most browsers, your Tixly instance needs to be on a subdomain of your venue website. e.g. tix.venuewebsite.se  That means this session sharing feature only works on what we call hosted skins. It is possible to show on the venue website that a user is logged into Tixly and if they have a basket. Also the basket contents can be shown on the website. Like this example: This is achieved by sharing session data from Tixly to the website. The website then uses this data to show it in the design they want. The sharing works by opening an iframe to the Tixly website with the integration url on the correct skin. This iframe should be hidden on the venue webpage and does not show anything. It is just used to have javascript from the event/postmessage framework to communicate between the opener page on the venue site and the iframe from Tixly. The post messaging is limited by the settings on the skin, to only allow some websites to post messages and receive data from (see Skin settings). Multiple websites can be configured, this allows development and staging servers of the venue site to use the same skin as the production website. The url of the URL to Iframe, itix (short for integration tix) file is; {skin url}/{language}/itix Example: https://tix.theateraandeparade.nl/nl/itix This url is best to be requested in an iframe . The postMessage 'GetSession' should be issued to the iframe. An EventListener is used to act on the return message with the session information. Looking at implementations of other tixly customers can help to understand this. The Brussels based venue La Monnaie / De Munt has an easy to understand setup. Data in the session information Below is an example of the json structure of the postmessage response. This shows an order with two tickets and the user. { "order": { "items": [{ "type": "Ticket", "name": "An evening with Q on stage", "details": "13-3-2022 20:00:00", "price": 12.0000 }, { "type": "Ticket", "name": "An evening with Q on stage", "details": "13-3-2022 20:00:00", "price": 12.0000 } ], "expires": 896.0954898, "url": "https://tix.theaterexample.nl/nl/buyingflow/purchase/" }, "user": { "id": 544803, "name": "James Bond", "email": "[email protected]", "hash": "2ac9f3a26521d0194530daf3e68c88589d4490617059793dd2eba1b14b786b84" "tags": [{ "id": 7, "name": "Premium", "abbr": "PP" }] }, "profile": "https://tix.theaterexample.nl/nl/profile/" } Details of the properties in the object that is being sent are as follows: order Object that is null if no order is currently in the user session order->items A list of all items in the order order->items->type Type of item. Can be Ticket, Subscription, GiftCard, Membership, Donation, or Product. Note: Subscription is a ticket that is part of a subscription package. order->items->name Name of the item, varies for each type: Ticket > Name of event Subscription > Name of subscription package GiftCard > Name of gift card group Product > Name of product order->items->details Details for each type: Ticket > Event’s start date Subscription > Event’s name and start date GiftCard > Amount of the gift card formatted as an invariant string “20.00” Product > No details given on products order->items->price Price of the item as an invariant decimal (0.00) order->expires Decimal seconds and milliseconds until the order expires from the moment the session info was requested. order->url A URL that takes you to the purchase page for the order. user Object is null if the user is not logged in on this session user->id Id of the web user. Note: this is not the customer id. In the CRM API, there is an endpoint to get the customer Id from the web user Id. CRM API: POST /WebUser/{webUserId}/customer user->name Full name of the logged-in user (can be empty) user->email Email of the logged-in web user (in rare cases, this can differ from the customer's email) user->hash With this hash, the website can validate if the web user id is valid. A secret must be added in the skin settings by a Tixly admin. The hash is computed as a SHA256 over the web user Id + skin secret. Example: web user id: 544803 secret: uXL9aHWX3pumEEZsjU!U The hash will be SHA256(544803uXL9aHWX3pumEEZsjU!U) resulting in: 2ac9f3a26521d0194530daf3e68c88589d4490617059793dd2eba1b14b786b84 user->tags A list of “Customer Tags” that the user is connected to, which can be matched with “tags” on events to see which benefits the logged-in user can access. user->tags->id Id of the tag user->tags->name Name of the tag user->tags->abbr Abbreviation of the tag, not guaranteed to be unique and can be chosen by venue admins profile A URL that takes you to the user's profile page, or to the login page if not logged in. Note: delivery fees are not in the session information. Using personalised information to give pre-sale access and different ticket types to some customers With the session information on the customer, in combination with the benefits in the Tixly Event API, the website is able to show personalised information to the customers. For example if a VIP customer is logged in they can see their VIP prices, normal customers don't see these. Or you can show the [buy tickets] button earlier to your members, with this they can buy before the general public is able to do so (pre sale). The method used here is the Tixly event API containing all the normal sales dates and prices, but also the possible benefits the customers with certain customer tags can utilise. And example of an object list of benefits; { "Benefits": [{ "CustomerTag": { "CustomerTagId": 8, "Name": "Student", "Abbreviation": "ST" }, "Prices": [{ "TicketType": "Student", "Translations": [], "Prices": [{ "PriceZone": "1", "Price": 8.5 }] }] }, { "CustomerTag": { "CustomerTagId": 16, "Name": "Friend", "Abbreviation": "FR" }, "OnlineSaleStart": "2021-06-10T13:00:00", "OnlineSaleStartUTCUnix": 1620039600, "Prices": [{ "TicketType": "Friends", "Translations": [], "Prices": [{"PriceZone": "Rang 1","Price": 15}, { "PriceZone": "Rang 2", "Price": 10}], "ActiveFrom": "2021-06-12T08:00:00+02:00", "ActiveFromUTCUnix": 1623477600, "ActiveTo": "2021-7-12T22:00:00+02:00", "ActiveToUTCUnix": 1626069600, "TicketCount": "0-2" }], }, ] } Here you can see that Customers with the tag Student get to buy tickets for TicketType Student for a price of 8.5. For customers who are Friend there is an alternative, earlier, OnlineSaleStart and also an extra TicketType Friends, that is only available during a limited time period and for a max of 2 tickets. All the benefit data should be stored in the database of the website, so they are available to use in the web front-end. The webpage by default shows an event with the prices visible in the template, the other Benefits prices are in hidden elements. Then when the website gets a user object in the session information from Tixly. The user > tags > id can be used to display the benefit prices, the ones with the corresponding CustomerTagId.  The same goes for the buy tickets button. The default information is used to display the initial state of the button. But when the user has a CustomerTag Id that matches a benefit with an earlier date, the button state to show can be re-evaluated using that date. Example of what normal, or not logged-in users see and what friends see when after the OnlineSaleStart of the friend has passed but the normal OnlineSaleStart is still in the future. Default info / state: "OnlineSaleStart": "2024-06-26T13:00:00" Friends benefit has a different date: "OnlineSaleStart": "2024-06-10T13:00:00 Notes Benefits can add ticket types to the list of available ticket types. Benefits can not change the price of already available ticket types, nor can they remove ticket types. A customer can have multiple customer tags. Each tag can have a benefit. All beneficiary ticket types are available to such a customer, and as such should be shown to him.  When there are multiple beneficiary OnlineSaleStart dates, the first occurring OnlineSaleStart should be used. A customer tag or benefit does not influence the OnlineSaleEnd, SoldOut or SaleStatus, they remain the same for all customers. Each tag can have a benefit. All beneficiary ticket types are available to such a customer, and as such should be shown to him.  When there are multiple beneficiary OnlineSaleStart dates, the first occurring OnlineSaleStart should be used. A customer tag or benefit does not influence the OnlineSaleEnd, SoldOut or SaleStatus, they remain the same for all customers. Skins The Tixly part that the customers see it the online flow and the account pages. This can be styled and configuered in many ways. That configuration is what we call a skin and controls these things, and even more: Design elements, colors, logos. Webtrackers. URLs on the logo, continue shopping buttons. Default settings for many of the emails. URL of the skin, where is can be on a your domain, for example "https://billet.musikhuset.dk" or on a tix domain like this "https://tix.no/nb/notteroy" When using organisations, a skin can be limited to sell only from the configuered organisation.  Define what sites are allowed to read session information.

An event date in the Tixly System is a specific date on which an event is held. One or more event dates are always connected to an event group. In the online buying process, all event dates connected to a specific event group are presented in one sales link. To create multiple dates connected to a group, start by creating an event date and then copy it into multiple dates, so that each date has the same settings but different start and end dates and times. Create event date To create an event date, navigate to Administration > Events > Dates and press Add event in the upper right corner. Information Internal name (if active) The internal name of the event, needs to be unique for every event date. Name The name of the event. Visible on the ticket, in Box Office and online. Subtitle (Optional) The subtitle of the event. Visible on the ticket, in Box Office and online. Organisation If there are multiple organisations, select the correct organisation. Season Used as a filter in reports and determines which online exchange rules are applied to events within the season. Promoter Used as a filter in reports and internally in the Box Office sales module. Can also be included on the ticket layout.  A promoter can quickly be created from this field or via Administration > Events > Promoters where they are also editable. Date & Time / End date The start and end time of the event. The event is visible in Box Office until its end time. Set Box Office sales period When set to yes it is possible to define when events are available for sale in Box Office and when an event becomes visible on the sales dashboard. This hides events from users who do not have access to the event outside the sales period. Free admission event Used for free non-ticketed events. This information can be sent via the Tixly Event API and the event is also visible on the sales dashboard.  Once an event is saved as a free admission event it is not possible to change this. Confirmed If No, the event will be marked as red on the sales dashboard and no date or time will be printed on the ticket. It is, however, still possible to sell tickets for the event. Sale status Event status visible in the online buying process and in Box Office.  No status: Default status when creating an event. Few tickets: Based on WG settings, can be last 100 tickets or 10% of the available tickets for instance. Sold out: Based on WG settings, can be 0 tickets or 0% of the available tickets.  Cancelled: Manually select this status when an event is cancelled.  Sale not scheduled: Used if the event should be visible online, but no start sale date is known yet. Auto Sales Status If yes, the sale status will automatically change to few tickets and sold out once the rules set on workgroup level are met. Do not forget to set auto sale status to No when manually changing the sale status to few tickets or sold out. Contact Tixly Support to discuss the workgroup settings. Waiting list Activate the waiting list for the event. The waiting list is activated when the event has the status Sold Out.  Max waiting list tickets: Indicates the number of tickets customers may request per sign up, it does not reflect the total number of waiting list spaces.  CSV download: Once customers have signed up for the waiting list a Get CSV button will appear. This is a static list, but customers can remove themselves from the waiting list in their online account. Duration The duration of the event, visible under the information button in the Box Office sale view and in the Tixly Event API. Internal note Internal information visible for the Box Office staff in the information box. Event groups Which event group or groups should the date be connected to. An event can be connected to multiple event groups, however, there is always only one default event group connected. Categories (required) Select one or more categories. Used in Tixly Event API, in reports and to create customer segments using the Tixly customer segmentation tool. New categories can be created directly from this field and can be edited via Administration > Events > Categories. Tags Add an existing tag or create a new one. Tags can be used to create customer segments and are also     searchable in the event search bar. They can be used by third party software through Tixly Event API. In the example below the name of actor has been added as a tag to the event, making it possible to find an event based on a custom search term. VAT Select the VAT rate on the event. Enter the VAT rate when creating the event. In case that was forgotten and the event is already on sale, adding the VAT rate does not work retroactively. Gift card groups Add a gift card group to allow customers to pay for this event using a specific gift card.  Read more Hall & Prices Venue The venue where the event is held. Venues are created under Administration - Venues - Venues. Hall The hall inside the venue where the event is held. Unnumbered halls can be created under Administration - Venues - Halls. Numbered halls are created by Tixly Support. Configuration Select which configuration of the hall should be used for the event. A numbered hall can have multiple configurations with different price zones, entrances, ranking, seat notices, pre defined allocations and more. Include service fee If yes, a fixed additional service fee per order can be set up. This fee is paid by the ticket buyer and added on top of the full order amount. When two events in the same basket have a different service fee, the highest fee amount is used.  It's also possible to set the order fee in a basket rule, then it doesn't have to be added to each individual event.  Price template If applicable, select which price template should be used for this event. The price types and prices will be added automatically. It is still possible to add/delete ticket types and adjust the prices. Prices / Fees Switch between prices and fees to adjust the amount per ticket type / price zone. Fees Select which fees should apply to this event. Fees can be created or edited under Administration > Tickets > Fees & commissions. Ticket types Select which ticket types should be available on the event. It is possible to search for available ticket types in the search field. The ticket types are then priced for each price zone individually.  Ticket types can be created or edited under Administration > Tickets > Ticket types. Shopping cart icon By connecting a product to a ticket type a package can be created. The ticket type can not be bought without the product. In the buying process the final price of the ticket + product is shown. If the star to the left of the ticket type is fully filled it's a subscription ticket type. A half filled star indicates it can be used in the subscription and standard flow. An empty star indicates it's a standard sales ticket type. Once a numbered event is saved it's not possible to change the venue, hall or configuration of the event. It is possible to change an unnumbered hall into another unnumbered hall, however, only the name of the hall will change. The capacity of the hall will remain the same, but can be changed on event level.  Access Sales and reporting access If external users (e.g. a promoter) should have access to the event, select Local users + specific users.   Users / Organisations Add specific users or organisations to have access to this event. Users of the type promotor will show up in the dropdown. Other users can be added by typing out their full email address and clicking add external. On user level it is possible to disallow editing shared events.   Sale access Select where the ticket type should be available: Online: The ticket type will be available online for every customer. Box Office: The ticket type is mainly available in Box Office only. Online access to this ticket type can be given by creating a special offer link or via a customer tag. POS Api: The ticket type is available in the POS API for third party sales. Quota Defines the maximum amount of tickets that can be sold of that specific ticket type. Quota can only be set per event date.   Online quantity rule Define if there are any quantity rules connected to the ticket type. 0,2,4,6,8: The customer can buy 0, 2, 4, 6 or 8 tickets. Not 1, 3, 5, 7, 9 etc. 0,8-20: The customer can purchase between 8 and 20 tickets. No less than 8 and not more than 20. 0,2,4,6,10-20: The customer can purchase 2, 4, 6 or between 10 and 20 tickets. Always start with 0, otherwise the customer is required to buy the ticket type. Do not use spaces in the sequence.  How do you schedule a ticket type? A ticket type can be schedule by clicking the clock icon behind the ticket type. There it is possible to define a date and time interval where the ticket type will be available online. The left date picker is the start and the right date picker is the end of the interval.  Ticket types can also be scheduled in bulk: How do you add a voucher code? Read more on how to set up a voucher code here. Ticket type specific layout In addition, it is possible to connect a specific ticket layout to a ticket type. This will override the layout selected on event level for that specific ticket type   Membership scanning To be able to scan membership cards, it must to be configured on event level. A profile icon may appear behind free ticket types to which a membership can be linked. When a membership is scanned at the door, the system will automatically sell the customer a ticket for the linked ticket type. Membership scanning is only available on unallocated / unnumbered events. Internet Available online Should the event be available for regular online sales. Online sale start & end When does the regular online sale start and end. Visible online Set when the event should be visible online and when it's sent to the external site through the Tixly Event API. Event that is visible online but where sales is scheduled to start at a later date and time. Skin Choose the skin / branding for the weblink. The skin is not saved on the event, so select the correct skin before copying the link.  Weblink Link to the online buying flow for the specific event date.  Min & Max tickets online Minimum and maximum number of tickets a customer can purchase online per order for this event.  Numbered seating view Select whether customers will see the hall map in the online buying process. No hall view mode: The hall is not shown in the online buying process. Hall view without manual selection: The hall is shown, but the customer can't change the selected seats. Manual seat selection: The hall is shown and the customer is able to change the selected seats. No seats can be left empty between sold orders, but tickets can be booked in different (price) zones Manual seat selection any seat: The hall is shown and the customer is able to change the selected seats. Seats can be left empty between sold orders and individual seats in multiple sections can be selected.  Social distancing: Will allow an offset of X seats between orders and a max capacity on the hall. Pick seats first Set if the customer should select their seats or ticket type / number of tickets first in the online buying process. If yes, the hall will automatically open up when opening the link.  Display 360 If the venue has a 360 view, it can be activated here.  Best search option Only applicable in high pressure ticket sales, when you want to set how best seat available should work.  Show event start time as Set whether to show the date & time or only the date in the online buying process. Delivery types Select which delivery types should be available for the event. Permissions Select which permissions should be connected to the event. A permission that is connected to the season will automatically be connected to the events within that season. It is also possible to add event specific permissions. WebTrackers This is where event specific Facebook Pixel, Google analytics and Google Tag Manager can be added. Commonly used if an external promoter wants to add their tracker to their own events. Default web trackers of the organisation can be added to the skin and will automatically be connected to all events.  Additional Terms And Conditions Event specific terms & conditions can be added here. This will not replace the regular T&C's, but will add an extra checkbox. New additional terms & conditions can be created via Administration > Workgroup settings > Additional Terms and Conditions. Internet + Customer tag Add a customer tag to the event to give customers with certain tags access to specific ticket types that are not available in the regular sale and/or to give customers with a tag pre-sale access. Special note (shown online) Extra text field that is shown online below the ticket type selection. Only visible when pick seats first is not active or when using the event group link. Online sales Select whether to use the default confirmation e-mail layout or a dedicated one for the event. When the customer buys multiple events in one order, the default template will be sent.   Extra information If yes, an extra free text field is added to the online buying flow where the customer can answer a question or enter additional information. It could, for instance, be used to ask customers to enter their allergies or t-shirt size when selling products. This information can be found in the customer report. Information text: Explain what information is asked for, will be the header of the text field.  Required: If yes, the field will be mandatory and the purchase can not be finalised without entering something in the text field. Customer info on each ticket If yes, the customer needs to enter a unique name, email address or phone number for each ticket in the order. The information can be entered from the online receipt page. This information needs to be provided in order to be able to download the tickets. Information text: Information text that is shown to the customer on their online receipt page, could be used to explain what is required and why. Force unique: Select if the name, email, mobile number or a combination of them must be unique on each ticket in the order. Position By default all event dates within an event group are ordered by date and time. It is possible to change this order by giving the dates a different position.  Allow gift card Deactivate if gift cards should not be accepted as payment for the event. Special offer It is possible to create a special offer for a dedicated ticket type directly from this tab. Read more Products Connect products to the event date. New products can be created via Administration > Products > Products. Read more Layout  Ticket title Can be used to shorten or alter the event title on the tickets. If nothing is entered here, the name of the event date will be used. Subtitle  Can be used to shorten or alter the subtitle on the tickets.If nothing is entered here, the subtitle of the event date will be used.  Info text 1-3  Text that can be included on the ticket if the variables are available on the layout. Often used for extra information such as; The entrance will open 2 hours prior to show. Ticket for PDF, Epson, Godex, Boca, etc  Select if the default ticket layout should be used for this event or if there's another layout that should be used (numbered vs unnumbered layout for instance). PDF Ticket image  Upload an image that can be printed on the PDF ticket layout provided that the variable is available in the layout. Translations Add translations for online and ticket elements to activated languages.  Translations are also included in the API.  SMS/Email  Create automated emails and SMS. Read more Payment Types Only use this feature if specific Box Office payment types should be available for the event. Scanning If Override scan settings is set to Yes, it is possible to specify a time interval when it should be possible to scan tickets to the event. If no interval is set, the default work group time (X hours before and after the event) will be used. If the default times need to be adjusted, please contact your local Tixly Support. It is also possible to activate the unscan functionality on event level.  Finance If required, add an external reference number, department, account and/or dimensions to the events. These numbers will show up in several reports and the finance export. Refunds When an event is cancelled or moved it is possible to activate some self service refund options that will be available on the online receipt page of the customer. Activate the options by setting Refunds to Yes. Fees to refund All fees that should be included in the refund need to be moved to the right box. Fees that are set to include in refunds on fee level will automatically be added to the right box, but can still be moved to the left box to not be included in the refund. Include event product Set if event related products should be included in the refund. Refund money Set to Yes to offer a monetary refund.  Refund payment type: Select which payment method should be used for the refunds. If the order was paid for online, the refund will be made to the account number used to make the payment. Mail template: Select the email template that will be sent once the customer has requested a refund. Tickets bought before Only tickets that were bought before this date will have the option of getting a refund. E.g. if a show has been moved it is possible to offer a refund to all ticket buyers that bought tickets before the move was announced. Limit refund period Set to yes if the refund option should only be available until a specific date and time, after this time the refund options will no longer be available on the receipt page of the customer.  Available gift cards / donations To enable the option to transfer the ticket amount to a gift card / donation instead of requesting a refund, select one or more gift cards / donations by moving them to the right box. Customers can only request a refund, gift card or donate the full amount of the event. No partial refunds are available via the online receipt page.

The organisations module allows organisations / theatres to share one Tixly system. Facilitating the sharing of events, subscriptions, and other items, but also restricting access on several different levels. It also supports organisations that have a centralised ticketing operations team and local teams in the theatres. Each item created in Tixly belongs to a specific organisation or can be shared with multiple organisations. Event and sales access can be controlled based on which organisation(s) users have access to.  Add organisation To add a new organisation, go to Administration > Organisation Settings > Organisations, and click Add organisation in the top right corner. Information Name The name of the organisation. Abbreviation A short abbreviation for the organisation. Used on the sales dashboard to indicate which organisation the event belongs to. CRN Company registration number. Address Address information of the organisation. Theme Define what colour scheme will be used in Box Office.   Default Set to yes if this is the main organisation. Receipt Fill out organisation specific receipt information that can be used on (online) receipts. If no organisation specific information is provided the work group information will be used.  Layout Select specific ticket layouts that will be used on orders belonging to the organisation.  Finances Fill out organisation specific finance numbers that will be used if no event / item finance numbers are available.  For more information on organisations, please contact Tixly Support.

Download the new app by searching for Tixly Scanner on your device or tap the icons below. Direct download If Google Play Store is not available on your Android device, use the links below. Latest version Tixly Scan 2.0.4 Old versions Tixly Scan 2.0.2 Tixly Scan 1.4.6 Tixly Scan 1.4.5  Tixly Scan 1.4.3 Tixly Scan 1.4.2

The Tixly POS API shall only be used when making an integration for selling tickets such as a third party marketplace or a box office system. It can also be used to develop a stand alone web shop. It requires a country specific URL and a API key created in system. Documentation can be found in Postman by following the link below. Postman