Mailchimp Developer LogoMailchimp Developer Wordmark
February 23, 2023Action Required

Added support for 401 Unauthorized response code

Transactional

What

We’re now supporting the 401 Unauthorized response code. When a customer makes a request using any invalid or revoked API Key, we’ll respond with 401 Unauthorized. If you’re specifically targeting HTTP response codes other than 200, you may need to update your code.

Why

Previously, we responded to requests made with an invalid or revoked API key with a 500 Server Error status code. We updated this to bring our response in line with proper semantics and allow more efficient status monitoring.

  • February 21, 2023

    Updated export download security

    Transactional

    What

    Export notification emails now include a link that prompts you to login to your Mailchimp account before you can download your report from the Exports page.

    Why

    Previously, our export emails contained a direct link to download the report. We’ve updated our security to require login before you can access the report on the Exports page.

  • January 12, 2023

    Added empty alt tag to tracking pixels

    Transactional

    What

    We added an empty alt tag to the pixel that is included in your emails when you’ve enabled open tracking.

    Why

    Many spam filters like to see alt tags included for all images, but we’re leaving the one associated with the open tracking pixel empty so that screen readers won’t see it. This helps keep your email from being marked as spam while not creating a poor user experience for your customers who use screen readers.

  • September 1, 2022

    IP validation now enforced on Add or Update List Member

    Marketing

    What

    We’re now checking the fields ip_signup and ip_opt for valid IPv4 and IPv6 addresses when you’re using the Add or Update List Member endpoint.

    Why

    We added IP validation to the contact importer and we are updating the API to maintain feature parity.

  • December 20, 2022

    Added docs around contributing to Open Commerce

    Open Commerce

    What

    We’ve added two docs that describe how you can contribute to Open Commerce:

    Why

    We’re committed to the open source community and these documents explain the processes and standards we use so you can more easily contribute to the project. 

  • November 8, 2022

    Added a field to various Transactional responses when messages are queued

    Transactional

    What

    We’ve add a queued-reason field to API responses when we return a status of queued. 

    This change affects the following endpoints:

    • messages/send

    • messages/send-template

    • messages/send-raw

    Why

    This new queued-reason field gives you more information and context why messages have been queued rather than sent.

  • October 17, 2022

    Added new command line interface

    Open Commerce

    What

    We’ve written a new CLI so you can start developing your Open Commerce projects more easily. Now, you only need a simple command to create your project, create a custom plugin, or add the Open Commerce admin and storefront to the project. Check out all the commands at the  CLI ReadMe or by running reaction help in your terminal. Or, see our guides and documentation for more details.

    Why

    Getting started or completing routine workflows with Open Commerce had become slow and cumbersome due to excessive memory use and device slowdowns. With the new CLI, you can run the API, storefront and admin applications independently, which frees up memory and improves performance.

  • October 6, 2022

    Added time limit to message scheduling

    Transactional

    What

    We’ve added a limit to how far in the future you can schedule messages. Currently, we’re allowing you to schedule messages within a year from the date of scheduling.

    This validation change affects the following APIs:

    • messages/send

    • messages/sendRaw

    • messages/sentTemplate

    • messages/reschedule

    Why

    We’re adding this validation limit to increase database efficiency and performance.