Webhooks

A webhook is Vivollo tapping your system on the shoulder. Instead of your code repeatedly asking "anything new yet?", you register a URL once, and Vivollo sends it a notification the instant something happens — a new message, a conversation update. It's the right tool whenever you want to react to events as they occur.

How it works

The idea is simple:

1. You stand up an endpoint on your side — a URL that can receive an HTTP request.
2. You register it as a webhook in Vivollo and choose which events you care about.
3. From then on, whenever one of those events happens, Vivollo sends your endpoint the details, in real time.

Your code does whatever you need with that: create a ticket, update a CRM record, post to a channel, kick off a workflow.

The events you can subscribe to

You pick exactly which events Vivollo should notify you about, so you only hear about what matters to you:

• message.created — a new message was sent or received in a conversation.
• conversation.updated — a conversation's status or state changed (for example, it was resolved or handed off).
• session.updated — a visitor's session details or metadata changed.
• user.updated — a customer's contact information changed.

Each notification carries the relevant details — the message and its conversation, the customer, the channel — so your system has what it needs to act without immediately calling back for more.

Setting one up

When you create a webhook, you provide:

• A name — so you remember what this one is for.
• The URL — your secure (https) endpoint that receives the events.
• The events — which of the above to subscribe to.
• Custom headers — optional, and the usual way to authenticate the request on your side (for example, a secret key your endpoint checks before trusting the call).

Reliable delivery

Networks hiccup and endpoints occasionally go down, so Vivollo doesn't give up on the first try — failed deliveries are retried, and you can review delivery logs to see what was sent, when, and how your endpoint responded. That makes it straightforward to debug an integration that isn't behaving, and gives you confidence you're not silently missing events.

Webhooks and the API, together

Webhooks and the REST API are a natural pair. The webhook tells you something happened; the API lets you fetch the full picture when you need more than the notification carried. A common pattern:

conversation.updated webhook fires → your code calls the API to pull the full conversation → you act on it in your system.

How many you can have

The number of webhooks you can register is part of your plan; see Plans & limits. And remember every webhook needs a valid API key context — set that up first if you haven't.