AsyncAPI channel · brevo · Brevo Webhook Events

/transactional-sms-events

Transactional SMS event notifications including delivery status, bounces, and subscriber changes.

Provider: brevo AsyncAPI: v2.6.0 Spec: Brevo Webhook Events Operations: 1 Messages: 5

Channel address

/transactional-sms-events

Operations

publish
receiveTransactionalSmsEvent
Receive transactional SMS event

Messages

smsSent
Fired when a transactional SMS is sent to the carrier.
Content-Type:
smsDelivered
Fired when a transactional SMS is delivered to the recipient.
Content-Type:
smsSoftBounce
Fired when a transactional SMS temporarily bounces.
Content-Type:
smsHardBounce
Fired when a transactional SMS permanently bounces.
Content-Type:
smsUnsubscribe
Fired when a recipient unsubscribes from SMS messages.
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.