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.
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 docsBuild 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.
