SingleSendMail

The sender address configured in the Direct Mail console.

The address type. Valid values:

0: A random account.

1: A sender address.

A tag for categorizing email batches, which you can create in the Direct Mail console. Tags allow you to query the sending status of each batch and are required if you enable email tracking. The tag must be 1 to 128 characters long and can contain letters, digits, underscores (_), and hyphens (-).

Specifies whether to use the default reply-to address configured in the console. This address must be verified. Valid values: true, false.

The destination email address(es). To specify multiple addresses, separate them with commas (up to 100).

The subject of the email, with a maximum length of 256 characters.

The HTML body of the email.

Note: You must specify either HtmlBody or TextBody.

• The size of the body is limited to approximately 80 KB when passed as a URL parameter.

• For recent SDKs (Java 1.4.0+, Python 3 1.4.0+, and PHP 1.4.0+), the request body is limited to approximately 8 MB.

The text body of the email.

Note: You must specify either HtmlBody or TextBody.

• The size of the body is limited to approximately 80 KB when passed as a URL parameter.

• For recent SDKs (Java 1.4.0+, Python 3 1.4.0+, and PHP 1.4.0+), the request body is limited to approximately 8 MB.

The sender name. It must be 15 characters or shorter.

For example, if you set the sender name to "Xiaohong" and the sender address is test***@example.net, the recipient sees the sender as "Xiaohong" <test***@example.net>.

The reply-to address.

The name displayed for the reply-to address.

Specifies whether to enable click tracking. Valid values: "1" enables click tracking, and "0" disables it (default).

disabled: Does not generate an unsubscribe link.

default: Uses the default policy. For batch sender addresses, an unsubscribe link is generated when sending to specific domains containing keywords such as "gmail", "yahoo",

"google", "aol.com", "hotmail",

"outlook", and "ymail.com". For more information, see Unsubscribe link generation and filtering mechanism.

The display language is automatically determined based on the recipient's browser settings.

The filtering level. For more information, see Unsubscribe link generation and filtering mechanism.

disabled: No filtering.

default: Uses the default policy. For batch addresses, filtering is applied at the sender address level.

mailfrom: Filters at the sender address level.

mailfrom_domain: Filters at the sender domain level.

edm_id: Filters at the account level.

Custom email header settings.

Both standard and non-standard fields must comply with standard header syntax. You can specify up to 10 headers for an API call. Excess headers are ignored. This limit does not apply to SMTP.

1. Standard fields

Message-ID, List-Unsubscribe, List-Unsubscribe-Post

Standard fields overwrite existing values in the email header.

2. Non-standard fields

Case-insensitive.

a. Fields starting with X-User-: These are not pushed to EventBridge or Message Service (MNS). This prefix is required only for API calls, not for SMTP.

b. Fields starting with X-User-Notify-: These are pushed to EventBridge and MNS. This is supported for both API and SMTP calls.

When pushed to EventBridge or MNS, the header object will contain these fields.

The ID of the dedicated IP pool. If you have purchased dedicated IPs, you can use this parameter to select which dedicated IP pool to use for sending the email. For more information, see Dedicated IP.

• A comma-separated list of BCC recipients.

• The system sends a copy of the email to each BCC recipient. The BCC information is hidden from all recipients, including those specified in ToAddress and BccAddress.

• To protect privacy, email tracking features (such as open and click tracking) are disabled for emails sent to BCC recipients. However, billing and sending status are still tracked.

• A maximum of two BCC recipients are allowed per request.

Note: The SingleSendMail API operation does not support a CC field. To send carbon copies, use SMTP.

Specifies whether to enable domain-level authentication.

• true

• false

This parameter is used only for domain-level authentication. Ignore it for sender address-level authentication.

1. Create the address domain-auth-created-by-system@example.com in the console. The prefix must be fixed, and the suffix must be your domain.

2.

API scenario

Set AccountName to your domain. Recipients will see the sender as domain-auth-created-by-system@example.com.

SMTP scenario

a. Call the ModifyPWByDomain API operation to set a password for the domain.

b. Authenticate with the domain and the configured password. Pass a custom address, such as user@example.com, as the actual sender in the MAIL FROM command. Recipients will see user@example.com as the sender.