Skip to main content
A web chat widget is a chat bubble on your website, answered by one of your agents. Visitors can type, and, if you allow it, tap to talk. Most people design widgets in the dashboard’s studio; the API lets you create and manage them from code, for example one widget per client site. Widget endpoints need webchat:read to read and webchat:write for every change. Chats from widgets land in the inbox with channel: "web".

Create a widget

The response is the widget, including its public_key (wck_…):

Publish and install

Visitors see the widget as it was when you last published. Publish after every change you want live:
Send {"studio_revision": 3} to publish only if nobody saved a newer design in the meantime. Then put one line on every page of the site, just before </body>:
The script is tiny. It adds the widget in a frame, so later design changes reach the site without touching this line.
The public key isn’t a secret: it’s meant to be on your website. What protects the widget is allowed_origins, the rate limits, and the fact that the key can only start chats with this one agent.

Change, rotate, delete

auto_reply_enabled: false stops the agent replying, so teammates answer every chat from the inbox themselves.