SendTransactionalBulkEmail function sends bulk transactional email messages to recipients. A maximum of 50 different content items can be sent per request, with up to 100 recipients for each content.
There are two types of content options for sending transactional emails:
Payload-1 (use content)
In this method, the client sends the content and recipient list. The system returns groupIds for each content batch and processes the emails asynchronously.
These groupIds are used to retrieve reports per content group, while the response provides detailed recipient information, including email addresses.
For multi-language sending, the multiLangContent property should be used.
Payload-2 (use template)
This method sends transactional email messages using an existing template in the system. The only difference from Method-1 is that the templateId field is used to select a template. A templateId can be created either through the API (CreateEmailContent) or via the GUI.
For multi-language sending, a template created as multi-language must be selected.
You can send with a custom sender name different from the one defined in the account. You can also modify the field before the @ sign of the sender address defined in the account. Sample requests are available for review.
You can analyze everything from reporting to tracking, or add custom headers such as list-unsubscribe by including xHeaders in your request. Sample requests are also provided.
Attachments can be included using the attachments object. All attached files must be base64 encoded.
Note: You cannot use multiLangContent and content properties at the same time.
The recipient’s language can be used as a parameter when sending multi-language content. If the recipient’s language is specified, it is used as the user language; otherwise, the contact’s default language is applied.
replyTo
If the replyTo property is empty, the fromId is used as replyTo. Content-specific replyTo values can be defined for each content when sending multi-language messages, or a base replyTo property defined under the root property can be applied to all contents inside multi-language messages.
If you are going to send these parameters via API, the {%=$Current.parameter%} name should be used. This parameter must also be added to the content via the panel.
<h2>{%=$Current.order_id%}</h2>