What Mailchimp Marketing changed, 30 April 2026 to 16 July 2026
292 operations became 298. None were removed, 0 were newly deprecated, 6 were added, and 0 request fields became required.
Read from mailchimp/mailchimp-client-lib-codegen at 7c96fc9 and e8bcdc9 (version 3.0.91). Generated 31 October 2026 by the specification parser the APIBreak Action uses, applied to Mailchimp Marketing's published specification.
Mailchimp keeps the description its client libraries are generated from in mailchimp/mailchimp-client-lib-codegen. This page reads the Marketing API file, spec/marketing.json, not the Transactional one. Version policy and shutdown dates are not in the specification, so this page does not state them; it reads the deprecated flag on each operation.
Removed from the specification
Nothing was removed in this window. That is a real result, not a gap in the check.
Newly deprecated in this window
A deprecation is the notice period. It is the cheapest moment to act and the easiest one to miss. This list compares operations present at the baseline.
No compared operation (one paired with a baseline operation) gained the deprecated flag in this window.
Deprecated as of the current specification (4)
Everything the vendor currently marks deprecated, whether or not it changed recently. The vendor has flagged each of these for possible removal, with or without a date attached.
- GET /conversations
- GET /conversations/{conversation_id}
- GET /conversations/{conversation_id}/messages
- GET /conversations/{conversation_id}/messages/{message_id}
Entries without a link were already marked deprecated at 7c96fc9 · 30 April 2026, the baseline compared here.
Mailchimp Marketing API questions
Every answer below is computed from the snapshot above, and each links to the Mailchimp Marketing specification it was read from.
- Which Mailchimp Marketing API endpoints were removed recently?
- None between 30 April 2026 and 16 July 2026, in spec/marketing.json in mailchimp/mailchimp-client-lib-codegen. It went from 292 to 298 operations in that window, and every operation present at the start was still there at the end, at the same URL.
- Source: mailchimp/mailchimp-client-lib-codegen, the two commits compared
- Which Mailchimp Marketing API endpoints are deprecated?
- As of 16 July 2026, spec/marketing.json in mailchimp/mailchimp-client-lib-codegen marks 4 operations deprecated: GET /conversations, GET /conversations/{conversation_id}, GET /conversations/{conversation_id}/messages and GET /conversations/{conversation_id}/messages/{message_id}. No compared operation (one the comparison paired with a baseline operation) gained the deprecated flag between 30 April 2026 and 16 July 2026. 4 were already deprecated at the baseline.
- Source: mailchimp/mailchimp-client-lib-codegen, the two commits compared
- Did any Mailchimp Marketing API request fields become required?
- None between 30 April 2026 and 16 July 2026, among the JSON request bodies in spec/marketing.json in mailchimp/mailchimp-client-lib-codegen the comparison could read. A field inside a union (anyOf or oneOf) is not compared, so it is not counted either way.
- Source: mailchimp/mailchimp-client-lib-codegen, the two commits compared
- Where is the Mailchimp Marketing OpenAPI specification?
- In the mailchimp/mailchimp-client-lib-codegen repository on GitHub. This page reads spec/marketing.json at commit e8bcdc9 (version 3.0.91), dated 16 July 2026.
- Source: mailchimp/mailchimp-client-lib-codegen on GitHub
The Action does not check Mailchimp Marketing yet
It checks GitHub REST and Stripe. If you want your CI to check the Mailchimp Marketing endpoints you call, say so in an issue, because requests like that decide which vendor the Action should support next.