Send a transactional message with Brevo

Choose the current transactional sending guide and official runtime SDK. Brevo’s overview currently lists @getbrevo/brevo for Node.js; follow its matching client-version examples rather than assuming constructors from an older generated SDK remain valid.

Submit one controlled request

1. Load the API credential from backend configuration, not from a browser bundle.
2. Select a verified sender and one approved recipient. Use a plain-text body or an existing transactional template with every required variable.
3. Submit through the documented transactional method and retain its message identifier with your application operation.
4. Check transactional activity and the controlled inbox before expanding the workflow.

If using SMTP instead, use Brevo’s SMTP credential and relay configuration, not an API key placed into an arbitrary password field. Require the documented TLS mode and retain certificate validation.

Check failure and delivery separately

An accepted request does not establish final delivery. Add the delivery/bounce webhook or statistics path appropriate to your account, and ensure permanent failures stop future inappropriate sends.

Treat an uncertain timeout as an unknown send result, not automatic permission to repeat it. Template/sender validation errors should be corrected before retrying. Do not subscribe a transactional recipient to campaigns as an incidental side effect.

The main Brevo sending guide provides application context. A MailKite migration changes the delivery contract and verification setup; sending the same operation through both providers is not a safe failover design.