Subscriber endpoint that receives Brevo transactional email webhook
events. Brevo POSTs one event per HTTP request. The `event` field in
the JSON body identifies the event class.
A transactional email was accepted by Brevo for sending.
Content-Type: application/json
TxDelivered
A transactional email was accepted by the recipient mail server.
Content-Type: application/json
TxSoftBounce
A transactional email was temporarily rejected by the recipient mail server.
Content-Type: application/json
TxHardBounce
A transactional email was permanently rejected by the recipient mail server.
Content-Type: application/json
TxBlocked
A transactional email was blocked before sending (for example, the recipient is on the account-level block list).
Content-Type: application/json
TxInvalidEmail
The recipient address was rejected as syntactically invalid.
Content-Type: application/json
TxDeferred
The recipient mail server temporarily deferred the message; Brevo will retry.
Content-Type: application/json
TxError
A processing error occurred while handling the transactional message.
Content-Type: application/json
TxSpam
The recipient flagged the transactional message as spam.
Content-Type: application/json
TxOpened
The recipient opened the transactional message (may fire multiple times).
Content-Type: application/json
TxUniqueOpened
The recipient opened the transactional message for the first time.
Content-Type: application/json
TxProxyOpen
The transactional message was opened via a mail-privacy proxy (for example Apple Mail Privacy Protection).
Content-Type: application/json
TxUniqueProxyOpen
The first proxy-based open recorded for the transactional message.
Content-Type: application/json
TxClick
The recipient clicked a tracked link in the transactional message.
Content-Type: application/json
TxUnsubscribed
The recipient unsubscribed from the transactional message.
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.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.