Explore features
Keep your systems informed when email status changes.
Send signed email-status updates to your own application. Choose the relevant events and projects, then inspect the callback delivery history in PulsePigeon.
Who it helps
Engineering and operations teams keeping an internal system or customer-support workflow up to date with email events.
Business value
Connect email status to the tools your team already uses. Callback history helps your technical team investigate whether an update reached its receiver and whether a retry or replay needs attention.
How it works
- Configure a secure receiving endpoint and choose its event and project scope.
- Have your integration verify the signed updates before processing them.
- Review callback history, retries and replay controls.
Choosing the right message path
A callback describes an email event. A successful callback means your receiver accepted that update; it does not independently prove email delivery or that a recipient read the message.
Plans and availability
Check the webhook controls available to your workspace and keep the receiver ready to verify signed events. Compare plans.
Next steps
Open Webhooks · Read the API reference · Explore SDK documentation.