Booking widget
The Kwickblocks booking widget runs in the guest’s browser on the venue’s website. It calls its own routes with a publishable key in the X-KB-Publishable-Key header, not an integration key.
- A publishable key is public by design: the browser holds it. It reaches only the widget’s routes listed here, never the integration operations.
- An integration key on a widget route answers
401invalid-key, and a publishable key on an integration route does the same. - Publishable keys are managed per venue by the venue’s admin under Admin, Integrations, Integration keys, in the Widget keys section.
The widget’s flow is: load the venue’s configuration, show free times, hold a time while the guest types, add the guest (and any extra contact), then confirm the booking from the hold. If a deposit is due, the guest pays in the browser and the widget polls the booking’s status.
These routes are documented so the contract is complete. To build your own booking experience, use an integration key and the availability and booking operations instead; they have no browser-only steps.