Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/Sumitbose5/tktplz/llms.txt

Use this file to discover all available pages before exploring further.

TktPlz supports four distinct event types, each with its own data model, booking flow, and configuration requirements. Choose the type that matches how your event is delivered and how attendees access it. This page explains each type in depth, including the specific fields and setup steps involved.
Seating events are held in a registered hall or cinema and give buyers the ability to select specific seats before checking out. This type is best for movies, theatre performances, concerts with reserved seating, and formal conferences.

How seating events work

Every seating event is linked to a hall and a screen within that hall. A hall can have multiple screens, each with a pre-configured seat layout. The seat layout determines which seats are available, how they are arranged by row and column, and what seat categories (types) exist.The total ticket count for the event is taken directly from the screen’s totalSeats value — you do not set a separate capacity.

Setting up a hall and screen

Halls and screens are managed separately and must exist in TktPlz before you can create a seating event. When creating the event:
  1. Enter the city and state where the venue is located.
  2. Select a hall from the filtered list.
  3. Select a screen within the hall.
  4. TktPlz checks for scheduling conflicts in real time. Screens enforce a 1-hour buffer between events — if another event ends at 6:00 PM, the earliest your event can start on the same screen is 7:00 PM.
If a screen is already booked for an overlapping window (including the 1-hour buffer), the “Next” button is disabled. Choose a different time slot or screen.

Seat categories

Each screen stores a seatTypeCounts JSON object that defines the category breakdown, for example:
{
  "Regular": 100,
  "Executive": 50,
  "Premium": 20
}
When you choose categorized pricing for a seating event, the form automatically reads these categories and asks you to set a price for each. You do not enter seat counts manually — they come from the screen configuration.

Seat layout builder

The seat layout builder (SeatLayoutBuilder) is available to halls managers. It lets you define:
  • Zones — named groups of rows (e.g. Regular covers rows A–D, Executive covers rows E–F, Premium covers rows G–H)
  • Rows — labeled A through Z; you can add or remove rows
  • Columns — the number of seats per row (configurable per row)
  • Gaps — column positions within a row that have no physical seat (e.g. 4,7 means columns 4 and 7 are aisles)
The seat schema stores each seat with a row, col, seatType, and boolean flags for isGap, isBlocked, and isBooked.

Pricing options

OptionBehavior
FlatOne price applies to all seats regardless of category
CategorizedEach seat type (Regular, Executive, Premium) has its own price

Subtypes available

Movie, Concert, Conference, Other.

Comparing event types

CapabilitySeatingOpenOnlineRegistration
Seat selectionYes (row/col)No (zone only)NoNo
Physical venueHall + screenAddressNoOptional
Platform link deliveryNoNoYesOptional
Custom form fieldsNoNoNoYes
Team sign-upsNoNoNoYes
Zone capacity limitsNoYesNoNo
Real-time slot checkYes (screen)NoNoNo
Flat pricingYesYesYesYes
Categorized pricingYes (seat types)YesYesYes

Build docs developers (and LLMs) love