Integration guide
Build with Brevo for transactional product email
Build with Brevo for transactional product email means treating the provider as an authorised external system—not a decorative logo. Xroga reports what the connected account allowed and what evidence the operation returned.
01
What belongs in the project
Keep code, configuration names, and provider-facing adapters reviewable in the repository. Keep secret values in the provider or deployment environment.
02
What must be verified
Confirm permissions, environment selection, failure behaviour, and the user-visible result. A successful API response and a working product are separate checks.
03
What Xroga will not assume
Xroga does not invent credentials, bypass provider policy, or report a deployment or integration as live without evidence from the authorised account.
04
Transactional email boundary
Templates and provider adapters can live in the repository; API credentials and sender configuration stay in the protected server environment. The application should retain provider message identifiers and distinguish accepted, delivered, bounced, and failed states.
05
Verification
- Verify the sender and intended environment.
- Test consent and unsubscribe rules for non-transactional mail.
- Make retries idempotent.
- Do not expose recipient data or credentials in logs.
Primary sources
Product capabilities change. These official pages were used for the factual statements above; verify them again before making a purchasing decision.