Skip to main content

Ticket Distribution

Let a third-party platform distribute tickets and products hosted on SECUTIX, meaning owned and configured by the venue manager, through SECUTIX APIs.

The venue manager stays in control: it manages the venues and products available for sale, the assigned quotas, and the prices. The reseller replicates that catalog into its own inventory, sells against it from its storefront, and finalizes orders back on SECUTIX.

Orders are settled to the partner's account for later reconciliation and the tickets are printed by the partner, from barcodes returned by the SECUTIX APIs.

Example use cases​

  • The reseller replicates the venue manager's catalog into its own inventory and keeps it in sync as products, prices, and availabilities change.
  • The reseller sells the venue manager's products from its own storefront and finalizes the orders on SECUTIX, settled to the reseller's account.
  • The reseller prints tickets on its own stock — either from the barcodes SECUTIX assigns at order closing, or from venue-specific barcodes it generates in real time at order completion.
  • The venue manager drives prices on performances and matches from an external pricing engine, and resellers pick up the new prices through the catalog.
  • The venue manager distributes inventory hosted on another ticketing system, whose venue system exposes real-time availability and seat assignment.
  • The venue manager unlocks restricted tariffs for holders of a membership or loyalty card, validated in real time by the partner system that owns the card base.
  • A partner replicates a catalog configured in an external system into SECUTIX, or surfaces its own hotel and merchandising products through an inventory widget.

Architecture Overview​

Ticket Distribution Integration Architecture

Integration Steps​

The numbered steps below correspond to the flows shown in the architecture diagram.

  1. Initial Catalog Sync — Your backend calls the Catalog API to retrieve every product available on the sales channel: descriptions, names, pictures, dates, and product families. Use the per-family search endpoints, for instance Search On Sale Events. Store the result in your own inventory store.

  2. Inventory Webhook (coming soon) — After the initial sync, rather than re-fetching the catalog, you subscribe to the inventory webhook and SECUTIX pushes you the changes as they happen: new or updated products, availability movements, and price changes. Your platform implements the receiving endpoints — Push On Sale Events, Push On Sale Event Availabilities, Push On Sale Event Prices (equivalent endpoints exist for the other product families) — and keeps your inventory in sync without polling.

  3. Create Contact (optional) — The venue manager usually wants to know who its customers are, so your backend can create or resolve the customer through the Contact API before building the cart. See How to Create/Modify/Delete User Accounts.

  4. Create Order — Your backend uses the Sales API to build the cart, starting with an order that carries the operations for the selected products. Creating the order holds the reserved inventory for 15 minutes (a configurable duration) while the buyer completes checkout. Whether this call can run asynchronously depends on your quota model — see Dedicated vs shared quota. See also How to Complete an Event Sale and Understanding Orders and Sales.

  5. Close Order — Your backend finalizes the order, which settles the sale before the hold expires.

  6. Get Tickets & Barcodes — Your backend reads the finalized order details, which expose the generated tickets — including the barcodes that will be used at venue access control. Two barcode strategies are supported (see Barcodes & printing below). API references: Read Order, Get Ticket.

Dedicated Quota vs Shared Quota​

The venue manager grants each reseller authorization on quota pools (=contingents). The choice depends on how much demand the event draws — and it decides whether order creation and closure (steps 4–5) can be asynchronous or must be synchronous.

Shared quotaDedicated quota
Best forLow-to-mid-demand eventsHigh-demand events
WhyMaximizes visibility by exposing the same inventory across many channelsLittle concurrency between channels, since each gets its own allocation
Order create & closeMust be synchronousMay be asynchronous
  • Shared quota — many channels sell from the same pool, so buyers on different channels can compete for the same seats. Calls must be synchronous so every order validates against real-time availability and the pool can't be oversold. Ideal for low-to-mid-demand events, where the goal is to maximize reach across as many channels as possible.
  • Dedicated quota — the reseller's allocation is reserved for it alone, so there is no contention between channels. Order creation and closure can run asynchronously (submit and poll), which scales better for the heavy, bursty load of a high-demand event.

Barcodes & printing​

Tickets are printed by the partner on its own stock, so a barcode must be available for every ticket. Two strategies are supported:

  • Distributor-assigned barcodes — if you already own the barcode (pre-printed stock or your own numbering scheme), you can provide it per ticket when the order is closed — see Close Order. The barcode you supply is stored on the ticket and accepted at venue access control. It must be at most 128 characters and unique across your own tickets — uniqueness of distributor-supplied barcodes is your responsibility.
  • SECUTIX-assigned barcode at closing time — if you have no barcode of your own to supply, SECUTIX assigns its own barcode when the order is closed (step 5). It is returned in the order details at ticket granularity, and the partner prints exactly that barcode.

Usage Plan​

This integration pattern maps to the TICKET_DISTRIBUTION usage plan. Available tiers: BASIC (10 req/s), STANDARD (50 req/s), PREMIUM (250 req/s). See Rate Limits for full details.