AsyncAPI channel · Brevo · Brevo Webhook Events

/transactional-email-events

Transactional email event notifications including delivery status, opens, clicks, bounces, spam reports, and unsubscribes.

Open source AsyncAPI → All Brevo channels Brevo provider profile
Provider: Brevo AsyncAPI: v2.6.0 Spec: Brevo Webhook Events Operations: 1 Messages: 10

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 Agent Skill and MCP server surfaces of the same providers.

Work with this as data

Every channel here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for event channels

4 MCP tools reach this
  • find_channelsBrowse and filter every channel in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This channel 
curl "https://apis.io/api/v1/channels/transactional-email-events"
All event channels 
curl "https://apis.io/api/v1/channels?limit=25"

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.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.