Updates on releases, changes, and bug fixes for Mailchimp's API.
Joined January 2009
- Tweets1.6K
- Following1.1K
- Followers3.9K
- Likes9
Our third winner is Tree House Craft Coffee and Frozen Yogurt, who rose to the challenge after Hurricane Harvey by opening their doors to offer relief to first responders and flood victims, and providing public restrooms, free coffee and electricity to their community. 🏆
Congrats to this year’s small business heroes, we’re proud to recognize you! 🏆
Learn more about the impact they’re making in their communities: spr.ly/6011zpuHf
We’re shutting down API 1.1, 1.2, and 1.3 on April 2, 2019, and encouraging all developers to update to Mailchimp API 3.0. More details here: eepurl.com/gh6WY1
We have deployed a fix and believe these problems are now resolved. Please let us know if you see further issues with login or site errors.
We believe we’ve identified the cause of the earlier errors, and we’re continuing to investigate. We’ll share updates as we know more.
We're seeing errors on login and for customers currently signed in, including our API and mobile clients. We are investigating now and will post updates soon.
Mailchimp API retweeted
Developers, please be sure to upgrade your TLS connections before May 31, 2018. Here's why: expi.co/01Yokq
Hey Debby. Mind sending an email to our Support team at [apihelp at mailchimp dot com]? They’ll be able to look into this.
Ah, eepurl.com/b2Q7Rb offers some insight on compliance issues. Leaving feedback to add that message to API docs. Thanks John!
That response was added a while ago to ensure unsubs/cleaned addresses aren't added back without opting in. It's CAN-SPAM required.
That response is seen when subscribing an unsub or cleaned address. Resend confirmation email using status=pending if it's an unsub.
The /reports/:id/sent-to string will give you the people the campaign was sent-to, Frank. More info: eepurl.com/cvs6Nv
Reminder: We're sunsetting API v1.0-2.0 on Dec. 31 now that v3.0 works with most in-app features. More details: eepurl.com/cojF21
We’ve made more improvements to API 3.0 as we prepare to sunset older versions on Dec. 31, 2016. Here’s what’s new: eepurl.com/chXNvP
Thanks for stopping by chats earlier. The API team wanted to make sure you got that in-app workaround, albeit less than ideal.
The data needs to be stored in your list for each subscriber, then field merge tags in the campaign can pull that data.
If you're a Ruby user, check out this wrapper for our API by our friend @amdev. xitter.cf/amdev/status/735299370…
@chosrgyamdrun A large count may cause timeouts to occur. We recommend using a combination of "offset" and "count": eepurl.com/bYbChX