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.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
personalizations
array of objects
required
personalizations*
from
object
required
reply_to
array of objects
reply_to
string
required

Subject line of the email

integer

Assigns delivery priority (1=OTP/Transactional, 2=Triggered, 3=Promotional).
Defaults to account/subaccount setting if omitted.

content
array of objects
required

Email content blocks. Supports dynamic placeholders like [%NAME%] with corresponding attributes.

content*
integer

ID of the email template (Settings → Templates).
If used, ensure HTML content is provided in content.

tags
array of strings

Labels to segment and track emails (e.g., ["signup-confirmation", "holiday-offers"]).

tags
integer

Scheduled send time in UNIX epoch format.

attachments
array of objects
attachments
bcc
array of objects
bcc
tracking_settings
object
mail_settings
object
number
Headers
integer
enum

(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.

Allowed:
integer

(Optional) Specifies the version of the encryption method being used. Required only if encryption is enabled.

string

(Optional) AES encryption key (Base64-encoded) used to encrypt the request payload. This key must be shared securely with Netcore.

string

(Optional) AES initialization vector (IV) in Base64 format. Used for decrypting the payload when encryption is enabled.

string
enum

(Optional) Set to gzip if the request body is compressed using GZIP. This helps reduce payload size and optimize bandwidth usage.

Allowed:
Responses

Language
Credentials
Bearer
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json