Improperly formatted JSON request bodies will return a 400 status with details about the parsing error in the detail field and a title of “JSON Parse Exception”.

We weren’t properly capturing parsing errors when handling API requests. Now that we do, we’re able to return more helpful details to the caller so that they can fix their requests.

A full_name property was added to the response anywhere that members are returned.

Previously, to determine a member’s name, you needed to look at the merge fields. Although FNAME and LNAME are the default merge tags for names, they can be changed. The full_name property makes a best effort to provide the full name using common merge tags.

We improved our timeout and retry logic when uploading API batch job operations and results to S3.

We use S3 to store operations and results for API batch jobs. We weren’t handling timeouts when communicating with S3 as well as we could have; these fixes will improve reliability and throughput of our API batch jobs.

We’ve renamed Reaction Commerce to Mailchimp Open Commerce, and we’re relaunching on Mailchimp Developer with brand-new documentation and guides. The API’s GraphQL playground is also now available on Mailchimp Developer, and you can read past and upcoming Open Commerce release notes as well. 

The existing Reaction Commerce site and documentation will be redirected to new spots on Mailchimp Developer. At this time, we aren’t changing the name within the codebase—repos will still be accessible at the same locations on GitHub, and there are no breaking changes.

Reaction Commerce was acquired by Mailchimp in April 2020. As part of the transition, we are now integrating and enhancing Reaction Commerce as part of Mailchimp’s developer-focused products. 

On Tuesday, April 20th at 1:00PM ET we upgraded a router in our Atlanta data center. This should have no user visible impact, but it’s a core piece of our networking infrastructure and its replacement could cause periods of errors or unreachable hosts.

We’re maintaining and upgrading our hardware for increased reliability.

Prior to this change, 410 responses from audience webhooks were treated like any other error—we retried three times for the given change, and kept trying for other changes to the audience. Now a webhook that returns 410 will be disabled with no retries, and for all future changes to the audience. The Webhook entry on the Webhooks page in your Audience settings will indicate that it’s been disabled.

410 means a resource is gone and its absence is likely to be permanent. Properly interpreting this response means less load on our servers and the servers that are hosting the webhook. Additionally, this allows webhook implementers to disable calls to their webhook without needing to make an API call to explicitly do so.

The Marketing API’s PHP client library was not handling the fields and exclude_fields query parameters correctly. We’ve fixed a bug in the client generation that will process the arrays as CSV strings. This change will affect version 3.0.35 of the PHP client library.

A user reported unexpected behavior when passing in an array of strings, and we discovered that the Swagger Codegen utility was not parsing the collectionFormat for query parameters as expected.