Single subscriber endpoint that receives every Postmark webhook event for
the configured server/stream. The `RecordType` field on the JSON body
identifies the event class. Postmark sends one event per HTTP POST.
Postmark successfully delivered a message to the recipient's mail server.
Content-Type: application/json
BounceEvent
A bounce of any non-transient type (HardBounce, SoftBounce, SpamNotification, etc.).
Content-Type: application/json
TransientEvent
A transient delivery failure (Bounce TypeCode 2). Sent on the same
Bounce webhook channel; distinguished by `Type` = `Transient`.
Content-Type: application/json
OpenEvent
A recipient opened a tracked outbound message.
Content-Type: application/json
ClickEvent
A recipient clicked a tracked link in an outbound message.
Content-Type: application/json
SpamComplaintEvent
A recipient or receiving mail provider reported a message as spam.
Content-Type: application/json
SubscriptionChangeEvent
A suppression was added or removed for a recipient address on a stream.
Content-Type: application/json
ManualSuppressionEvent
A manually-applied suppression. Postmark delivers manual suppressions
through the SubscriptionChange webhook with
`SuppressionReason` = `ManualSuppression` and a null `MessageID`.
Content-Type: application/json
InboundEvent
Postmark received and parsed an inbound email and is forwarding it as JSON.
Content-Type: application/json
About AsyncAPI
The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.