Ticket Administration
Learn how to manage your users’ tickets
The Tickets feature in Unidy provides a centralized hub for managing all tickets within Unidy. It allows you to search, view, create, edit, and delete tickets, ensuring streamlined workflows and quick access to essential information. Additionally, you can view the Tickets history log in the History section. Tickets always need to be linked to a certain ticket category.
Tickets
The Ticket interface provides an efficient way to manage all tickets stored in Unidy. You can view all tickets directly in the interface and use the search bar to locate specific ones by entering the ticket ID, title, reference, or the user’s email address.
For a detailed view of a specific ticket, simply click on the ticket ID. If you need to edit or delete a ticket, you can do so by selecting the appropriate icon located on the right-hand side of the ticket entry. Additionally, user profiles can be accessed by clicking on the user’s email address. This interface is designed to streamline ticket management and enhance productivity.

Detailed ticket view
The detailed ticket view allows you to access and edit all ticket information stored in Unidy. However, please be aware that, depending on your integration, any changes made may not be synced to the primary ticket management system.

Relevant data fields and descriptions
Attributes marked with a star are mandatory.
Field | Description |
ID | Unique identifier of the ticket in Unidy. It is required to update or delete the ticket via API. |
Reference* | Reference for the external ticket provider. it doesn't have to be unique. |
Title* | Title displayed in the ticket front end |
Text | Description text displayed in the ticket front end |
State* | The status of the ticket:
- active : ticket is valid
- passive : ticket is valid
- inactive : ticket is invalid
Expired tickets are set to inactive automatically based on the Ends at timestamp |
Starts At* | Timestamp when the ticket gets valid / the event starts |
Ends At | Timestamp when the ticket expires / the event ends |
Button CTA URL | URL of the ticket CTA. If left empty, the URL defined in the associated ticket category is set by default. |
Info Banner | Text displayed on a info banner in the ticket front end. Banner won’t be displayed if left empty. |
Metadata | Arbitrary information associated to the ticket. Can contain all the required information that cannot be stored in our standard fields. |
Payment State | States whether the payment was processed successfully
- payed = payment processed successfully
- not payed = payment still not processed successfully |
Price | Price of the ticket |
Currency | Currency of the ticket price. Follows the ISO_4217 standard. If left empty, ticket category currency is valid. |
Seating | Seating description |
User* | User account to the ticket is connected to |
Ticket Category* | Category of the ticket in Unidy |
Wallet Export | Flag for ticket that can be exported as wallet passes in Unidy |
Venue | The location of the ticket event |
Service* | Service that are enabled to access the respective ticket information. If you oAuth app is not associated to the service, you can’t access the ticket information. |
Source | Creation source of the ticket |
Created At | Timestamp of the ticket creation in Unidy |
Update At | Timestamp of the last ticket update in Unidy |
History
The History section displays all activity logs for the selected ticket. You can use the search bar in the top right corner to locate specific logs. For a more streamlined view, entries with no changes can be hidden by selecting the option in the right corner. Clicking on the ticket's title in the left corner will take you back to the detailed ticket view.

Relevant data fields and description
Field | Description |
Property | Ticket data field that was changed |
New Value | Current value of the data field |
Old Value | Value of the data field before the change |
Source | • Service: Change was made by a third party service
• API: Change was made by a third party API
• Admin: Change was made by the administrator |
Author | Party that made the change (if known) |
Update At | Date and time of the change |
How to Guides (Tickets)
The following chapter contains all relevant use cases, you need to know to work with tickets.
How to create a ticket
- Open the Tickets section in Unidy Admin.
- Click on the New button in the top right corner.
- Enter all the relevant information.
- Click on the Create Ticket button at the bottom of the page.
- The ticket is created in Unidy
How to edit a ticket
- Open the Ticket section in Unidy Admin.
- Search for the relevant ticket using the corresponding ID, title, reference or user email address.
- Ensure that this is the ticket you want to edit.
- Click on the pen icon or open the ticket and click on the Edit button in the top right corner.
- Update the respective data fields in the ticket.
- Save changes by clicking on the Update Ticket button at the bottom of the page.
- The ticket is updated in Unidy.
How to delete a ticket
- Open the Ticket section in Unidy Admin.
- Search for the relevant ticket using the corresponding ID, title, reference or user email address.
- Ensure that this is the ticket you want to delete.
- Click on the trash bin icon or open the subscription by clicking on the ID or title and click on the Delete button in the top right corner.
- Confirm the deletion of the ticket.
- The ticket is deleted from Unidy.
Ticket Categories
Here you can view, edit, and delete all Ticket categories stored in Unidy. You can search for ticket category by entering the ID or title in the search bar. For a more detailed view on the respective ticket category data, please click on the ticket category ID. You can also directly access the editing mode or delete a Ticket category by clicking on the respective symbol on the right hand side.


Ticket category information
Every tickets needs to be linked to a certain ticket category (i.e. home games, VIP, special events etc.). Only admin-authorized users are allowed to create new ticket categories via the Ticket Categories menu link. By clicking on the New button in the upper right corner, the administrator will be directed to a page where they must provide certain information to create a new Ticket category.

Required fields and description
Field | Description |
Title (required) | Title of your ticket category. You are free to choose its phrasing. It should be considered that this item is visual to the user. |
Visible for brand | Only applicable for multibrand instances. You can set up for which brand this Ticket category should be visible. |
Url (required) | User will be redirected to this URL (ticket or website) when clicking on the CTA button of the ticket category (see below). |
Description (required) | Description of your ticket category. You are free to choose its phrasing. It should be considered that these item is visual to the user. |
Currency | Tickets also have an attribute to define the currency of a price. This field is programmed according to the currency standard codes (ISO_4217). Here you can define a default currency for respective ticket category. UI displays the price with the correct symbol for the given currency. When currency in the single ticket is left blank, the default currency of the respective category is used instead.
Currency is stored with the ticket, so that service provider also see the correct currency associated to a price when fetching Ticket information from Unidy. In that case, the currency will also be returned when someone fetches the Ticket information through API. |
Button cta label | Text for the Call-to-Action (CTA) button on the ticket tile. By default it is set to “Manage” (see below). |
Logo | The logo has to be in a square format (min. 60x60 px and max. 500x500 px), can not be bigger than 1 MB and has to be a PNG image. An app we can recommend to optimize your images is https://squoosh.app/. |
Background image (optional) | A background image is not required. If you choose to not upload one, it will be the background color of your ID (see below). The background image has to be at least 400x100 px and the maximum image size can be 2000x500 px, the format has to be a JPEG and it can’t be bigger than 2 MB. An app we can recommend to optimize your images is https://squoosh.app/. |
Visible | It can sometimes be useful to prepare tickets in advance or to hide them if the ticket is unavailable for a short period of time. If enabled, this ticket category will be visible to the user as a tile with Call-to-Action (CTA) button (see below). |

How to Guides (Ticket Categories)
The following chapter contains all relevant use cases, you need to know to work with ticket categories.
How to create a ticket category
- Open the Ticket categories section in Unidy Admin Settings.
- Click on the New button in the top right corner.
- Enter all the relevant information.
- Click on the Create Ticket category button at the bottom of the page.
- The ticket category is created in Unidy
How to delete a ticket category
- Open the Ticket categories section in Unidy Admin Settings.
- Search for the relevant ticket category using the corresponding ID or title.
- Ensure that this is the ticket category you want to delete.
- Click on the trash bin icon or open the ticket category by clicking on the ID or title and click on the Destroy button in the top right corner.
- Confirm the deletion of the ticket category.
- The ticket category is deleted from Unidy.
How to edit a ticket category
- Open the Tickets categories section in Unidy Admin Settings.
- Search for the relevant ticket using the corresponding ID or title.
- Ensure that this is the ticket you want to edit.
- Click on the pen icon or open the ticket category and click on the Edit button in the top right corner.
- Update the respective data fields in the ticket category.
- Save changes by clicking on the Update Ticket category button at the bottom of the page.
- The ticket category is updated in Unidy.
Visibility and hiding of tickets and ticket categories
Hiding ticket categories or individual tickets can be useful when their primary purpose is background synchronization between systems rather than user-facing functionality. By default, all tickets are visible in the user interface, but you have two options for concealing them:
- Hide Ticket Menu Option: This setting removes all tickets from the user interface entirely.
- Hide Specific Ticket Categories: This option conceals all tickets linked to a particular category.
Additionally, entire ticket categories can be hidden if needed, providing flexibility in managing what is shown to users.
If no ticket and no ticket categories are displayed for a customer, then the menu link for tickets won’t be displayed at all.
When ticket categories are displayed but the customer has no tickets, a white box appears, informing them about the possibility of connecting tickets. This ensures clarity and guides the customer toward linking their tickets.
