Source

Sending API, SMTP & developer experience — found from sitemap — Brevo Transactional Email

Checked for Brevo Transactional Email on 1 Nov 2026

Technical details

type: page
http status: 200
content hash: sha256:7341ecdfeba5c707d5eb70eae0d692d08c30ae53bf00d8cb5c31867218fb5cbc
permission: robots_ok
screenshot: Screenshot on file (internal exhibit, not published)

Cited by

Smtp relay purpose Report an error

“Use the SMTP relay to send transactional emails from your email client or application. Send order confirmations, password resets, account creation notifications, and other automated messages.”
Smtp auth key type Report an error

“Use an SMTP key, not an API key, for SMTP relay connections.”
Smtp unencrypted ports Report an error

“Non-encrypted: Use ports 587 or 2525”
Smtp encrypted port Report an error

“Encrypted: Use port 465 with SSL or TLS encryption”
Smtp parameters Report an error

“The following parameters are available for SMTP relay messages:”
Smtp template support Report an error

“templateId Int64 Template ID to use for the email.”
Smtp custom headers Report an error

“Only non-standard headers are supported.”
Smtp scheduling Report an error

“scheduledAt date-time UTC date-time for scheduled delivery (YYYY-MM-DDTHH:mm:ss.SSSZ). Include timezone. Expected delay of up to 5 minutes. Currently in public beta.”
Smtp batch sending unsupported Report an error

“The SMTP relay does not support batch sending. Use the batch sending API endpoints for batch operations. The SMTP relay is designed for transactional emails.”
Sender name max length Report an error

“name String Sender display name. Maximum 70 characters.”
Attachment local files unsupported Report an error

“Provide absolute URL (no local files) or base64-encoded content with attachment name.”