Skip to main content
All integrations
Ticketing & CRM Beta

Tixly

The CMS for Tixly, so your website stays in step with what is on sale.

Basker is the CMS and website builder for arts organisations on Tixly. Bring your Tixly events onto your site through the Tixly event API, with the branded buying process carrying patrons through to checkout.

Integration type
Ticketing & CRM
Status
Beta
Scope
Tixly ticketing and the Tixly event API.

What the Tixly integration gives you

  • The CMS layer for Tixly

    Basker manages the website and content layer. Tixly remains the ticketing system.

  • Event listings

    Your Tixly events surface on the pages where patrons are already looking, pulled through the Tixly event API.

  • Branded buying process

    Patrons book through Tixly's branded buying process, so checkout stays on brand.

  • Map once

    Connect your account, map Tixly events to Basker collections, and keep listings in step.

Overview

Basker is a CMS and website builder for arts organisations that run on Tixly. It connects your website to Tixly so your Tixly events stay live without manual exports. The integration is in beta: it pulls your events through the Tixly event API onto your site, and Tixly's branded buying process carries patrons through to checkout.

Tixly's role

Tixly is a ticketing platform built for performing arts venues and culture houses. It manages events, ticketing, and the buying process for patrons. For venues that run on it, Tixly is where the operational ticketing data lives.

Basker's role

Basker is a content management system and website builder for organisations that put on live events: theatres, performing arts venues, and cultural institutions. Basker is not a ticketing system. It gives marketing, ticketing, and digital teams a place to build pages, publish content, and present Tixly events on the public website.

How does the Tixly integration work?

Connect your Tixly account and map your events to Basker collections through the Tixly event API. Your listings surface on the pages patrons already visit, and Tixly's branded buying process takes them through checkout. There are no spreadsheets, manual exports, or bespoke integration code to maintain.

Why Basker is the right CMS for your Tixly site

Basker pairs your Tixly event listings with a visual, block-based editor and live preview on any device. Teams can edit themes in code or directly in the browser, which supports bespoke designs without slowing down day-to-day publishing. Basker is delivered as SaaS on a single shared codebase with continuous updates, so there is nothing to install and no version to fall behind on.

Features

  • Event listings pulled through the Tixly event API.
  • Tixly's branded buying process for an on-brand checkout.
  • Events mapped to your Basker collections.
  • No manual exports or bespoke integration code to maintain.
  • Visual, block-based editor with live preview, and theming you can edit in code or the browser.

Frequently asked questions

Is Tixly a CMS?
No. Tixly is a ticketing system. Basker runs the CMS and website layer that connects to it.
What is the best CMS for Tixly?
For arts organisations on Tixly, Basker is built to do the CMS job around Tixly: manage pages, publish content, and present your Tixly events on the public website. It is not a replacement for Tixly.
Does Basker replace Tixly?
No. Basker is the website and content layer. Tixly still handles ticketing and the branded buying process.
Is the Tixly integration available now?
It is in beta. If Tixly is part of your stack, get in touch and we will get you set up.
Will I need a separate Tixly subscription?
Yes. Tixly is a third-party platform with its own agreement. Basker connects to your existing Tixly account.

Related integrations

View all

See Basker on your venue's site

Talk to sales and we will show your Tixly data running on a Basker page, built around how your team actually works.