#4755 - An important change that may impact an integration you use
Good afternoon,
A customer has received the following email
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, ROSSINI 1882 SPA, 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.
API key(s): 5a39
You can find your API key in your account. It’s important to note that we can’t see where your API keys are used, only that they’re being used. Sometimes, the API key will include a label to describe which integration is associated with that API key. If you’re unsure which integration is associated with an API key, you or a developer will need to review any integrations connected to your Mailchimp account to determine which uses the API key.
After you know the integration that uses the API key, check the integration’s website, if applicable, to see if there is an updated version that uses Mailchimp API 3.0. If the integration isn’t on Mailchimp API 3.0, or if you can’t determine this for certain, you’ll want to consider switching to a different integration. Our integrations directory is a good place to find alternative integrations, or you can hire a Mailchimp partner to help create a custom solution to meet your needs.
If you or a developer created a custom integration for your account, you’ll need to ensure it’s updated to Mailchimp API 3.0 before June 5. If you’re the developer of your integration, we offer a lot of great resources to help you transition to 3.0 in our Mailchimp API documentation.
If you have any questions, please use one of our support options.
I guess you need to update the SugarChimp plugin. For this reason I ask if what was assumed is correct and an updated version for SugarSell version 12.3.0
Best Regards Sergio Schirone
a year ago
Hi Sergio. Happy to help. You are correct that the customer needs to update to the latest version of SugarChimp. The latest version of SugarChimp is SugarChimp 13.0.0 (which is for Sugar versions 12 and up.)
The latest version is under the Purchase on SugarOutfitters, but if you have any trouble finding it, feel free to let me know mailchimp@fanaticallabs.com.
Thanks, Heidi