Tessitura
Connect Basker to Tessitura — sync productions and performances, manage TNEW templates, and deploy Blocks Office routes
The Tessitura app is Basker's deepest ticketing integration. It connects your Basker site to a Tessitura installation and handles four related jobs:
- Syncing productions and performances from Tessitura into Basker as events and performances.
- Mapping Tessitura keywords and web content into Basker fields and custom attributes.
- Powering TNEW (Tessitura Network Express Web) templates served from your Basker site.
- Powering Blocks Office templates for any Blocks Office routes your site exposes.
Connection
The Tessitura app needs connection details for your Tessitura REST API:
- The Tessitura host and API version.
- Encrypted REST credentials.
Once connected, Basker verifies the connection and confirms it can reach your Tessitura installation.
Sync settings
Tessitura sync runs against productions and performances. Configure:
- Default event sync settings — how new events from Tessitura are mapped into Basker.
- Default performance sync settings — how new performances are mapped.
- Modes of sale — which modes of sale your site uses, and how they appear on the public booking flow.
- Keyword filtering — which Tessitura keywords are imported as searchable attributes in Basker.
Sync runs on a schedule and on demand. Manual sync is useful when you've just made a change in Tessitura and want it reflected immediately.
Sync maps
Sync maps control which Tessitura data flows into which Basker fields. The Tessitura app settings include two mapping panels: one for productions (mapped to Basker events) and one for performances (mapped to Basker event instances).
Event-level fields you can map to in Basker
Title · Description · Duration · Start Date · End Date · and any custom attribute fields defined on your events.
Instance-level fields you can map to in Basker
Title · Start Date · Duration · Hide on Calendar · Booking Status · Booking Button Label · and any custom attribute fields defined on your event instances.
Tessitura data you can map from — at the event level
Drawn from the production season behind the event.
| Tessitura data | What it gives you |
|---|---|
| Description, Full Text, Short Name, Text 1–4 | The production's titles and descriptive copy, for mapping into event title and body text. |
| First and Last Performance Date | The date range the production runs across. |
| Production and Season details | The production and season this event belongs to — useful for grouping or filtering. |
| Keyword | A specific Tessitura keyword, pulled in by its title (for example a genre or audience tag). |
| Web Content | A named piece of Tessitura web content — picked from your installation rather than typed in. |
Tessitura data you can map from — at the performance level
| Tessitura data | What it gives you |
|---|---|
| Date, Description, Duration, Short Name, Text 1–4 | The performance's date, descriptive copy, and run time. |
| Doors Open / Doors Close | When the doors open and close for the performance. |
| Default sale start and end date/time | When the performance opens and closes for sale by default. |
| Status, Type | The performance's current status and its type, for driving booking status or labels. |
| AvailSaleIndicator | Whether the performance is currently on sale — useful for showing or hiding it automatically (see below). |
| Availability | How many tickets your mode of sale reports as available — used for sold-out and limited-seating treatments (see Availability and sold-out status). |
| Venue and seating details | The facility, seat map, zone map, and best-seat map behind the performance. |
| Time slot | The named time slot the performance falls into. |
| Campaign details | The marketing campaign attached to the performance, including its dates and status. |
| Publish dates | The window during which the performance is published. |
| Keyword | A specific Tessitura keyword, pulled in by its title. |
| Web Content | A named piece of Tessitura web content. |
Sync behaviour per field
Each mapped field has two options. Overwrite on sync (the default) means Tessitura overwrites the Basker field on every sync, regardless of any edits made in Basker since. Import once means Tessitura fills the field only if it is currently empty, then leaves it alone — use this for fields you intend to edit in Basker after the initial import.
Overrides
Mapping defaults apply to all events globally. Individual events can override the global defaults using the per-event mapping controls, without affecting any other events.
How the sync works
The Tessitura sync runs nightly. For each connected event it:
- Adds new performances found in Tessitura that don't already exist as instances in Basker.
- Updates existing Basker instances with current data from Tessitura, according to your configured field mappings.
- Does not delete instances. If a performance is cancelled or removed in Tessitura, its Basker instance is not automatically deleted or hidden. It remains on your site until an editor takes action.
This is by design — automatic deletion could cause data loss if source data changes temporarily or in error.
Cleaning up cancelled performances
If a performance no longer exists in Tessitura, open the event's Instances tab in Basker and hide the affected instance using the Hide Event Instance? toggle, or delete it manually.
Offsale performances and Mode of Sale
Basker uses your configured Mode of Sale (MOS) to determine which performances are imported from Tessitura. Only performances available in your configured web MOS are created as instances in Basker. A performance not in your web MOS at the time of sync is never imported and will not appear on your site.
If a performance goes offsale after being imported
Basker does not automatically hide existing instances when a performance goes offsale in Tessitura. The instance will remain visible on your site until an editor acts.
To automate this: in your instance-level sync map, map AvailSaleIndicator or Status from Tessitura to the Hide on Calendar field in Basker. With this mapping active, each sync will show or hide the instance based on Tessitura's current availability data.
If an offsale performance comes back on sale
It will be picked up on the next nightly sync and the instance updated accordingly. If you've set up the mapping above, Hide on Calendar will update automatically.
Availability and sold-out status
When you map Availability in your performance sync map, Basker stores the AvailableCount that Tessitura returns for your configured Mode of Sale — a count of how many tickets that mode of sale reports as available for the performance.
- An availability of 0 means the performance is sold out in that mode of sale.
- A positive number means tickets are still available.
How that count is presented to visitors — for example a "Limited seating" badge versus a plain "available" state — is a theme decision. The threshold for when a performance counts as "limited" rather than simply available is defined in your theme, not in Basker core, so two themes can label the same availability number differently.
If a performance you know is sold out still shows availability on your site, the mode of sale Basker is reading may be counting held or allocated seats (holds, comps, or allocations) rather than only publicly saleable ones. Choose or configure a Mode of Sale whose AvailableCount excludes held and allocated seats so that 0 reflects a true public sell-out.
TNEW
If your site serves TNEW directly, the Tessitura app provides:
- TNEW domain and routing settings.
- Approved domains for TNEW redirects.
- Custom CSS overrides applied to TNEW templates.
- Session-sharing configuration between your Basker site and TNEW.
The app also queues a static template regeneration whenever you change theme — so TNEW stays visually aligned with the rest of your site after a theme update.
For promo codes and tracking handoff to TNEW, see TNEW: promo codes and tracking parameters.
Blocks Office
Blocks Office routes follow the same pattern. Basker serves the Blocks Office templates with the active theme's styling, and queues a regeneration whenever the theme changes.
Booking from event pages
When the Tessitura app is installed and an event has a synced production, theme blocks that include a booking button automatically link to the right Tessitura booking URL.