AsyncAPI channel · brevo
· Brevo Webhook Events
/marketing-email-events
Marketing campaign event notifications including delivery, opens, clicks, bounces, spam reports, unsubscribes, and contact list changes.
Channel address
/marketing-email-events
Operations
publish
receiveMarketingEmailEvent
Receive marketing email event
Messages
marketingDelivered
Fired when a marketing campaign email is successfully delivered.
Content-Type:
marketingOpened
Fired when a recipient opens a marketing campaign email.
Content-Type:
marketingClicked
Fired when a recipient clicks a link in a marketing campaign email.
Content-Type:
marketingHardBounce
Fired when a marketing campaign email permanently bounces.
Content-Type:
marketingSoftBounce
Fired when a marketing campaign email temporarily bounces.
Content-Type:
marketingSpam
Fired when a recipient marks a marketing campaign email as spam.
Content-Type:
marketingUnsubscribed
Fired when a recipient unsubscribes from marketing emails.
Content-Type:
marketingListAddition
Fired when a contact is added to a marketing list.
Content-Type:
contactDeleted
Fired when a contact is deleted from the account.
Content-Type:
contactUpdated
Fired when a contact's attributes are updated.
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.