Previously, when an HTTP request was sent to the Marketing API, we redirect it to HTTPS. We’ve now stopped redirecting these requests and will instead return an HTTP 426 error code indicating the request needs to use HTTPS.

Users with affected API keys or Authorized Apps should have received an email about the change.

Although the Marketing API only accepts HTTPS requests, providing a redirect meant it still supported sending an initial HTTP request that transmitted a user’s sensitive information in plaintext. Returning a 426 error with the appropriate message helps ensure integrations are sending their requests securely.

Previously, when using the /reports/{campaign_id}/open-details/ endpoint within a batch operation, you could get an Unknown Filter error if you had more than 1,000 entries in the collection, or if you submitted query parameters other than since.

The endpoint was not correctly handling parameters, and would throw the Unknown Filter exception in cases when it should not. We removed this exceptional case, and will now ignore unexpected query parameters. Batch requests using this endpoint should now resolve successfully.

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": "invalid@gmaill.con 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.