Skip to main content
Webhooks allow you to receive real-time HTTP notifications when events occur in your application, such as incoming messages or delivery status updates.

​
Per-Application Configuration

Each application has its own webhook configuration. This means:
  • Different webhook URLs for different applications
  • Independent event subscriptions per application
  • Isolated webhook delivery and retry logic

​
Event Types

Subscribe to specific events to receive only the notifications you need:

​
SMS Events

Triggered when an inbound SMS or MMS message is received.
Triggered when an SMS message has been successfully sent to the carrier.
Triggered when an SMS message has been delivered to the recipient’s device.
Triggered when an SMS message delivery has failed.

​
WhatsApp Events

Triggered when an inbound WhatsApp message is received.
Triggered when a WhatsApp message has been successfully sent.
Triggered when a WhatsApp message has been delivered to the recipient’s device.
Triggered when a WhatsApp message has been read by the recipient.
Triggered when a WhatsApp message delivery has failed.

​
Webhook Configuration

When creating a webhook, you can configure: URL
  • The HTTPS endpoint where webhook payloads will be delivered
  • Must be a publicly accessible URL
Events
  • Array of event types to subscribe to
  • Subscribe to one or multiple events
Headers (optional)
  • Custom HTTP headers included with each webhook request
  • Useful for authentication or routing
See Webhooks Setup for detailed instructions on configuring webhooks for your application.