> Portal Navigation:
> 
> - Append `.md` to any URL under `https://dev.wix.com/docs/` to get its markdown version.
> - Pages are either content pages (article or reference text) or menu pages (a list of links to child pages).
> - To get a menu page, truncate any URL to a parent path and append `.md` (e.g. `https://dev.wix.com/docs/sdk.md`, `https://dev.wix.com/docs/sdk/core-modules.md`).
> - Top-level index of all portals: https://dev.wix.com/docs/llms.txt
> - Full concatenated docs: https://dev.wix.com/docs/llms-full.txt

## Resource: Introduction

## Article: Introduction

## Article Link: https://dev.wix.com/docs/api-reference/business-solutions/events/registration/ticketing/ticket-reservations/introduction.md

## Article Content:

# About the Ticket Reservations API

The Ticket Reservations API allows you to hold tickets for a specified time period during the checkout process. When visitors select tickets for an event, the system creates reservations to prevent other customers from purchasing the same tickets while the original customer completes their purchase. The API also provides advanced reservation settings, such as the ability to bypass availability limits.

With the Ticket Reservations API, you can complete the following tasks:

- [Create time-limited ticket reservations](https://dev.wix.com/docs/api-reference/business-solutions/events/registration/ticketing/ticket-reservations/create-ticket-reservation.md).
- [Delete a ticket reservation](https://dev.wix.com/docs/api-reference/business-solutions/events/registration/ticketing/ticket-reservations/delete-ticket-reservation.md) from the system records.
- [Retrieve a reservation](https://dev.wix.com/docs/api-reference/business-solutions/events/registration/ticketing/ticket-reservations/get-ticket-reservation.md), which is useful for tracking reservation counts and ticket availability across events.
- [Cancel a ticket reservation](https://dev.wix.com/docs/api-reference/business-solutions/events/registration/ticketing/ticket-reservations/cancel-ticket-reservation.md) to change a reservation status to `CANCELED_MANUALLY`.

## Reservation lifecycle

Understanding the reservation lifecycle is essential for effective implementation:

1. When a visitor selects tickets, reservations start in `PENDING` status with an automatic expiration time (typically 5 to 30 minutes based on [event settings](https://dev.wix.com/docs/api-reference/business-solutions/events/event-management/events-v3/introduction.md), the `reservationDurationInMinutes` field).
2. The system holds tickets exclusively for the visitor who proceeds to checkout. Other visitors can't purchase these specific tickets.
3. Reservations resolve in one of several ways:
    - **Confirmed**: Payment completion changes the status to `CONFIRMED`, securing the tickets permanently.
    - **Canceled**: Manual cancellation or payment failure changes the status to `CANCELED_MANUALLY` or `CANCELED`. Tickets are immediately released back to the available inventory.
    - **Expired**: Automatic expiration after the time limit changes the status to `EXPIRED`. Tickets are immediately released back to the available inventory.

## Before you begin

It's important to note the following points before starting to code:

- The site must have [Wix Events & Tickets](https://www.wix.com/app-market/web-solution/events) installed.
- The API requires existing ticket definitions. Create events and ticket types using the [Events V3](https://dev.wix.com/docs/api-reference/business-solutions/events/event-management/events-v3/introduction.md) and [Ticket Definitions V3](https://dev.wix.com/docs/api-reference/business-solutions/events/event-management/ticket-definitions-v3/introduction.md) APIs first.
- Advanced reservation settings like bypassing availability limits should be used cautiously to prevent overselling.
- For seat reservations, you need to implement custom logic to retrieve the seat selected by the customer.

## Use cases

- [Reserve tickets and process payments](https://dev.wix.com/docs/api-reference/business-solutions/events/registration/ticketing/ticket-reservations/sample-flows.md)

## Terminology

- **Ticket Reservation**: A temporary hold on specific tickets for a limited time period during checkout.
- **Ticket Definition**: The template or type of ticket (for example, 'General Admission', 'VIP') defined at the event level. For more information, see the [Ticket Definitions V3](https://dev.wix.com/docs/api-reference/business-solutions/events/event-management/ticket-definitions-v3/introduction.md) API.  
- **Line Item**: An individual entry in a reservation representing tickets of the same type, price, and seating.
- **Expiration Time**: The date and time when a `PENDING` reservation will automatically expire and release tickets.
- **Guest Price**: Custom pricing set by customers for 'pay-what-you-want' or donation-style tickets.
- **Pricing Option**: Different price tiers for the same ticket type (for example, 'Early Bird', 'Regular').
- **Seat Assignment**: Specific seat locations for assigned seating events (section, row, seat number).
- **Service Fee**: Additional fees applied by Wix for payment processing and platform usage.

@sdk_package_setup