Yes — the Email API supports BCC.
Add an optional bcc array to the notification object in your /createEmailMessage request. Each address in the array receives a copy of the email without the other recipients seeing it.
{
"request": {
"application": "XXXXX-XXXXX",
"auth": "YOUR_API_ACCESS_TOKEN",
"notifications": [
{
"send_date": "now",
"preset": "XXXX-XXXXXXXX",
"subject": "Your receipt",
"devices": ["user@example.com"],
"bcc": ["bcc1@example.com", "bcc2@example.com"]
}
]
}
}
See the createEmailMessage reference.
Caveats
-
/createEmailMessageis marked deprecated in favour of Messaging API v2, although it remains fully operational. - The Messaging API v2
EmailPayloaddoes not currently expose abccfield. If you need BCC via the API today, use/createEmailMessage.
Alternative: Customer Journey
You can also set BCC recipients on the email element of a Customer Journey, where the element configuration includes a BCC field.
Comments
0 comments
Please sign in to leave a comment.