Skip to content
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

Update Documentation so That Using Substitutions is Easier #681

Closed
thinkingserious opened this issue Apr 24, 2018 · 2 comments
Closed

Update Documentation so That Using Substitutions is Easier #681

thinkingserious opened this issue Apr 24, 2018 · 2 comments
Labels
difficulty: easy fix is easy in difficulty status: help wanted requesting help from the community type: community enhancement feature request not on Twilio's roadmap

Comments

@thinkingserious
Copy link
Contributor

Issue Summary

Please see the thread here.

@thinkingserious thinkingserious added type: community enhancement feature request not on Twilio's roadmap status: help wanted requesting help from the community difficulty: easy fix is easy in difficulty up-for-grabs labels Apr 24, 2018
@tkafka
Copy link

tkafka commented Aug 7, 2018

To everyone as desperate as me yesterday: in v3 API you need to use dynamic_template_data instead of substitutions, this isn't yet documented anywhere!

Then use {{var_name}} in email template and dynamic_template_data: { var_name: "var_value" } in API call.

@thinkingserious
Copy link
Contributor Author

Thanks for sharing your solution @tkafka!

Please follow this thread for progress.

With Best Regards,

Elmer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
difficulty: easy fix is easy in difficulty status: help wanted requesting help from the community type: community enhancement feature request not on Twilio's roadmap
Projects
None yet
Development

No branches or pull requests

3 participants