No email is sent during a check. The free plan includes 100 checks a month.
Point a Postmark webhook at your workspace. Bounces, spam complaints, and unsubscribes update your suppression list.
1.1 Postmark
1.2 Delivery endpoint
1.3 Recorded as
§ 1
Why it matters
When an event is only recorded in the email platform, the address comes back with the next import.
Close the loop between Postmark and your list checks.
§ 2
How it works
Postmark does not sign webhooks. The private URL carries a secret token, and you can limit the endpoint to a list of IP addresses through the API.
Sent by Postmark
{ "RecordType": "Bounce", "Type": "HardBounce", "Email": "[email protected]", "BouncedAt": "2026-10-16T09:12:44Z", "MessageID": "883953f4-6105-42a2..."}Verifier · POST /v1/inbound/providers/postmark/{endpoint}/{token}
{ "provider": "postmark", "accepted": 1, "duplicates": 0, "rejected": 0}GET /v1/suppressions/[email protected]
{ "suppressed": true, "reason": "bounce", "source": "postmark"}§ 3
What you get
Table 3 · Event mapping
| Event from the platform | Recorded as |
|---|---|
| Delivery | delivered |
| Bounce | bounced |
| SpamComplaint | complained |
| SubscriptionChange (suppressed) | unsubscribed |
| Open | opened |
| Click | clicked |
§ 4
In practice
Case 4.1
Stop repeat problems
A suppressed address goes to the drop file when you clean your next list.
Case 4.2
More than one sending tool
A Postmark bounce also stops the address in lists from your CRM and other tools.
Questions
The event mapping on this page shows what is recorded. Bounces, spam complaints, and unsubscribes go on the suppression list.
A SubscriptionChange event with SuppressSending set to true is recorded as an unsubscribe. A change that turns sending back on is not.
Continue reading