Webhooks & Alerts
MailReach can push real-time notifications to your systems when something happens on an account, domain, or spam test. Notifications are delivered as a JSON POST to a webhook URL you provide, or posted directly to a Slack channel.
Configure alerts
You can set up alerts either from the Alerts tab in your MailReach project settings, or programmatically via the API:
| Endpoint | Description |
|---|---|
POST /v1/alerts |
Create an alert |
GET /v1/alerts |
List all alerts for the project |
DELETE /v1/alerts/{id} |
Delete an alert |
When creating an alert, specify the event type you want to subscribe to and the destination (webhook URL or Slack channel ID).
Events
| Event | Trigger |
|---|---|
| Account disconnected | One or more accounts lost their IMAP/SMTP or OAuth connection |
| Domain expiring soon | A connected domain is approaching its expiration date |
| New warming mode proposed | MailReach recommends switching an account to a new warming mode |
| Account back to normal warming | The account returned to its standard warming mode |
| Missing inbound emails | Expected inbound emails are not being received on an account |
| Reputation score decrease | An account's reputation score dropped |
| Reputation score increase | An account's reputation score improved |
| Too many messages sent | Sending volume exceeds safe thresholds on an account |
| SendGrid missing emails | A SendGrid-connected account is not receiving expected emails |
| Outlook missing outgoing emails | An Outlook account is failing to send expected outgoing emails |
| Automated spam test completed | A scheduled or on-demand spam test finished |
Receiving webhook events
When a subscribed event fires, MailReach sends an HTTP POST request to your endpoint with Content-Type: application/json. Your server must respond with a 2xx status code to acknowledge receipt.
Respond fast. Return 200 immediately and process the payload asynchronously. Slow or failing endpoints may be retried or paused.
Best practices
- Acknowledge quickly. Return a
2xxbefore doing any processing, then offload work to a queue or background job. - Handle duplicates. MailReach may deliver the same event more than once under failure conditions. Use the event identifier to deduplicate on your end.
- Validate the source. Restrict your webhook endpoint to
POSTrequests and consider logging unexpected payloads for inspection. - Return the right status. A
2xxtells MailReach the delivery succeeded. Any other status is treated as a failure.
Slack integration
Instead of (or in addition to) a webhook URL, any alert can be routed to a Slack channel. Configure the Slack destination from the Alerts tab in your project settings. No API call needed.
Testing your webhook
Use a service like webhook.site or RequestBin to capture and inspect payloads during development before pointing MailReach at your production endpoint.