Send Mail
The Send Email API enables you to send emails using your verified sending domain to one or multiple recipients in a single API call. You can control key elements like recipients (to, cc, bcc), subject, and content through the personalizations object, while the settings object allows advanced configurations such as scheduling, tracking, and global bcc. Optional features include tagging emails for performance analysis (tags), setting delivery priority via priorityflag, and compressing the payload with gzip to optimize data usage. Personalization lets you tailor shared content uniquely per recipient group, enhancing engagement from a single API request.
To view sample request payloads for these use cases, open the Examples panel on the right.
email-send-example: Full send request with attachments, CC/BCC, tags, and tracking options.
email-example-unsubscribe: Adds List-Unsubscribe headers for one-click unsubscribe support.
multiple_email_id_in_to: Sends to multiple recipients using separate personalization blocks.
dynamic-attribute-example: Uses dynamic attributes to replace placeholders with recipient-specific values.
Headers
(Optional) Set to 1 to enable encryption for the API request. When enabled, both the payload and its key components must follow AES encryption standards.
(Optional) Specifies the version of the encryption method being used. Required only if encryption is enabled.
(Optional) AES encryption key (Base64-encoded) used to encrypt the request payload. This key must be shared securely with Netcore.
(Optional) AES initialization vector (IV) in Base64 format. Used for decrypting the payload when encryption is enabled.
(Optional) Set to gzip if the request body is compressed using GZIP. This helps reduce payload size and optimize bandwidth usage.
Request body
Response
Email accepted for delivery