Platform, Security & Integrations / Integrations

Open API & Webhooks

An open API (Application Programming Interface — a defined way for other software to talk to and control your phone system) lets a developer connect your phone system to virtually any other business software, even ones we don’t offer a pre-built connector for.

What can I actually do with the API?

Common uses include: pulling call records into a custom reporting dashboard, triggering an action in another system when a call happens, automatically creating records in an internal tool, and controlling calls (placing, transferring, hanging up) from another application. If your business runs custom-built internal software, this is how it talks to your phone system.

What’s a webhook, in plain terms?

A webhook is an automatic notification — see Glossary: Webhook — your phone system sends to another application the instant something happens, like a call ending or a voicemail arriving, so that application can react immediately instead of having to constantly check for updates.

Do I need a developer to use this?

For anything beyond the pre-built integrations (CRM, helpdesk, Microsoft 365), yes — the API and webhooks are developer tools. If you have an in-house developer or IT partner, they can build against our documented API; if not, we can scope custom integration work as part of your project.

Is this secure?

Yes. API access uses secure, individually issued authentication tokens rather than shared passwords, so access can be granted, tracked, and revoked per integration without affecting anything else connected to your system.

How is this different from an SDK?

The API lets other software talk to your phone system from the outside. An SDK goes further — it lets a developer build calling itself directly into a custom application, like adding a “call” button inside your own website or app.