The Spektrix integration is built for theatre venues that also run a restaurant. When a ticket buyer opens your reservation widget, it reads their Spektrix basket and pre-selects the date of their show, so the times they see fall naturally before or after the performance. The guest books their table as normal, and the booking is linked to their Spektrix customer record.
Who this is for
This integration is useful if your venue:
- Sells tickets through Spektrix for performances, events, or experiences.
- Also takes restaurant bookings, ideally on the same evenings as those performances.
- Wants to offer dinner as a low-effort add-on to the ticket purchase, rather than asking guests to navigate a separate booking flow.
If your venue uses Spektrix but does not run a restaurant alongside, you do not need this integration. If your restaurant runs without a box office, the regular reservation widget is the right place to start.
What the integration does
The integration has two halves: one on the widget, and one on the customer record.
On the widget
When a ticket buyer with a Spektrix basket on the page opens your booking widget, the widget reads the basket and looks at the earliest event in it. It uses that to pre-select the date in the widget's date input on your site, so the guest lands on the same date as their show.
Because the slot list comes from your Make a Rezzy availability for that date, the times the guest sees naturally fall before or after the performance — without you having to maintain a separate "around the show" schedule.
Once the guest picks a slot, they enter their details and confirm the booking — on your own page with the inline widget, or on a Make a Rezzy booking page from a button. Either way the booking is linked back to their Spektrix customer, so their visit history can be updated. See Adding the widget to your site for the wider picture.
On the customer record
After a guest's restaurant booking is marked Completed in Make a Rezzy, the integration writes a short summary of their visit back to their Spektrix customer profile — the date of the most recent visit and the total visits to date.
The exact fields and how the write-back is wired up are covered in Field mapping.
What you need on each side
On the Spektrix side
- An API user with permission to read baskets and write customer attributes.
- Two customer attributes set up in your Spektrix Settings for the visit-history write-back — see Spektrix's Customer Attributes guide.
On the Make a Rezzy side
- A Make a Rezzy account for the restaurant, with the Spektrix tenant connected from the Integrations page.
- A reservation widget published with the Spektrix integration switched on.
The end-to-end walkthrough is in Setting up the sync.
What it does not do
Make a Rezzy and Spektrix solve different problems, and the integration is a small bridge between them.
- It does not sell tickets. Spektrix remains your box office. Make a Rezzy handles restaurant bookings only.
- Restaurant bookings do not become Spektrix orders. A table booking made through the widget stays in Make a Rezzy. Spektrix's order list will not see it.
- Spektrix tickets do not become Make a Rezzy bookings. The widget reads the basket only to help the guest pick a dinner time — the ticket itself stays in Spektrix.
- It does not change your seat plans. Make a Rezzy floor plans and Spektrix seat plans are unrelated.
Where to go next
- Setting up the sync — credentials, customer attributes, and turning the widget on.
- Field mapping — what flows where, between Spektrix and Make a Rezzy.
- Troubleshooting — fixes for the most common problems.
- Spektrix integration documentation — the reference for everything on Spektrix's side.