Skip to main content


Before you can buy a ticket, it first needs to be reserved in the OpenTicket system. Only when a ticket has been reserved, it can be added to an order. This system has two benefits. Firstly, reservations allow you to finish their order in a reasonable time without being rushed. Secondly, by requiring a ticket to be reserved before it can be added to an order, it will never happen that more tickets are ordered than that there are available.

Reservations last for 8 minutes, and have to be made for every ticket that need to be part of an order. After the 8 minutes have passed, a reservation will automatically drop, and a ticket had to be reserved again before the process of creating an order can continue.

Creating reservations

Thus, you first need to reserve a ticket. For this, you need the following information:

  • shopGUID: the GUID of the shop through which the ticket will be sold.
  • ticketGUID: the GUID of the ticket which is being ordered.

Use the required information to make a GET request to All the required information is embedded in the endpoint URL. See the following code blocks for examples of such requests.

$curl = curl_init();

curl_setopt_array($curl, [
"Authorization: Bearer $accessToken"
CURLOPT_URL => "$shopGUID/reserve/ticket/$ticketGUID"

$response = curl_exec($curl);

echo $response;

The response to the request indicates that a ticket has successfully been reserved. As you can see, the response contains a product fields as well. These fields are used to complete an order, but will not be explained in depth. However, note that the GUIDs listed correspond to the ticketGUID and the GUID of the eventDate attached to this ticket.


For the shown API requests, the endpoint is used, which is slightly different from the endpoint that was used in the documentation thus far.