Hi Mailchimp Integrator,
On April 2, 2019, Mailchimp will shut down API 1.1, 1.2, and 1.3. Before this date, you must update any integrations to Mailchimp API 3.0 for it to continue working as expected for you and your customers.
What’s changing
We’ll no longer allow integrations to use Mailchimp API 1.1, 1.2, and 1.3. We stopped supporting these APIs at the start of 2017. At the time, developers could keep using Mailchimp API 1.1, 1.2, and 1.3 for their integrations; however, we’re no longer comfortable allowing their continued use. As these older APIs age, they could cause integrations to break at any time, which would negatively impact our mutual customers.
If your integration isn’t using Mailchimp API 3.0 by April 2, all requests will fail with an http 410 status code and return an error message that the integration needs to be updated to continue working.
What you need to do
Before April 2, you’ll need to ensure your integration is updated to Mailchimp API 3.0 and that your users are on the latest version. We offer a lot of great resources to help with this transition in our Mailchimp API documentation. In most cases, the endpoints you’re currently using will have clear equivalents in Mailchimp API 3.0.
Additionally, it’s important to note that we stopped supporting Mailchimp API 2.0 at the start of 2017, along with Mailchimp API 1.1, 1.2, and 1.3. While Mailchimp API 2.0 will continue to work for now, we strongly encourage that all integrations transition to Mailchimp API 3.0, which is the only Mailchimp API that’s fully supported by our team of engineers.
What’s next
On March 4, we’ll email Mailchimp customers who have recently made calls on integrations that use API 1.1, 1.2, and 1.3. Our email will encourage customers to verify that they’re on the latest version of their integration and that the integration uses Mailchimp API 3.0.
Questions
If you need additional guidance or support, reply to this email and we’ll be happy to help.
Thanks,
Mailchimp Support
|
|
|
|
|
