The previous section of the documentation describes how to create an
event. In this part of the documentation, you will make tickets for this
event. These tickets can eventually be sold through shops, but since shops are completely separate resources, they are described in a separate section. The process of creating tickets is similar to the creation of events, but requires a new operation: resource attachment. This operation allows you to easily relate resources to each other, and will be discussed in the following parts of the documentation. As before, you can also create tickets through the dashboard. However, the documentation focuses on setting up all the necessary resources through the API.
The Entity Relation (ER) diagram extends the diagram shown before. As you can see, the
ticket resource has been added to the diagram, along with its relations to the
eventDate resources. The remainder of this section explains the new
ticket resource and its relations. You can find the explanation of the other resources in the previous section.
As per usual, you need to create a
ticket that stores relevant information about a ticket, such as its
As the diagram above shows, a
ticket and an
event are related. This makes sense since an event must exist before you can make tickets for that event. The OpenTicket system reflects this as well: you must first create an
event, and only then a
ticket can be created. The
ticket uses the
event to indicate to which event the ticket grants you entrance.
After you create an
event, you can associate many
ticket resources with it. Thus, each
event can be associated with zero or more
ticket resources. On the other hand, each
ticket is associated with exactly one
As has been shortly mentioned before, it is possible to sell day-based tickets through the OpenTicket system. To avoid any confusion, this will not be discussed in detail in the documentation. However, this feature does introduce a relation between the
eventDate resources, which you need to take into account when you create a
ticket. In essence, a ticket sells access to an event for a specific timeslot. The OpenTicket system represents this by attaching
eventDate resources to
ticket resources, such that each
eventDate represents a certain timeslot of an event.
Because of this, there exists a relation between
eventDate. Explaining the cardinality of the relations requires a more in-depth explanation of day-based events, and is therefore omitted from this documentation. Instead, the documentation assumes that an
event only has one
eventDate associated with it.
In the following sections, you will create the above-mentioned resources in the OpenTicket system through the API. To keep this as clear as possible, only required fields for creating these resources are shown. However, in practice, there is much more information that can be added to these resources. The API reference mentions all additional fields that can be added to these resources.