Send Transactional Email via SendGrid Compatibility Layer
Sends transactional email through Routee's SendGrid compatibility layer.
Query
Comma-separated response fields to include.
Body
You may add up to ten (10) custom headers in format {"customHeader1Name" : "customHeader1Value", "customHeader2Name" : "customHeader2Value" ...}
Optional parameter (object) mail_settings contains a child object : footer
The object mail_settings.footer contains two properties reflecting the additional text to be included at the end of HTML or Text message bodies.
The html content of footer (partial HTML). If mail_settings.footer is present, this property must contain a valid partial HTML string.
If you wish to set a custom footer to be added to plain/text message part of your email, then indicate the string you wish to be appended at the end of your message.
Personalizations array contains arrays of emailAddresses representing contacts to be included in the "to","cc" and "bcc" headers of your message
The array that indicates the recipients of an actual message.
This property holds the actual email address of a recipient. At least one recipient must be indicated in the personalizations.to array to be able to submit a message.
Optional string indicating the friendly name to be displayed in the messages "to" header (i.e. "John Doe").
Optional array of objects indicating recipients to be added to carbon copy of a message. If present, it must contain at least 1 recipient.
If optional personalizations.cc array is present, it must contain at least one recipient with valid email address. This property holds the email address to be included in the "cc" message header.
Optional string containing the friendly name of the email address to be added to the carbon copy recipients.
Optional array of blind carbon copy recipients.
If the optional array of BCC recipients is present, then it must contain at least one valid email address.
A friendly name to be used when sending a bcc to the above mentioned email address.
Optional array of objects containing the file attachments.
A valid file name to be prompted when this attachment is attempted to be saved
A valid MIME type for the content. Please note that not all types of content are allowed by all providers. Most will disallow any executable file such as .cmd, .vbs etc.
Base64 encoded content of the attachment file.
Optional object indicating which will be the address to use in case when the recipient replies to the message. If not set, then the contents of **from** objects are used.
Optional property indicating the friendly name of the return address to be displayed when the recipient replies to a message.
If the optional reply_to object is present then this property is required. It indicates the actual email address to be used as recipient when a message recipient replies to a message.
The subject of the email, up to 144 UTF8 characters. It is not strictly required but it is strongly recommended to fill this property with something meaningful.
This is a required object representing the sender of this message.
This property represents the email address to appear in the "from" message header.
Optional friendly name of the sender.
Array containing the content of the message divided based on content type (html, text).
This property contains the exact MIME type of the content following. Acceptable values are "text/html" and "text/plain". Other MIME types will be rejected.
This property encapsulates the actual data to be included in the section, i.e. the actual HTML message body or the Text message body.