Developers
Bookitive's integration surfaces — the embeddable widget, the typed JS client, the partner API, and webhooks — and which to reach for.
Bookitive is built to plug into your own stack. There are four developer surfaces, each for a different job — this page helps you pick, and the rest of the section goes deep on each.
The four surfaces
| Surface | Use it to… | Auth |
|---|---|---|
| Widget | Drop the seat map + checkout into your own website. | None — public event |
| JS client | Build a fully custom checkout UI against the public API. | None — public event |
| Partner API | Read your events/orders/tickets from a server, or feed a turnstile. | API key / scanner device |
| Webhooks | React to orders and check-ins in your own systems. | Signed requests |
A rough decision tree:
- Sell on your own site, minimal code → embed the widget.
- Sell on your own site, your own design → the JS client for data, the widget's captcha bridge for safe submission.
- Pull data into a dashboard, CRM, or gate → the partner API.
- Be notified when something happens → webhooks.
Interactive API reference
Both machine APIs publish an OpenAPI spec and an interactive explorer:
- Public buyer API —
https://api.bookitive.com/public/v1/docs - Partner API —
https://api.bookitive.com/partner/v1/docs
@bookitive/js generates its types from the public spec, so the
TypeScript you write against it cannot drift from the live API.
(@bookitive/widget-js hand-redeclares its types, so those can drift.)
The widget and JS client talk to the public API with no credentials — they only ever expose what a buyer could see and do. The partner API is for your server with a secret key, and reads across your organization. Never ship a partner key to a browser.
Related
Lock Screen Live Activity
The automatic check-in Live Activity — a doors countdown that flips to live admission numbers on your Lock Screen and Dynamic Island, with the app closed.
Embed the widget
Embed the Bookitive seat map and checkout on your own site — the loader, every mount option, the events it emits, the controller API, and the captcha-safe checkout.