Observe
Follow delivery events
Connect message activity to the rest of your application.
Prepare an endpoint
Create a server endpoint to receive events. Keep it reachable over HTTPS. Confirm your provider’s supported event names, payload fields, and verification method before accepting events in production.
Verify incoming requests
Use the service’s documented signature-verification procedure. Do not assume a request came from your email provider simply because it arrived at your endpoint.
Connect the event to the message
Store the message ID from the initial send and use it to associate later events. Keep processing idempotent so repeated delivery of the same event does not duplicate actions.
Treat each state deliberately
A delivery event indicates that the receiving server accepted the message. A bounce means the message could not be delivered. Process each supported event according to your product’s needs and your provider’s documented semantics.