<aside> 🌎

Webhooks are automated HTTP callbacks that enable real-time event notifications. When a specific event that you subscribe to occurs in Vaspian One, the system immediately sends an HTTP POST request to your configured endpoint with relevant event data.

This push-based approach allows your applications to react to call events instantly without continuously polling the Vaspian API. Webhooks are ideal for integrating telephony events into CRM systems, analytics platforms, logging services, or custom business workflows.

</aside>

Successful inbound call with recording and transcript

sequenceDiagram
	participant Caller
	participant SBC as Vaspian SBC
	participant CRS as Call Router
	participant Ext as Extension 101
	participant WH as Customer <br> Webhook Endpoint
	participant Store as Customer Storage <br> (Transcipt & Recording)

	Caller->>SBC: Inbound call
	SBC->>CRS: Create session
	CRS->>Ext: Ringing
	CRS-->>WH: HTTP POST event=Call Ringing
	Ext->>CRS: Answer
	CRS-->>WH: HTTP POST event=Call Answered
	Ext<<->>Caller: Conversation
	CRS-->>WH: HTTP POST event=Call CDR
	CRS-->>WH: POST event=Call Recording (file_url token)
	CRS->>Store: Save recording
	CRS-->>WH: HTTP POST event=Call Transcription (file_url token)
	CRS->>Store: Save transcript
	WH->>CRS: 2xx ACK for each event

Vaspian One Webhook Capabilities

Vaspian One can send webhooks for:

• Inbound calls: Events triggered when external parties call into your system
• Internal calls: Events for extension-to-extension communication within your organization
• Outbound calls: Events generated when your extensions place external calls

Extension-Level Event Configuration

Webhook events are configurable on a per-extension basis, giving you granular control over which extensions trigger notifications and which events you want to capture. This allows you to:

• Monitor specific extensions or teams without generating unnecessary webhook traffic
• Subscribe only to relevant events (e.g., recordings and transcriptions for support lines, CDR for billing extensions)
• Implement different integration logic for different departments or use cases

For example, you might configure your sales extensions to send Call Answered and Call Ended events to your CRM, while support extensions send Call Recording and Call Transcription events to your quality assurance system.

Supported Events