Skip to main content

Overview

The previous section of the documentation describes how to create an event and a ticket for that event. In this part of the documentation, you will set up a waiting list resource which can be used to allow a customer to add themselves to a list of interested buyers. The process of creating a waiting list is very similar to the creation of any other resource. As before, you can also create a waiting list through the dashboard. However, the documentation focuses on setting up a waiting list through the Waiting List API.

Resources​

Event
Event
Waiting list
Waiting list
Signup
Signup
has
has
registers
registers
Text is not SVG - cannot display


The Entity Relation (ER) diagram extends the diagram shown before. As you can see, the event resource has been added to the diagram, along with its relations to the waiting list and signup resources. The remainder of this section explains the waiting list and signup resources.

You can find the explanation of the shop resource in a previous section of the documentation.

Waiting list​

You need to create a waiting list that stores relevant information about an event's waiting list,
such as type and allow_quantity.

Event relation​

As the diagram above shows, a waiting list and an event are related. An event must exist before you can create a list for that event. The Weeztix system reflects this as well: you must first create an event, and only then a waiting list can be created.

After you create an event, you can associate one waiting list resource with it. Thus, each event can be associated with zero or one waiting list resource. Similarly, each waiting list belongs to exactly one event.

Signup​

After you set up a waiting list customers can show interest in sold out events by signing up to be added to the list and let organizers know their details such as their name and email.

Event relation​

As the diagram above shows, a signup and a waiting list are related. The Weeztix system reflects this as well: you must first create an waiting list, and only then a signup can be created.

After you create an waiting list, you can associate many signup resources with it. Thus, each signup belongs to one waiting list resource, and each waiting list has many signups.