We’ve started providing more specific error messaging when adding or updating e-commerce customers.

Previously, when managing e-commerce customers, the API would sometimes return a vague error with the message, “Your request could not be processed.” 

We fixed these errors to be more actionable. The large majority are related to email validation and will look like:

{ "title": "Customer Was Not Saved", "status": 400, "detail": "[email protected] is an invalid email address and cannot be imported.", }

List carts now returns the created_at and updated_at dates for each cart.

We had a bug where created_at and updated_at were blank strings for each cart in the list of carts.

We fixed a bug in the report_summary section of the individual campaigns endpoint for parent automation and variate campaigns. Previously, we reported 0 total clicks for those campaign types; now we will report the sum of clicks between the child campaigns.

This falls in line with the expected behavior elsewhere in the report_summary section for other stats (like opens).

We updated the description for the List response’s visibility property, and removed visibility from the body parameters when adding and updating a list.

visibility is a legacy setting, and no longer in use. Please note that although we removed it from documented body parameters, we’ll still accept it as a parameter.

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.