Handling Recipient Errors

When the system has successfully received API requests that trigger actions for the recipients, it will return a successful HTTPS status code of 200 OK. API requests that fall into this category are the "Merge Trigger" and the "Trigger" APIs.

However, the triggered action might have mixed results. The response payload contains an array of messages about the success or failure for each individual recipient.

A success message for the recipient will look like this:

{
   "errorMessage" : null,
   "success" : true,
   "recipientId" : 72067
}
	

In a failure message, success is false and errorMessage will be one of the following. The response may or may not include the recipientId; if it is not possible to do so, then the recipientId will be -1.

errorMessage	Notes
RECIPIENT_STATUS_UNDELIVERABLE: Recipient deliverability status is undeliverable	The campaign is not sent to the recipient, because the recipient's deliverability status in the Profile List is set to undeliverable.Usually returns recipientId of -1.
FAILURE: Number of attachments cannot exceed 10 for a recipient	10-attachment limit includes both API payload and attachments set for the email campaign by the marketer.
FAILURE: Invalid attachment type, allowed types are png, jpg, jpeg, pdf, ical	The API accepts only Base64-encoded files of type PNG, JPG or JPEG, PDF, or ICAL.
FAILURE: The total size of the attachments cannot exceed 500 KB	500 KB size limit for attachments includes both API payload and attachments set for the email campaign by the marketer.