How does Notify handle delivery logs and webhook events?

Notify typically handles delivery logs and webhook events as two separate but related mechanisms:

Delivery logs

These are the internal records of what happened to each notification as it was processed and delivered. They usually include things like:

• Notification ID
• Recipient / destination
• Timestamp
• Delivery status (queued, sent, delivered, failed, bounced, etc.)
• Provider response or error details
• Retry attempts

Delivery logs are mainly used for:

• Debugging delivery issues
• Auditing notification history
• Monitoring success/failure rates
• Supporting customer support investigations

Webhook events

Webhooks are outbound HTTP callbacks Notify sends to your system when a notification changes state or an event occurs. Common webhook events include:

• Notification accepted
• Sent
• Delivered
• Failed
• Opened / clicked, if supported
• Bounced / rejected

With webhooks, your app can react in real time by:

• Updating your database
• Triggering downstream workflows
• Alerting operators
• Syncing notification status with your UI

How they work together

• Delivery logs are the source of truth inside Notify for tracking notification lifecycle.
• Webhooks are the mechanism for pushing those lifecycle updates to your application.
• If a webhook delivery fails, the event may still be recorded in delivery logs, and Notify may retry the webhook depending on its configuration.

Best practices

• Make webhook handlers idempotent so duplicate events don’t cause issues.
• Verify webhook signatures if Notify supports them.
• Use delivery logs for troubleshooting, not as your primary real-time integration mechanism.
• Expect occasional delays or retries in webhook delivery.

If you want, I can also show a sample event flow or explain how to design a webhook consumer for Notify.