MailChimp API 1.0 and 2.0 Retiring on 6/5/2023

Greetings - we just received an e-mail from MailChimp stating that API 1.0 and 2.0 are expiring in a month. And we need to upgrade to 3.0. This is the first we’ve heard of this.

In reading a past forum thread from 2019 when 1.3 was retired - it seems that it was determined that S2Member uses 2.0, and thus no further action was needed.

It seems that action may be needed now to keep this integration functional? Does S2Member need an update, or can we just use 3.0 and it work?

  • Chris
    (S2Member customers since 2014).

We’re writing to let you know that we will retire API Export 1.0 and API 2.0 on June 5, 2023. This action will cause integrations that connect to Mailchimp through these APIs to stop working as expected. We have identified that your account uses an integration that made a call to one of these impacted APIs in the last month.

Here’s more information about this change and what you need to do to avoid an interruption in the functions provided by your integration.

What’s changing

We’ll no longer allow integrations to use API Export 1.0 or API 2.0 after June 5, 2023. We stopped supporting these APIs on December 31, 2016, and all API documentation was taken offline in January 2019. Over the years, we’ve encouraged developers to update their integrations to Mailchimp 3.0. Our focus is on developing and maintaining Mailchimp API 3.0, so these retired APIs have increasingly seen performance issues. While we’ve managed some of these issues since we stopped supporting these APIs, we’re no longer comfortable continuing to maintain them.

What you need to do

Before June 5, you’ll need to ensure all integrations in your account use Mailchimp API 3.0. Below is the API key(s) used to connect to an affected integration. For security reasons, we can only provide the first 4 characters of your API key.


Thanks for reporting that. I’ll look into it. :slight_smile:

1 Like

Our developer found this on GitHub, and thinks it means the 3.0 integration may have already been handled:

So… we decided to be adventurous today and replaced the API Key with a new 3.0 one from MailChimp. Everything seems to have continued working as expected.

Thanks for the update, Chris.

I will still review the integration and make sure their v3 is actually supported by s2.



That GitHub thread doesn’t appear to indicate (to me) that the issue was addressed. It looks like the can was kicked down the road for 9 months but no indication of resolution. Then the issue was closed. Hopefully this recent message from Mailchimp will result in some action to confirm/verify the change.

Right, that’s what it seems to me as well. That’s why I need to take a close look, and do what’s needed for v3.