AsyncAPI channel · brevo
· Brevo Webhook Events
/transactional-email-events
Transactional email event notifications including delivery status, opens, clicks, bounces, spam reports, and unsubscribes.
Channel address
/transactional-email-events
Operations
publish
receiveTransactionalEmailEvent
Receive transactional email event
Messages
emailDelivered
Fired when a transactional email is successfully delivered to the recipient's mail server.
Content-Type:
emailOpened
Fired when a recipient opens a transactional email.
Content-Type:
emailClicked
Fired when a recipient clicks a link in a transactional email.
Content-Type:
emailHardBounce
Fired when a transactional email permanently bounces due to an invalid or non-existent email address.
Content-Type:
emailSoftBounce
Fired when a transactional email temporarily bounces due to a full mailbox or temporary server issue.
Content-Type:
emailSpam
Fired when a recipient marks a transactional email as spam.
Content-Type:
emailBlocked
Fired when a transactional email is blocked from sending.
Content-Type:
emailInvalid
Fired when a transactional email is sent to an invalid email address.
Content-Type:
emailDeferred
Fired when delivery of a transactional email is temporarily deferred by the receiving mail server.
Content-Type:
emailUnsubscribed
Fired when a recipient unsubscribes from transactional emails.
Content-Type:
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.
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.