Changelog

Customer Segmentation API reference corrections

Thanks to user feedback, we audited the Customer Segmentation REST reference against the live API and corrected several inaccurate response definitions for the Segments and Shopper Profiles endpoints.

• Delete responses — Delete Segments, Delete Shopper Profiles, and Remove Shopper Profiles from Segment now correctly document a 200 response with a batch result body (data, errors, meta) and a 422 for invalid input, instead of an empty 204.
• Validation errors — Create Segments, Update Segments, and Create Shopper Profiles now document 422 for invalid request data, instead of 400.
• Response bodies — Create, update, add, and remove responses now document the full batch result envelope, including the data, errors, and meta (total, success, failed) fields the API returns. Paginated list responses now document the pagination links object.

For details, see the Customer Segmentation API reference.