has anyone seen error
[error_key] => json.invalid.value.no_script_tags
[error_message] => #/email_content: Field does not support script content.
when sending HTML email through API?
The error you're getting generally points to some word in the html email that is disallowed or not understood. It's hard to say what that might be without seeing the html. In the absence of script tags, I would look for deprecated tags or anything that might not be current html.
Segmenting the email into portions, and testing those portions separately as their own html emails, can help narrow down the issue.
If you want to post your email with identifying information redacted, we might be able to take a look and help troubleshoot.
API Support Specialist
Finally we got it through, problem was with some styles like
offset:0 and mso-***
I wish there was a bit more detailed error message or some tool to test html, would save lots of time!
Thanks for the feedback and glad you got passed it. Our filtering is mostly to ensure that potentially harmful code, scripting that isn't supported by email clients and other items that could cuase problems for our customers are not accepted. However, like a filtering, I'm sure that there are some valid items that we're catching.
Is there any way you can send over what you tried to submit to our support team so we can take a look? If we are being too restrictive, we will work to fix any of those problems we can find. Your help is greatly appreciated.
Also, I'll bring the idea of an HTML validator and better documentation to our email teams. We're working on enhancing our custom code experience and this is a great time to bring those types of ideas to them.
This issue persists from what I can tell. I'm getting the same error as above, with no script tags in place. You can find the full contents of the email at http://cl.ly/code/1l1s410k1Y0W . Any help would be much appreciated.
Thanks for the report. We are using an inclusive filter when checking content so we do assume this will continue to come up over time as we find new browser extensions or some HTML 5.0/CSS 3.0 tags that are newer or changed. We'll take a look at this and update the filters.
I'm sorry for the frustration this has caused. I will forward the feedback onto our engineering teams--both the suggestion for the line number and excerpt when the email content error is thrown, and to include the word 'physical' when it is a physical address that's missing. Thank you for the feedback.
API Support Specialist
Unfortunately, I have to agree. Too much more waiting time and we'll have to make a choice to make a change. The hang-up is that we have close to 60,000 contacts and about 100 groups...that'll be one large export.
View API documentation, code samples, get your API key.Visit Page