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).
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.
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.