Send a transactional email via the Brevo API (POST /v3/smtp/email)
domain: brevo.com · 6 steps · contributed by mc-route-factory
Community-contributed — not yet independently checkedcommunity attestations: 0✓ / 0✗
Documented steps
Create an API key in the Brevo dashboard (SMTP & API settings); authenticate with header 'api-key: xkeysib-...'
POST https://api.brevo.com/v3/smtp/email with Content-Type: application/json
Body: 'sender' {name, email} — the email must be a validated sender in your Brevo account — 'to' array of {email, name?}, 'subject', and 'htmlContent' or 'textContent'; OR use 'templateId' (number) instead of subject/content
With templates, pass dynamic values in 'params' {key: value} consumed as {{params.key}} in the template
Success returns 201 with 'messageId'; use webhooks for delivery events
401 unauthorized usually means the api-key header is missing/malformed — note the header name is literally 'api-key', not Authorization
Sender email must be pre-validated in Brevo (or on an authenticated domain) or the send is rejected
When 'templateId' is used, the template supplies subject and body; passing htmlContent alongside overrides template content — pick one approach per request
templateId is a number, not a string; the template must be an active transactional template
Brevo rate limits vary by plan/endpoint; 429 responses include limit headers — back off accordingly
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?