Send MIME email

The ID that uniquely identifies the message sent to a recipient.

The ID that uniquely identifies the sent bulk. This filter will enable you to query delivery reports for all the messages using just one request. You will receive a bulkId in the response after sending an email request. If you don't set your own bulkId, unique ID will be generated by our system and returned in the API response. (Optional Field)")

The email address specified in this field takes precedence over the From header in the MIME message. If you leave this field empty, the From address in the MIME message will be used instead. If you provide both values and they are different, their domains must match at the organizational level; otherwise, the request will be rejected.

This field accepts a complete email message serialized in the MIME format, conforming to RFC 5322 and MIME-related standards (RFCs 2045–2047, RFC 2183). The MIME message must be correctly constructed per the following requirements as if it were being sent via traditional SMTP. The entire MIME message (including headers and body) must be base64-encoded before being sent. <br/><br/>

When using this field, these are the requirements: <br/> - The message must consist of a set of header fields, followed by a blank line (CRLF), and then the message body <br/> - All required and optional fields must be properly formatted with header-name, colon, and header-value <br/> - If any MIME part contains non-7-bit-ASCII data (e.g., UTF-8 text, binaries), that part must be encoded <br/> - If your message uses multipart content (attachments, alternative bodies, etc.), each MIME part must contain Content-Type header. For encoded parts, include Content-Transfer-Encoding. For attachments, include a valid Content-Disposition. <br/><br/> We also support specifying additional headers in your MIME message, such as List-Unsubscribe, List-Unsubscribe-Post, In-Reply-To, References and Message-ID.

The real-time Intermediate delivery report that will be sent on your callback server.

The URL on your callback server on which the Delivery report will be sent.

Preferred Delivery report content type. Can be application/json or application/xml.

Additional client data that will be sent on the notifyUrl.

The URL on your callback server on which the open and click notifications will be sent. See Tracking Notifications for details.

Adds a priority rating to this email message. Allowed values are HIGH, STANDARD and LOW. Messages with a higher priority value sent by your account are prioritized over messages with a lower priority value sent by your account. If no priority value is provided, messages will be treated with STANDARD priority by default.

Required for application use in a send request for outbound traffic. Returned in notification events.

Required for entity use in a send request for outbound traffic. Returned in notification events.

The ID that uniquely identifies a list of message responses.