Skip to main content

Website Integration: Catalog Display

The simplest website integration. Your website displays event listings fetched from SECUTIX APIs, and redirects users to the standard ticketshop for purchasing.

Ideal when you want to showcase events on your own branded website without building a purchasing flow.

Architecture Overview​

Website Catalog Integration Architecture

Integration Steps​

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

  1. Retrieve Catalog — Your backend calls the Catalog API to retrieve in real-time all products available on the sales channel. This includes product descriptions, names, pictures, dates, tariffs, prices, and sales periods across all product families (events, competitions, memberships, season tickets, visit passes). Since catalog calls are scoped to a {salesChannelId}, each channel can expose different products and pricing. The API is designed to be called on demand — no client-side caching is required. See Catalog Overview

  2. Availabilities — For each product on sale, your backend fetches real-time availability using the dedicated availability endpoints. Availability endpoints exist at product, event, performance, and seat level. The APIs deliver up-to-date data directly — no client-side caching or polling strategy is needed.

  3. Redirection — When a user visits your website, he will browse the catalog and availability data retrieved in steps 1 and 2. When the user selects tickets, your application redirects them to the standard SECUTIX Ticketshop to continue the product selection (tariff, seat) and checkout experience. This redirection is orchestrated by your frontend, using Deep Links (Redirect API) integrated into purchase buttons.

  4. Authentication & SSO — When the user is redirected to the SECUTIX Ticketshop, they need to be identified. Two scenarios are supported: either the user logs in directly at the ticketshop, or they are already authenticated on your website via your own Identity Provider (IdP) and SECUTIX seamlessly re-authenticates them using SSO (OIDC). In the SSO scenario, SECUTIX acts as a Service Provider (SP) and delegates authentication to your IdP — the user experiences no additional login step. See Contact SSO (SECUTIX as Service Provider) for configuration details.

  5. Load Handling — The SECUTIX Ticketshop is protected by PeakProtect, which manages traffic when a large number of users access the ticketshop simultaneously. PeakProtect ensures a smooth experience using a FIFO (First-In-First-Out) queuing approach. If you anticipate high-traffic events (on-sales), the SECUTIX team can provision additional resources to ensure the best possible customer experience.

Usage Plan​

This integration pattern maps to the TS_CATALOG usage plan. Available tiers: BASIC (8 req/s), STANDARD (40 req/s), PREMIUM (200 req/s). See Rate Limits for full details.