AsyncAPI channel · Sendinblue · Brevo (Sendinblue) Webhooks

`/brevo/marketing/webhook`

Subscriber endpoint that receives Brevo marketing webhook events. Brevo POSTs one event per HTTP request. The `event` field in the JSON body identifies the event class. Marketing webhooks cover both campaign activity (opens, clicks, bounces, unsubscribes) and contact-list lifecycle activity (list additions, contact updates, contact deletes).

Open source AsyncAPI → All Sendinblue channels Sendinblue provider profile

Provider: Sendinblue AsyncAPI: v2.6.0 Spec: Brevo (Sendinblue) Webhooks Operations: 1 Messages: 5

Channel address

/brevo/marketing/webhook

Operations

publish

receiveMarketingWebhook

Receive a Brevo marketing webhook event

Messages

MkOpened

A recipient opened a marketing campaign email.

Content-Type: application/json

MkClick

A recipient clicked a tracked link in a marketing campaign email.

Content-Type: application/json

MkListAddition

A contact was added to one or more lists.

Content-Type: application/json

MkContactUpdated

One or more attributes of a contact were updated.

Content-Type: application/json

MkContactDeleted

A contact was deleted from the account.

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.

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.