TicketingHub for developers.
Embed the booking widget, build your own checkout with the Widget API or connect your systems with the Supplier APIs and webhooks, with every endpoint in the developer documentation.
Embed the booking widget on your website.
This is the live widget your guests book in: add a ticket to try it.
Embed the widget. Add it to your website with a short snippet and test it before you go live.
Use your own colors. Hosted checkout in your colors, on your own website.
Take payments through TicketingHub. Availability, payment and confirmation stay on TicketingHub.
Explore selling online with the booking widget.
See the widget live on Immersive Gamebox’s websiteBuild your own checkout with the Widget API.
Your checkout gets availability from the API and confirms the booking after payment.
Get availability. Retrieve the dates and times a guest can book.
Build the basket. Add tickets and the guest’s details to the order.
Keep credentials on your server. Requests run through your server, and your integration takes payment before it confirms the order.
Connect your systems with the Supplier APIs and webhooks.
Each new booking is sent to your tools, and to your own system as a signed webhook.
Work with your account. The Supplier APIs manage products, bookings and operations from your own systems.
Receive signed webhooks. Get a notification when a booking is confirmed, canceled or updated.
Verify and retry. Check each signature on your server; the documentation explains payloads and retries.
From your first request to launch.
Tell us what you’re building. Share your booking flow, the systems you want to connect and the data you need.
Confirm your access. Work with our team on the API access and setup your integration needs.
Build and test. Use the API reference to explore endpoints, check request formats and test your booking flow.
Prepare for launch. Check payment handling, error responses and the webhooks your integration uses.
Frequently asked questions.
Do you offer public, self-serve API keys?
We enable API access after a short conversation about your use case so we can point you to the right surfaces and environments. Book a demo to get started.
What's the difference between the Widget API and the Supplier APIs?
The Widget API helps you build server-driven flows around our embeddable checkout. Supplier APIs are for managing products, bookings, and operations programmatically. Many teams use both.
How do I test before production?
We provide environment-appropriate credentials and documentation so you can validate integrations safely. Your contact at TicketingHub will confirm which endpoints to use while you build.
How are webhooks authenticated?
Webhooks are delivered over HTTPS and include signatures you should verify on your server. Treat the signing secret like any other credential—store it server-side only.
Can I get implementation help?
Yes. Our team supports partners through onboarding, edge cases, and go-live reviews—especially when you're connecting payments, access control, or custom reporting.