Your webhook receiver should assume that delivery events are operational data. Store them before running business logic,
process them asynchronously, and make handlers idempotent.
Success and failure
MailChannels treats a webhook request as successful when your endpoint returns a 2xx HTTP status. Other responses are
recorded by status category, including 1xx, 3xx, 4xx, 5xx, and no_response.
Use the webhook batch API to inspect recent webhook batches. If no time range is supplied, the API returns batches from
the last 3 days. If you provide created_after and created_before, the range must not exceed 31 days.
Replay failed batches
After you fix a receiver problem, you can resend a specific batch.
A successful resend API response means MailChannels made the resend attempt and captured the endpoint response. It does
not mean your endpoint returned a 2xx status. Check the response body and your receiver logs.
Test delivery
Use webhook validation before production launch and after endpoint changes. Validation sends a test event with your customer
handle, a test sender, a test event type, and a generated smtp_id.