Mailchimp Developer LogoMailchimp Developer Wordmark
November 16, 2021

Batch API limit now considers pending batch webhooks

Marketing

What

We now allow a user to submit up to 500 pending API batches. For each completed batch, we send those results to each batch webhook that has been created. A user will not be able to create more API batches if there are 500 outstanding batch webhooks that have yet to complete. A 429 status code will be returned in this instance.

Why

Previously, we did not have a limit on how many batch webhooks could be instantiated for a given user. This unbounded nature can have an impact on the performance of the API, which this new limit will help mitigate.

  • October 29, 2021

    Added camelCase support to Handlebars

    Transactional

    What

    In the past, our implementation of Handlebars did not support camelCase, so all variables had to be written using all lowercase letters or using snake_case. Using camelCase for variable names is now supported.

    Why

    A large portion of developers using the Handlebars templating engine are used to the JavaScript convention of writing variables in camelCase.

  • October 4, 2021

    Fixed Rejection Denylist display

    Transactional

    What

    ​​We fixed an issue that was causing the Rejection Denylist page to appear as blank.

    Why

    Expired entries were appearing on the Rejection Denylist page, which pushed out active entries and made the list appear empty. Now only active entries appear.

  • October 1, 2021Action Required

    Added Stripe SCA payments plugin

    Open Commerce

    What

    We’ve created a new Stripe plugin, api-plugin-payments-stripe-sca, and we recommend that all users of the existing Stripe plugin migrate to it. api-plugin-payments-stripe is now deprecated and will be supported until October 31, 2021. This release also affects the example-storefront repository, which now includes components to support 3D Secure validation.

    Thanks to contributor Janus Reith for his input.

    Why

    The new plugin is designed to comply with the current Strong Customer Authentication (SCA) regulation, part of PSD2 regulation in Europe, which requires changes to how your European customers authenticate online payments.

  • September 23, 2021

    Added new Allowlists series of endpoints

    Transactional

    What

    We’ve added a new series of Allowlists endpoints that are functionally identical to the Whitelists endpoints, but use new inclusive terminology instead. 

    Why

    In an effort to move towards using more inclusive terminology in our application, we’ve changed all instances of the terms “blacklist” and “whitelist” to “denylist” and “allowlist,” respectively. There may still be lingering uses of the old terminology in API responses or webhooks; please know that we are working on retiring all instances of those terms.

  • September 22, 2021

    Cleaning up batch webhooks when deleting API keys or app connections

    Marketing

    What

    When deleting an API key or removing an authorized app connection, we will remove the batch webhooks created by that key or connection.

    Why

    When a batch job completes, we send that response body to all created webhooks. Previously, these batch webhooks weren’t cleaned up when a user disconnected from an authorized app, or removed an API key.

  • September 14, 2021

    Data changes with Apple Mail Privacy Protection

    Marketing, Transactional

    What

    Apple is launching Apple Mail Privacy Protection, which may change campaign reporting data. Check out our Apple Mail Privacy Protection Resources for more.

    Why

    The Apple Mail Privacy Protection changes coming in iOS 15 will change Mailchimp’s email tracking for iOS users who opt in. Check our FAQ, but you may want to review how you use data and features related to opens and user location. If you surface this data in your integration, we recommend providing context on Apple’s changes.

  • September 7, 2021Action Required

    Adding a limit to Batch Webhooks

    Marketing

    What

    We’ve added a limit to the number of batch webhooks you can create: going forward, you will not be able to exceed 20 batch webhooks for a given Mailchimp account. If you attempt to create a new batch webhook via the POST /batch-webhooks endpoint and have already exceeded the limit, a 400 status code will be returned. In order to resolve this error, you will have to delete an existing batch webhook via the DELETE /batch-webhooks endpoint.

    Why

    Most users of the Batch Webhooks endpoint create fewer than 20 webhooks for their account. Allowing an unlimited number of webhooks for each account can have performance implications for the API.