AsyncAPI channel · Sendinblue
· Brevo (Sendinblue) Webhooks
/brevo/transactional/webhook
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.
Channel address
/brevo/transactional/webhook
Operations
publish
receiveTransactionalWebhook
Receive a Brevo transactional email webhook event
Messages
TxRequest
A transactional email was accepted by Brevo for sending.
Content-Type:
application/jsonTxDelivered
A transactional email was accepted by the recipient mail server.
Content-Type:
application/jsonTxSoftBounce
A transactional email was temporarily rejected by the recipient mail server.
Content-Type:
application/jsonTxHardBounce
A transactional email was permanently rejected by the recipient mail server.
Content-Type:
application/jsonTxBlocked
A transactional email was blocked before sending (for example, the recipient is on the account-level block list).
Content-Type:
application/jsonTxInvalidEmail
The recipient address was rejected as syntactically invalid.
Content-Type:
application/jsonTxDeferred
The recipient mail server temporarily deferred the message; Brevo will retry.
Content-Type:
application/jsonTxError
A processing error occurred while handling the transactional message.
Content-Type:
application/jsonTxSpam
The recipient flagged the transactional message as spam.
Content-Type:
application/jsonTxOpened
The recipient opened the transactional message (may fire multiple times).
Content-Type:
application/jsonTxUniqueOpened
The recipient opened the transactional message for the first time.
Content-Type:
application/jsonTxProxyOpen
The transactional message was opened via a mail-privacy proxy (for example Apple Mail Privacy Protection).
Content-Type:
application/jsonTxUniqueProxyOpen
The first proxy-based open recorded for the transactional message.
Content-Type:
application/jsonTxClick
The recipient clicked a tracked link in the transactional message.
Content-Type:
application/jsonTxUnsubscribed
The recipient unsubscribed from the transactional message.
Content-Type:
application/jsonAbout 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.
Browse every event-driven channel on the APIs.io network or compare with the broader Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.