How webhook delivery works
1
Register an HTTPS endpoint
Add an endpoint in your Dugble team settings and select one or more
supported events your application needs.
2
Return a successful response quickly
Verify and persist the event, return a
2xx response, and perform slow
work asynchronously.3
Handle retries and duplicates
Webhook delivery is an at-least-once process. Use the event ID as an
idempotency key before applying side effects.
Build your endpoint now
You can prepare an endpoint around a small dispatcher:Verify signatures
Authenticate requests with the raw body and your endpoint signing secret.
When polling is still useful
Webhooks remove the need for routine polling, but direct resource retrieval is still useful for reconciliation or when your application needs the latest full resource state:GET /emails/{message_id}for emailGET /sms/{message_id}for SMSPOST /sms/{message_id}/sync-statusto request an SMS provider status refresh
Event catalog
Review the supported lifecycle events and suggested application behavior.
Operational controls
Monitor endpoint health, recover failures, and control delivery traffic.