-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
substitutionData per recipient #57
Comments
Thanks for pointing this out @woodscreative. I think this is because we don't wrap the API that far down for recipients, rather just pass those through to the API. @beardyman I wonder if there is something we could do to translate keys from title case to snake case automagically? |
Thanks @woodscreative I was going around in circles and couldn't work out why the data wasn't coming through to the template. |
I'm going to leave this ticket open until we have the 2.x refactor out the door. We're planning on removing the parameterMapping, which is not only confusing to a lot of people, but causes exactly these types of problems. |
Sorry to hook into this issue … but I am more confused than before. Does it mean it is impossible to personalize emails sent via API? Currently I have my recipients … How do I implement the substitutionData? Do they have to be in the $address array or do they need to be an array of its own? Perhaps I missed some part of the docs, but I can't find a good example. |
Ok, now I got it. That was like Where's Waldo It is not substitutionData but substitution**_d**ata
|
2.0 has been released: https://packagist.org/packages/sparkpost/sparkpost |
Hi, it appears per recipient substitution data key is inconsistent consider the following:
The text was updated successfully, but these errors were encountered: