Mailchimp Marketing API
/2.0/* version retirement
Stopped workingSubscribe to Mailchimp Marketing APIShare
On June 1, 2023, Mailchimp retired API 2.0. Requests sent to the /2.0/* endpoints now fail and return an HTTP 410 status message. Calls made to these endpoints are no longer supported.
Calls it hits
/2.0/*
What to use instead of these calls
Move the calls to the Marketing API 3.0 (/3.0/*).
In Mailchimp Marketing API's words
We retired API Export 1.0 and API 2.0 on June 1, 2023. We won’t support calls to these endpoints after the retirement date and will return an HTTP 410 status message.
Facts
- API
- Mailchimp Marketing API
*.api.mailchimp.com - Kind
- Version retirement
- Announced
- December 31, 2016
- Takes effect
- June 1, 2023
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Mailchimp Marketing API's own pages
Questions
When does this change take effect?
Calls to /2.0/* on Mailchimp Marketing API stopped working on June 1, 2023.
What happens to calls after June 1, 2023?
They have failed since June 1, 2023.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Mailchimp Marketing API 4
-
/export/1.0/*Version retirement Stopped working -
No date
GET /3.0/listsParameter removal Deprecated, no date -
No date
GET /3.0/lists/{id}Parameter removal Deprecated, no date -
No date
GET /3.0/conversations*Removal Deprecated, no date
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.