Mailchimp Marketing API
Conversations API removal
Deprecated, no dateSubscribe to Mailchimp Marketing APIShare
Mailchimp Marketing API deprecated GET /3.0/conversations* without giving a shutdown date yet.
Calls it hits
GET /3.0/conversations*
What to use instead of these calls
None in the API: campaign replies and other messages now live in Inbox, which these endpoints do not return.
Inbox data has no API replacement: whether to keep reading past Conversations or drop the feature is a product decision.
In Mailchimp Marketing API's words
Conversations has been deprecated in favor of Inbox and these endpoints don’t include Inbox data. Past Conversations are still available via this endpoint
Facts
- API
- Mailchimp Marketing API
*.api.mailchimp.com - Kind
- Removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Mailchimp Marketing API's own pages
Questions
When does this change take effect?
Mailchimp Marketing API deprecated GET /3.0/conversations* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Mailchimp Marketing API has not given a shutdown date yet.
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
-
/2.0/*Version retirement Stopped working -
/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
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.