Software integration

Webhooks

Route calls on your own data or trigger actions in your software automatically.

Webhooks let Voxbi notify your own systems the moment something happens on a call. When a call starts, ends, is missed, or reaches another event you care about, Voxbi sends an HTTP request to a URL you specify. Your system receives that data and can act on it: log the call, update a record, send an alert, or trigger any workflow you have built. The logic lives in your system; Voxbi supplies the signal.

This is the pattern for connecting Voxbi to business tools and processes that are not covered by a named integration. If you have an internal application, a custom CRM, a ticketing system, or an automation platform you want to keep informed about call activity, a webhook gives you the data in real time without polling. Alongside the Voxbi API, which lets you read call history, manage call recordings, send SMS, and programmatically control telephony, webhooks complete the picture by pushing events to you the instant they occur.

When you'd use webhooks

  • An internal helpdesk that should create a ticket automatically when a support call is missed during business hours, so no call goes unacknowledged even if the queue is unattended.

  • A business analytics or reporting tool that needs accurate, real-time call data fed directly into it without manual exports or scheduled polling of the call history.

  • An automation platform where an incoming call from a known customer number should trigger a lookup and push customer context to the agent before they pick up the phone.

How webhooks work in Voxbi

  1. Prepare an endpoint in your system

    Your system needs a URL that can receive an HTTP POST request and process the JSON payload Voxbi sends. This endpoint should be accessible from the internet and return an appropriate response code so Voxbi knows the delivery succeeded.

  2. Configure the webhook in Voxbi

    In the Voxbi Cockpit, navigate to the webhook or automation settings and add your endpoint URL. Select the call events you want to subscribe to, such as call started, call ended, or call missed.

  3. Receive and act on the event

    When the subscribed event occurs, Voxbi sends the call data to your endpoint. Your system processes the payload and runs whatever logic you have defined: writing to a database, sending a notification, creating a record, or triggering a downstream process.

  4. Combine with the API for two-way workflows

    Webhooks deliver events from Voxbi to you. The Voxbi API lets you go the other direction: read call history, retrieve recordings, send SMS, and control telephony programmatically. Combining the two gives you full two-way automation between Voxbi and your stack. API documentation is available at docs.voxbi.com.

Frequently asked questions

What is the difference between a webhook and the Voxbi API?

A webhook is event-driven: Voxbi sends data to your endpoint when something happens, without you having to ask. The API is request-driven: your system calls a Voxbi endpoint when it needs information. Most integration patterns use both: webhooks for real-time triggers, the API for on-demand data retrieval.

Do I need a developer to use webhooks?

Setting up a webhook endpoint requires some technical capability, as your system needs to be able to receive and interpret HTTP requests. If your team uses an automation platform that supports webhooks as an incoming trigger, that platform may handle the endpoint for you, reducing the amount of custom code needed.

What data does Voxbi include in a webhook payload?

Webhook payloads contain call event data. The precise fields depend on the event type, but typically include the caller number, destination, timestamp, call duration where applicable, and a call identifier. Refer to the Voxbi API documentation at docs.voxbi.com for the current payload specification.

Can I use webhooks to route calls based on data in my own system?

Webhooks can feed call events into your systems, and the way routing decisions feed back into Voxbi call flows depends on your integration design. If you want a routing workflow that depends on external data returned in real time, contact the Voxbi team to discuss your use case before building it.

See Voxbi in your business.

Talk to us or to a certified Voxbi partner.