Ticket Reservations API: Sample Flows

This article presents possible use cases and corresponding sample flows that you can support. It provides a useful starting point as you plan your implementation.

Reserve tickets and process payments through checkout

This flow demonstrates the complete ticket purchasing process from initial reservation through payment completion. It shows how to temporarily hold tickets while site visitors complete their purchase, ensuring inventory is protected without overselling.

To reserve tickets and process payments:

1. After the site visitor clicks the checkout button, call Create Ticket Reservation with the site visitor's ticket selections.
2. Save the returned reservation id, eventId and expirationDate fields from the response.
3. Call Checkout to checkout the reserved tickets. This method redirects the site visitor to the Wix checkout. The site visitor completes payment through Wix Payments. There might be 3 outcomes:
   • The reservation status automatically updates to CONFIRMED upon successful payment. You can verify this by calling Get Ticket Reservation.
   • If payment isn't completed before the expiration time, the reservation automatically changes to EXPIRED status and tickets are released back to inventory.
   • If a site visitor decides not to complete their purchase, you can manually cancel their reservation to immediately release the tickets:
     1. Ensure the reservation is in PENDING or CONFIRMED status.
     2. Call Cancel Ticket Reservation.
     3. The reservation status changes to CANCELED_MANUALLY and tickets are immediately available for other customers to purchase.