Send Email
API Query Parameters
The API accepts either a single dsid (DailyStory unique id) or a comma separated list of email addresses. If email query string parameter has a value, the dsid value will be ignored.
email- The email parameter accepts a single example address, e.g.email=person@example.com, or a comma separate list of email addresses, e.g.email=person1@example.com,person2@example.com
If both the email address and the dsid parameter is sent, the implied intent is that the email address is preferred and the dsid is a fallback.
Any email addresses that are invalid or are attempted to be used for invalid contacts will be ignored.
JSON Body
Optionally include a JSON body with properties used to personalize the email.
These fields are then accessible in the email. The following fields are reserved field and for a templated email that is sent these fields are usually already set.
subject- set an alternate subject for the email.from- set an alternate from address for the email.preheader- set an alternate preheader for the email.plaintext- set an alternate plaintext for the email.cc- carbon copy recipients. Must be in standard email format. Multiple addresses should be separated with a semi-colon.bcc- blind carbon copy recipient. Must be in standard email format. Multiple addresses should be separated with a semi-colon.reply-to- set the reply-to header of the email. Must be in standard email format. Only a single address is allowed.
For example:
Hello, your confirmation code is{{profile.confirmation_code}}.
It's also possible to send a subject or from with a personalization token, for example:
When the email is sent if the contact has a personalization field of custom_id it will automatically be inserted.
email is also provided.dsid is ignored and each address is resolved to (or created as) a contact.filename → base64-encoded file bytes. See Including Attachments for the encoding recipe.{{profile.}} personalization tokens within the email body, subject, or from address.