SendTransactionalEmail function sends transactional email messages to recipients.

There are two type of content to send transactional emails.

Payload-1 (use content)
In this method, the client sends the content and recipients.The system returns uuid-type transactionalIds per recipient and uuid-type groupId for all.

These transactional ids are used to get the report per recipient whereas the groupId response field is used to get the report of all recipient at once.

For multi language send, the multiLangContent property should be used.

Payload-2 (use template)
This method is used to send transactional email messages using an existing template in the system. The only difference from Method-1 is templateId field is used to select the template from the system. This templateId can be created both using API (CreateEmailContent) or through GUI.

For multi language send, a template id created as multi language should be selected.

You can send with a sender name other than the sender name defined in the account.You can send by changing the field before the @ sign of the sender address defined in the account.You can examine sample requests.

You can analyze your own report by adding xHeaders to your post.You can examine sample requests.

Inserting attachments are possible with attachments object. Attached files must be base64 encoded.

** You cannot use multiLangContent and content properties at the same time.

Recipients language can be used as a parameter for sending with multi language content if recipient language is given, this property used as a user language otherwise contact language is used.

reply to
If the reply to property is empty, fromId used as a replyTo. Content specific replyTo information can be used for each content in sendings with multilanguage or base replyTo property which is defined under which is defined under root property, can be used for all contents inside of the multilanguage contents.

Idempotency Support: This endpoint supports idempotency via the optional traceId parameter. For more information, see Rest API Idempotency.