How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Sendinblue

A service that provides solutions relating to marketing and/or transactional email and/or SMS

This event API exposes 2 operations across 2 channels, and defines 42 schemas. It is described by AsyncAPI 2.6.0, at version 1.0.0.

The API connects through a single server, {webhookUrl} (https).

2 operations 2 channels 42 schemas

Metadata

The identity and technical contract details declared by the specification.

Specification
AsyncAPI 2.6.0
API Version
1.0.0
Base URL
https://developers.sendinblue.com/docs
Resource Areas
1

Channels & Operations 2

Across 2 channels, the API surfaces 2 operations. Each is listed below with its action, channel, parameters, and response codes.

Channels 2
PUB
/brevo/transactional/webhook
Receive a Brevo transactional email webhook event
receiveTransactionalWebhook body
PUB
/brevo/marketing/webhook
Receive a Brevo marketing webhook event
receiveMarketingWebhook body

Messages & Schemas 42

The contract defines 42 schemas that model the data carried by its messages. The most detailed are TxEmailBase (16 properties), MkCampaignBase (12 properties), MkListAdditionPayload (7 properties), MkContactDeletedPayload (7 properties). Each schema is shown below with its type and property counts.

TxRequest
message
A transactional email was accepted by Brevo for sending.
TxDelivered
message
A transactional email was accepted by the recipient mail server.
TxSoftBounce
message
A transactional email was temporarily rejected by the recipient mail server.
TxHardBounce
message
A transactional email was permanently rejected by the recipient mail server.
TxBlocked
message
A transactional email was blocked before sending (for example, the recipient is on the account-level block list).
TxInvalidEmail
message
The recipient address was rejected as syntactically invalid.
TxDeferred
message
The recipient mail server temporarily deferred the message; Brevo will retry.
TxError
message
A processing error occurred while handling the transactional message.
TxSpam
message
The recipient flagged the transactional message as spam.
TxOpened
message
The recipient opened the transactional message (may fire multiple times).
TxUniqueOpened
message
The recipient opened the transactional message for the first time.
TxProxyOpen
message
The transactional message was opened via a mail-privacy proxy (for example Apple Mail Privacy Protection).
TxUniqueProxyOpen
message
The first proxy-based open recorded for the transactional message.
TxClick
message
The recipient clicked a tracked link in the transactional message.
TxUnsubscribed
message
The recipient unsubscribed from the transactional message.
MkOpened
message
A recipient opened a marketing campaign email.
MkClick
message
A recipient clicked a tracked link in a marketing campaign email.
MkListAddition
message
A contact was added to one or more lists.
MkContactUpdated
message
One or more attributes of a contact were updated.
MkContactDeleted
message
A contact was deleted from the account.
TxEmailBase
object
Fields common to all transactional email webhook events. The event field is the discriminator. tsepoch is documented as UTC milliseconds for most events; ts an…
16 properties 4 required
TxRequestPayload
object
TxDeliveredPayload
object
TxSoftBouncePayload
object
TxHardBouncePayload
object
TxBlockedPayload
object
TxInvalidEmailPayload
object
TxDeferredPayload
object
TxErrorPayload
object
TxSpamPayload
object
TxOpenedPayload
object
TxUniqueOpenedPayload
object
TxProxyOpenPayload
object
TxUniqueProxyOpenPayload
object
TxClickPayload
object
TxUnsubscribedPayload
object
MkCampaignBase
object
Fields common to marketing campaign events (opened, click). Brevo documents tssent and tsevent in seconds, and ts as the webhook delivery timestamp in seconds.
12 properties 3 required
MkOpenedPayload
object
MkClickPayload
object
MkListAdditionPayload
object
Contact was added to one or more Brevo contact lists.
7 properties 2 required
MkContactUpdatedPayload
object
Attributes of a contact were updated.
7 properties 2 required
MkContactDeletedPayload
object
A contact was deleted.
7 properties 2 required

Specification

The full machine-readable AsyncAPI contract behind this narrative.

Source

sendinblue-webhooks-asyncapi.yml Raw ↑
Where this information came from

This is an independent, third-party profile of Sendinblue, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.