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.

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

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

• Contributing to Open Commerce

• Open Commerce Git Formatting Conventions

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. 

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

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

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.

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.

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

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

The Batch Subscribe endpoint now accepts ‘transactional’ as a possible status value.

Previously, the Batch Subscribe endpoint did not accept ‘transactional’ in the status field, which did not match the behavior of adding an individual list member. This change allows you to add transactional list members using the Batch Subscribe endpoint moving forward.

We’ve added “field” and “field_message” to the Batch Subscribe error response. You’ll see data in these fields when a merge field error is encountered.

Previously, when you encountered a merge field error during a Batch Subscribe operation, you didn’t see any details about the field in the error. This can cause headaches when you’re troubleshooting a remedy.

These additional fields, when present, should provide more insight into how to resolve an issue.