Developer overview

Most of Vivollo is no-code, and most teams never need to write a line. But when you do want to wire Vivollo into your own systems — your CRM, your backend, your data warehouse — the Developer tools are how. This section is for the technical members of your team.

There are three pieces, and they cover the three things you'll typically want to do.

The three building blocks

• API keys — the credentials that let your code talk to Vivollo securely. Everything else here starts with one.
• Webhooks — Vivollo reaching out to you, sending a real-time notification whenever something happens (a new message, a conversation update). For reacting to events as they occur.
• REST API — your code reaching into Vivollo, to read and work with your data: conversations, messages, collections, and more.

Which one do I need?

It depends on the direction you're working in:

• You want to pull data out, or push data in — "sync our conversations into our data warehouse", "add this article to a collection from our CMS". Use the REST API, authenticated with an API key.
• You want to react when something happens — "create a ticket in our system the moment a conversation is handed off", "log every new message to our CRM". Use a webhook so Vivollo tells you in real time.

Many integrations use both: a webhook to know when something happened, and the API to fetch the full details.

And inside flows, too

It's worth remembering that you don't always need code to integrate. Inside a flow, the API Call action lets the agent reach your external systems mid-conversation — looking up data and acting on it — with no developer work at all. Reach for the Developer tools when you need integration around Vivollo; reach for the API Call action when you need it during a conversation.

Start with API keys — they're the front door to everything else.