@Nagra’s solution is good but it will throw an error when executed from the client’s browser due to the Same-Origin Security Policies in effect. In essence, these security measures are there to prevent cross site requests that occur when the originator and the sender are on different domains. If you see errors like the below … Read more
As someone who regularly codes emails for marketing campaigns at my job, I feel your pain. Gmail, along with many other email clients, can be a bit funky to code for. For one, it strips out any CSS that’s outside the body. So putting in things like media queries and document level styles don’t work. … Read more
Having spoken to MailChimp, the certificate they’re still (Jan 2016) using – for compatibility reasons, they told me – is the GTE CyberTrust Global Root (note GTE was bought by Digicert), so you don’t need to replace the entire bundle, just add or force PHP to read this certificate: https://gte-cybertrust-global-root.digicert.com/info/index.html (note you’ll get an ‘insecure … Read more
Based on the List Members Instance docs, the easiest way is to use a PUT request which according to the docs either “adds a new list member or updates the member if the email already exists on the list”. Furthermore apikey is definitely not part of the json schema and there’s no point in including … Read more
You don’t need an API key, all you have to do is plop the standard mailchimp generated form into your code ( customize the look as needed ) and in the forms “action” attribute change post?u= to post-json?u= and then at the end of the forms action append &c=? to get around any cross domain … Read more