Webhooks and API access, on every plan
Connect LiveChatDock to the rest of your stack. Webhooks and API access are included on the one plan, rather than locked behind a higher tier, so there is nothing to upgrade into before you can automate anything.
The seven events you can subscribe to
A webhook fires an HTTP request to a URL you choose whenever one of these happens. You pick which events each webhook listens for, so a Slack notification and a CRM sync can each subscribe to only what they need.
| Event | When it fires |
|---|---|
chat.started | Fires the moment a visitor opens a new conversation, before anyone has replied. |
message.created | Fires for every message, from a visitor or an agent, so you can mirror a conversation elsewhere in real time. |
chat.assigned | Fires when a chat is picked up, whether that happens automatically or an agent claims it. |
chat.closed | Fires when a conversation is marked closed, useful for logging resolution time. |
visitor.identified | Fires when a visitor is recognised, for example after they give an email address in chat. |
rating.received | Fires when a visitor rates the conversation. |
file.uploaded | Fires when a file is shared in a chat, with a link to the upload. |
Signed payloads, so you can trust them
Every delivery is signed with HMAC-SHA256 using a secret unique to that webhook. Check the signature on your end before you act on a payload, so a request that did not come from LiveChatDock gets rejected rather than processed.
If your endpoint is briefly down, a delivery is retried automatically, up to five attempts with an increasing delay between each one. You do not need to build your own retry logic for short outages on your side.
Five API key scopes
An API key carries one or more scopes, and it can only do what those scopes allow. A key used only to read visitor data should not also be able to send messages, so give each integration the narrowest set it needs.
| Scope | What it allows |
|---|---|
chats:read | List and read conversations. |
chats:write | Create, assign or close conversations. |
messages:read | Read messages inside a conversation. |
messages:write | Send messages into a conversation. |
visitors:read | Read visitor details, such as location and device. |
A Slack notification without a Slack app
If you want a message in Slack when a chat starts, paste a Slack incoming webhook URL into your workspace settings. LiveChatDock posts a short notification to that channel. It is a one-way notification, not a two-way Slack app, so for anything more than an alert, build on the chat.started and message.created events with the webhooks above instead.
No upgrade to connect
These features are not reserved for a higher tier. Every workspace can use them from the first day of the trial, with the same scopes and the same seven events available to everyone.
For the inbox these events come from, see the shared inbox feature. For staffing questions once you are connected to other tools, read how many agents you need for live chat.
Check what else is on the one plan, or start a 14-day trial and add a webhook from the dashboard.