Quick setup: Callbacks can be configured at multiple levels: account-wide defaults, per-application, per-trunk, or per-call. More specific configurations override broader ones.
Configuring Callbacks
Callback URL Requirements
- ✓ Must use HTTPS (not HTTP)
- ✓ Must be publicly accessible (not localhost)
- ✓ Must respond within 3 seconds
- ✓ Must return HTTP 200 status code
- ✓ Should handle POST requests
- ✓ Should accept
application/x-www-form-urlencodedcontent type (form data)
Callback Configuration Hierarchy
Callbacks are resolved in this order (most specific to least specific):1
Per-Call Callback
Callback URL specified when making a call.
status_url parameter in Make Call API2
Application Callback
Callback configured in Application settings.
callback_url in Application object3
Trunk Callback
Callback configured on SIP Trunk.
status_callback in Trunk configuration4
Account Default
Account-wide default callback URL.
default_callback_url in Account settingsApplication Callbacks
Configure Application Callback
Set up callbacks when creating or updating an application:Create Application with Callback
Application Callback Parameters
Trunk Callbacks
Configure Trunk Status Callback
Receive callbacks for all calls through a specific trunk:Update Trunk with Callback
Trunk Callback Use Cases
- Call Tracking: Monitor all calls through a specific trunk
- Department Routing: Different callbacks for sales vs support trunks
- Billing Integration: Track usage per trunk for chargeback
- Quality Monitoring: Collect metrics for specific carriers/trunks
Call-Level Callbacks
Per-Call Callback Configuration
Override application/trunk callbacks for specific calls:Make Call with Custom Callback
Callback Authentication
To verify that callbacks originate from Vobiz, configure shared secrets and verify HMAC signatures. See Callbacks for verification code examples.Testing Callbacks
For local development, use a tunneling service like ngrok to expose your local server publicly:https://abc123.ngrok.io/webhooks/vobiz) as your callback URL.