-
Notifications
You must be signed in to change notification settings - Fork 625
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
Problem when using {key} as a substitution #264
Comments
Actually, it spanned from only the single item
Should actually be
Requires all parameters to be sent over as string enclosed in quotes. Should make this aware somewhere in the Personalizations section |
Thank you @LewisTheobald! I will leave this ticket open until we update the docs and code to clarify. |
Can you update the the error object that is sent back to include more information than {"errors":[{"message":"Bad Request","field":null,"help":null}]} I didn't find this to be very useful in diagnosing the problem |
Yes, that will be part of the update. Thanks for taking the time to provide feedback! |
@LewisTheobald thanks saved me a few hours of debugging. |
Please take a moment to fill out this form so we can send you some swag :) With Best Regards, Elmer |
This has been moved here. |
Issue Summary
We've been using the { and } symbol as the wrapper around our substitution tags. When migrating to v3, these come back with a '400 Bad Request'. Though the request works fine if I remove the substitutions section.
Steps to Reproduce
The JSON payload for the personalistion section is:
The response is:
If I remove the substitutions block or change it to another symbol, we receive '202 Accepted'.
Technical details:
The text was updated successfully, but these errors were encountered: