Skip to main content
Webhooks send an HTTPS notification to your application when a supported event happens in your Visito workspace, such as a new message, a delivery update, a handoff, or a CRM opportunity change.

​
Choose your starting point

Dashboard setup

Create and manage endpoints with your admin login—no API key needed. Follow the illustrated walkthrough to test locally with ngrok, inspect deliveries, and troubleshoot retries.

API reference

Manage subscriptions programmatically. Find routes, required scopes, event payloads, signature verification, and delivery behavior.

​
How delivery works

  1. Create a subscription with a public HTTPS destination and the events you need.
  2. Save the endpoint’s signing secret and verify incoming requests before processing them.
  3. Accept events durably, deduplicate by event ID, and monitor delivery attempts.
Events contain metadata and resource IDs. Fetch additional content through the API with the appropriate permissions. Delivery is at least once, without guaranteed ordering; failed requests receive up to six automatic retries after the initial attempt.

​
Dashboard or API?

Both paths use the same event types, signing, and delivery system. The difference is how you manage the subscription and authorize delivery. Dashboard admins can manage both types. An explicit transfer to dashboard management preserves the endpoint and history, but removes dependence on the owning credential. Ordinary edits do not silently change the authorization mode.
These guides cover M2M event subscriptions. Webhooks attached to Capture Data actions are configured separately under Actions.