Mobile app only. Webhooks are configured through the Allo mobile app.
What are webhooks?
Webhooks let you receive real-time notifications from Allo to your own systems or applications. When an event happens in Allo (like a call ending or receiving an SMS), we send an HTTPS POST request to your specified URL. Common use cases:- Log calls to your custom database
- Trigger automations in your own systems
- Send notifications to internal tools
- Build custom integrations
How to set up webhooks
Step 1: Enable webhook
- Open the Allo mobile app
- Go to Settings
- Tap Integrations
- Select Webhooks
- Toggle Enable webhook on
Step 2: Configure your URL
Enter your webhook URL in the URL field. Requirements:- Must use HTTPS (not HTTP)
- Must be capable of receiving POST requests
- Must return a 2xx status code
Step 3: Select event types
Choose which events you want to receive: Call Received- Triggered every time a call finishes
- Includes call details, recording, transcript, and summary
- Triggered every time you receive an SMS
- Includes message content and sender information
Step 4: Test the connection
Before going live, test your webhook:- Scroll to Test the connection
- Tap Send
- Allo will send a test POST request to your URL
- Verify your endpoint receives the test data
- Your URL is correct
- Your endpoint is publicly accessible
- Your server accepts POST requests
- Your endpoint returns a 2xx status code
Webhook payload
Call Received event
When a call finishes, we send a POST request with the following data:SMS Received event
When you receive an SMS, we send a POST request with:Security best practices
Verify webhook authenticity
Recommended security measures:- Use HTTPS only
- Validate the request signature (if provided)
- Check the request origin
- Implement rate limiting
- Log all webhook requests
Handle webhook failures
Your endpoint should:- Respond within 5 seconds
- Return a 2xx status code for success
- Handle errors gracefully
- Implement retry logic if needed
- Allo will retry up to 3 times
- Retries happen with exponential backoff
- After 3 failures, the webhook is disabled
- You’ll need to re-enable it manually
Troubleshooting
Webhook test fails
Webhook test fails
Check these common issues:
- ✅ URL is correct and publicly accessible
- ✅ Using HTTPS (not HTTP)
- ✅ Endpoint accepts POST requests
- ✅ Firewall allows incoming requests
- ✅ Server returns 2xx status code
- ✅ Response time is under 5 seconds
Not receiving webhook calls
Not receiving webhook calls
Possible causes:
- Webhook disabled: Check if toggle is still on
- Event types not selected: Verify you enabled the right events
- Endpoint down: Test your server is running
- Failed deliveries: Check if webhook was auto-disabled after failures
Receiving duplicate webhooks
Receiving duplicate webhooks
Why this happens:
- Network issues can cause retries
- Allo retries failed deliveries
Webhook was auto-disabled
Webhook was auto-disabled
Reason:After 3 consecutive delivery failures, Allo automatically disables the webhook to prevent resource waste.Solution:
- Fix the issue with your endpoint
- Test that it’s working
- Re-enable the webhook in the app
- Run a test to verify