Tessitura Data Reaches Event Instance Endpoints
Build production event pages from Tessitura event instance endpoints, without duplicating ticketing data or replacing Tessitura as the source of truth.
Public themes used to see Tessitura values only as separate admin-only metadata. Tessitura data now reaches event instance endpoints, so public themes can work with ticketing-aware instance data directly.
Production-ready event pages
This makes event detail pages, calendars, and ticketing handoffs more production-ready. When the theme has access to full instance data including times, modes of sale, and availability, it can render a complete event page without requiring editors to manually duplicate information from Tessitura into content fields.
Basker and Tessitura in their right roles
The release reinforces the core product pattern: Tessitura remains the authoritative source for ticketing data, while Basker uses that data to power the visitor-facing experience. Both systems work within their domain, and editors keep editorial ownership in Basker without touching the ticketing records directly.