Webhooks let Allo push events to your server in real time. When something happens — a call finishes, an SMS arrives, a contact is created — Allo sends an HTTPS POST request to your endpoint with the event data.Documentation Index
Fetch the complete documentation index at: https://help.withallo.com/llms.txt
Use this file to discover all available pages before exploring further.
How it works
- An event occurs in your Allo account (e.g., a call is completed).
- Allo sends an HTTPS POST request to the URL you configured.
- Your server receives the request, verifies the signature, and processes the event.
Available events
| Event | Description |
|---|---|
call.received | Inbound call starts ringing |
call.triggered | Outbound call initiated |
call.completed | Call finished with full data (recording, transcript, summary) |
tag.added | Tag added to a call |
tag.removed | Tag removed from a call |
sms.received | Inbound SMS received |
sms.sent | Outbound SMS sent |
contact.created | Contact created |
contact.updated | Contact updated |
Payload format
Every webhook uses the same envelope format:| Field | Type | Description |
|---|---|---|
topic | string | Event type (e.g., call.completed, sms.received) |
version | string | Payload version, always "2.0" |
timestamp | string | ISO 8601 timestamp when the event was sent |
data | object | Event-specific payload |
Quickstart
Create a webhook endpoint
Go to Settings > Webhooks in your Allo dashboard. Add your HTTPS endpoint URL and select the events you want to receive. The webhook applies to all Allo numbers in your workspace.
Handle incoming requests
Your endpoint receives POST requests with the event payload in the body. Return a
2xx status code within 20 seconds to acknowledge receipt.Verify signatures
Every webhook includes a cryptographic signature. Verify it to ensure the request came from Allo. See Verifying signatures.
Next steps
Event catalog
Full reference for all events and their payloads
Verifying signatures
Authenticate incoming webhooks with HMAC-SHA256