Suppressions
Suppressions
Suppressions prevent Lettermint from sending to recipients that should not receive more email. They protect deliverability, honor recipient choices, and help enforce compliance decisions.
Reasons
| Reason | API value | Created by |
|---|---|---|
| Hard bounce | hard_bounce | Lettermint after permanent delivery failure |
| Spam complaint | spam_complaint | Lettermint after a recipient reports spam |
| Unsubscribe | unsubscribe | Hosted unsubscribe and unsubscribe workflows |
| Manual | manual | Dashboard or Team API |
The suppression reason is unsubscribe. The webhook event for a recipient unsubscribe is message.unsubscribed.
Scopes
| Scope | Applies to | Required ID |
|---|---|---|
| Team | All projects and routes in the team | None |
| Project | All routes in one project | project_id |
| Route | One route | route_id |
Higher-level suppressions take precedence. A team-level suppression blocks sends across all projects and routes.
Suppressions table with reason, scope, route, project, and created date.
Add suppressions
You can add one address or up to 1000 addresses in one Team API request.
Add suppression dialog with email, reason, and scope.
Remove suppressions
Manual, hard bounce, and unsubscribe suppressions can be removed when appropriate. Spam complaint suppressions cannot be removed through normal self-service; contact support if you believe one needs review.
Next steps
- Email activity - Inspect suppressed message events
- Routes - Understand route-level lists
- Team API reference - Review suppression endpoints