Cannon VoIP Help

The API and webhooks: connect your own software

API keys sign into the same API the apps use; webhooks push events to your systems.

Updated September 16, 2026

API keys

On the Developer page, create a key and pick its scopes. The key signs into the same REST API the portal and apps use, so anything you can see in the portal, an integration can read or manage within the scopes you grant. Scopes cover nearly every module, view and manage; keys can never manage users or roles, sign porting documents, or touch reseller controls.

The key is shown once at creation. Store it like a password.

Use it as a bearer token:

curl -H "Authorization: Bearer cvk_..." https://app.cannonvoip.com/api/calls?when=today

Webhooks

Register an https endpoint and pick events: finished calls, missed calls, texts in and out, new voicemails, faxes, meetings created, recordings ready, tickets, new contacts, port-out activity.

Every delivery is signed: the x-cannon-signature header is an HMAC-SHA256 of timestamp.body under the endpoint's secret, so your receiver can prove the event came from us. Failed deliveries retry with backoff; an endpoint that fails 25 times straight is switched off visibly rather than hammered forever.

The recent-deliveries log

The Developer page shows the last deliveries per endpoint with status and error, so "did the webhook fire" is a look, not a guess.

Was this helpful?
← All help articles