Manage a transactional campaign
Describes the request and response details of this Moosend API endpoint to create a transactional campaign.
Request
|
Parameter |
In |
Type |
Required |
Description |
|---|---|---|---|---|
|
|
header |
string |
true |
Determines the expected format and data type to retrieve the response data. Value: |
|
|
query |
string |
true |
The API key of your account. |
|
|
body |
object |
false |
An array containing the parameters of the sender: Email - the email address of a verified sender. sendersName - the name of the sender name displayed in the recipient's inbox. |
|
|
body |
object |
false |
An array containing the parameters of the sender the user can reply to: Email - the email address of one of a verified sender. sendersName - the name of the Reply to email displayed to the user when the user clicks Reply. |
|
|
body |
string |
false |
The subject line of the email message displayed to the recipient. It may contain parameters for personalization. When no value is provided, use the subject of the template. |
|
|
body |
array |
false |
An array of email addresses to include as carbon copy (Cc) recipients of the message. |
|
|
body |
array |
false |
An array of email addresses to include as blind carbon copy (Bcc) recipients of the message. |
|
|
body |
GUID |
false |
Statistics will be registered to the campaign with this ID. If you have created a template id, you can find it in the user interface. If the array |
|
|
body |
string |
false |
The name of the transactional campaign that this message will be sent for. Transactional campaign names are unique. If the array |
|
|
body |
array |
false |
Content types: Type - the type of content to send. Value - the format specified by WebLocation - the URL that holds the content to use for this message. To reuse it for the next requests and avoid re-downloading, cache it to S3 for 24 hours. Only one |
|
|
body |
array |
true |
A list of recipients of the transactional message. It may contain personalization parameters. To - an array containing the parameters of the receiver Email - the recipient email address (text/plain). Name - the recipient name (text/plain). Cc - an array of email addresses to include as carbon copy (Cc) recipients of the message. Bcc - an array of email addresses to include as blind carbon copy (Bcc) recipients of the message. Substitutions - the values to substitute in the message content/subject for the current recipient, in the form of key/value pairs. There are some restricted keywords implemented, see note below. |
|
|
body |
array |
true |
BypassUnsubscribeManagement When set to Default: IncludeUnsubscribeLink Let's you turn the unsubscribe link on or off or provide a website link to use instead; this will temporarily override the saved settings without changing them. Default: ScheduledForDatetime When omitted, the transactional campaign will be dispatched immediately. If the value exists in the format “ Default ScheduledForTimezone When omitted, the system will take the time zone from the user’s settings if present, otherwise will default to “ Default |
|
|
body |
object |
false |
An array containing the parameters of the attachments: - Content - A base64 string that represents the file bytes of the attachment (Required). Type - The MIME type of the attached content (e.g. application/pdf, image/PNG) (Required). FileName - The file name of the attachment that the recipient will see (Required). Disposition - Allowed values are: “inline”, “attachment” (Required). ContentId - A user-defined string that maps an embedded image to an attachment. (Required only for inline disposition). |
Note
Restricted keywords for substitutions: datetime, ab, appDomain, appDomainProtocol, trackingDomain, doubleOptInDomain, utilitiesDomain, updatePreferences, emailSentTo, forwardToFriendLink, updateProfileLink, verificationLink, unsubscribeLink.
Response
|
Status |
Description |
Headers |
Schema |
|---|---|---|---|
|
|
The request is successful. |
|
N/A |