API Export 1.0 and API 2.0 will be retired on June 5, 2023

[jjohnson]

API Export 1.0 and API 2.0 will be retired on June 5, 2023

[amro]

Not sure I follow so please let me know if I’ve misunderstood: any new endpoints in API 3.0 should already work

…

On Thu, May 4, 2023 at 7:38 PM Jeff Johnson ***@***.***> wrote: Supported in Mailchimp API 3.0 — Reply to this email directly, view it on GitHub <#325 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAEEBA2I4FRDW2MUGUZHJDXEQ4YJANCNFSM6AAAAAAXWKLXLQ> . You are receiving this because you commented.Message ID: ***@***.***>

[amro]

Hi @vlasar. Version 3.0.0+ of Gibbon has supported Mailchimp API 3.0 since release. Export API was a separate set of endpoints for exporting large amounts of data. The latter API is being retired, and if you're not using the Export API then you've nothing to worry about.

You can continue to use the version of Gibbon you have or upgrade to the latest. When you decide to upgrade there should be minimal or no changes needed in your codebase, but please double check the changelog to confirm that. (There may be newer version of dependencies required, etc.)

[amro]

Thanks @jjohnson. I can release an update to remove Export API support in the near future

[amro]

BTW, is there a public announcement of this? Failing to find it

[jjohnson]

I also have not seen anything public. Email comms:

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.

[amro]

Thanks so much — I wouldn’t have known otherwise. I’ve got the changes merged and I’ll push an update a little closer to June 5

…

On Thu, May 4, 2023 at 7:28 PM Jeff Johnson ***@***.***> wrote: I also have not seen anything public. Email comms: 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. — Reply to this email directly, view it on GitHub <#325 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAEEBGIWBL6TG6FS5BY4ILXEQ3QXANCNFSM6AAAAAAXWKLXLQ> . You are receiving this because you commented.Message ID: ***@***.***>

[jjohnson]

Is the only fix dropping Export support in Gibbon?

[amro]

Gibbon is a wrapper around MC’s API and not more — yup. Is there something I’m missing?

…

On Thu, May 4, 2023 at 7:31 PM Jeff Johnson ***@***.***> wrote: Is the only fix dropping Export support in Gibbon? — Reply to this email directly, view it on GitHub <#325 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAEEBG6NSEWKZQ2GD26RVLXEQ33XANCNFSM6AAAAAAXWKLXLQ> . You are receiving this because you commented.Message ID: ***@***.***>

[jjohnson]

Supported in Mailchimp API 3.0

[vlasar]

Hello @amro,

Thank you for all your work.

We just received the same email yesterday, even though we are using 3.0.2 version of this gem (and not using the export API at all), which seems to already be using v3 of the MailChimp API? We can upgrade to the latest version, I'm just worried that we won't know if that was the issue.

[vlasar]

@amro thank you for the confirmation!