Booking
Attach a third-party booking link to events and event instances when your ticketing system isn't natively integrated
The Booking app is for organisations whose ticketing system isn't one of Basker's native integrations. It lets you attach a booking URL to each event or event instance, so theme blocks can render a booking button that takes the visitor to your ticketing flow on the third-party site.
Use it when:
- You sell tickets through a platform that doesn't have a Basker integration yet.
- Ticketing is handled outside Basker entirely — a venue's central box office, a partner's site, or a third-party event listing.
- You need a manual booking link as a stop-gap while a deeper integration is being set up.
Because there's no sync, you create and maintain events and event instances by hand inside Basker. The rest of this page covers that workflow.
Attaching a booking URL
Once the Booking app is installed, events and event instances gain a booking-URL field. Open the event or instance, paste the URL audiences should go to when they click the booking button, and save.
You can attach the URL at either level:
- On the event — useful when every performance of that event uses the same booking URL.
- On the event instance — useful when a specific date has its own booking URL (for example, a captioned performance on a separate ticketing page, or an opening night handled through a different supplier).
When both are set, the instance-level URL wins for that performance.
Creating events manually
Without sync, every event is one you create in Basker. See Create events for the full walkthrough — title, description, venue, season, dates, and the rest of the editorial detail.
Creating event instances manually
Each performance of an event is an event instance — a single dated occurrence that audiences see as a showtime. With Booking, you add each instance by hand:
Open the parent event
Open the event you want to add a performance to. Switch to the Instances tab where its existing instances are listed.
Create a new instance
Start a new instance. The parent Event should already be set; if you started from the Event Instances area instead, pick it.
Set the date and time
Fill in Start Date and pick its Timezone. These are the only required fields — most instances inherit everything else from the event.
Set any overrides
Override Title, Venue, Company, Duration, Season, Series, or Works if this performance differs from the event's defaults — opening nights, touring dates, and captioned performances usually need at least one of these.
Add the booking URL
Paste the booking URL for this instance, if it differs from the event-level URL. Use the Hide Start Time? toggle if you're not yet announcing the time, or Hide Event Instance? to keep it off the public site for now.
Save
Click Save. The instance appears on the event's listings, and the booking button on the live site routes to the URL you set.
For a production with many instances on a regular pattern, add the first instance and duplicate it to seed each subsequent date — adjust the date and any per-night overrides on each duplicate.
What's lost compared to a native integration
The Booking app only stores a URL. Compared to Tessitura, Spektrix, Elevent, Tixly, or Line-Up integrations:
- There's no sync of event detail back from the ticketing system, so any changes (cancellations, time shifts, rescheduling) need to be made by hand in Basker as well as in the ticketing system.
- There's no live availability data, no sold-out indicator, and no in-flow basket — just a button that links out.
- There's no preview gating — the URL renders the same regardless of whether the event is in draft or published.
If your ticketing platform gains a Basker integration in future, you can switch over without losing the manually-created events.