Configure a Brevo transactional sender and credential
Authenticate a Brevo sender/domain and separate API, SMTP, and marketing permissions before connecting an application.
Reviewed
Brevo combines several messaging and marketing products. An application sending a receipt needs the transactional email path, not automatic contact-list enrollment or a campaign workflow.
Prepare transactional sending
- Complete the account’s transactional sending activation requirements.
- Add the approved sender/domain and publish the exact authentication records provided by Brevo.
- Choose the documented API authentication method for your integration, or generate the separate SMTP credential if using relay.
- Store that credential server-side and separate production from development connections.
The developer overview documents API keys, OAuth options, official SDKs, transactional sending, and inbound parsing. Do not copy an older client example without checking its package and authentication model against current docs.
Verify the intended service
Use one controlled recipient and confirm the message appears in transactional activity. Sender verification does not mean you have created a marketing audience or receiving route.
An authorization error can mean the wrong credential type, restricted permission, or account capability. Diagnose it before requesting a broader key. Adding recipients to a marketing list merely to send a password reset changes consent/billing behavior and is not a prerequisite to invent.
MailKite can provide a separate signed receiving or sending path. Its credentials do not authenticate to Brevo, and its suppression state does not automatically synchronize with Brevo’s contacts or blocklists.