Embed our checkout, or build with the APIs.
Hosted widget, supplier endpoints, and signed webhooks—on one TicketingHub stack.
Connect your booking systems.
Orchestrate sales, partners, and automation from one layer—APIs and webhooks included.
- Your site & checkout
- Booking widget
- OTAs & resellers
- Payment gateway
- Integrations
- Webhooks & events
- CRM & analytics
- Supplier & automation
Integration sequence.
From scoped access and sandbox credentials to OpenAPI validation and production webhooks.
Pick your surface. Embed the hosted widget, build with the REST APIs, or combine both.
Get sandbox keys. We scope access and hand off credentials with environment URLs.
Build against the reference. Interactive OpenAPI in Swagger UI, with sample requests and lifecycle events.
Go live. Switch to production keys, subscribe to webhooks, and monitor retries.
Integration surfaces
Embed the hosted widget when you don’t want to own checkout, or build with the HTTP APIs when you model baskets, products, and back-office flows yourself. Both surfaces share one OpenAPI reference, grouped by product area in Swagger UI.
Embeddable widget: Hosted checkout with your branding. Availability, payments, and confirmations stay on TicketingHub—your site supplies traffic and context.
Explore featuresHTTP APIs & webhooks: Supplier- and widget-facing endpoints live in the same reference. Pair REST calls with signed webhooks for bookings and lifecycle events your stack consumes.
View developer docsWhat the reference contains
Build basket and checkout flows for TicketingHub widgets from your server-side integration.
v1 covers established resources; v2 targets next-generation supplier automation—see the reference for endpoints and versions.
Receive signed HTTP callbacks when bookings and other events happen—verify signatures and keep your stack in sync.
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.