2 Answers
- Newest
- Most votes
- Most comments
0
Hi,
Thank you for sharing your observations in detail. I would like to mention that I am able to replicate the behaviour shared by you.
Further, I am also able to move past this behaviour after using Substitutions
instead of Context
either under Addresses or Endpoints in the SendMessages API call.
I used the following command at my end :-
aws pinpoint send-messages --application-id <application-id> --message-request file://file.json
The contents of file.json is mentioned below :-
{
"Addresses": {
"<email>": {
"ChannelType": "EMAIL",
"Substitutions": {
"tripId": ["1223445"]
}
}
},
"MessageConfiguration": {
"EmailMessage": {
"FromAddress": "<from-address>"
}
},
"TemplateConfiguration": {
"EmailTemplate": {
"Name": "tesst",
"Version": "1"
}
}
}
In case of any follow up queries, please reach out to us via creating a support case with us.
0
Yes, I was able to make this discovery as well.
I wish AWS would update the Pinpoint documentation to more clearly define when to use Context vs. Substitutions, since they are very similar as to how to use them.
answered a year ago
Relevant content
- asked 5 months ago
- asked 4 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago