October 2026
Feature
Recommended items now include product_id, the identifier that groups all colors and sizes of a product. Responses also contain available_skus, which lists the in-stock SKUs of each recommended item. Both are returned in v1 and v2, for every garment format.
identifier_type=sku now resolves variant SKUs on all endpoints.
We’ve released a new endpoint, /api/v2/facetted. It returns the same recommendations as /api/recommendations/facetted, in the v2 response format. Filters are passed as an object keyed by filter name, and price ranges are filtered with min_price and max_price. canonical_only, fields and device_type are not supported in v2. /api/recommendations/facetted is unchanged.
Bugfix
items/basket with direction=asc now returns results in v1 and v2.
The identifier_type value ean has been removed from the documentation. It never worked. Use gtin instead.
items/basket now handles errors like items/top and items/similar in v1 and v2. If no recommender is configured, it returns 404. Server errors and timeouts return 500. In v1, other errors return 422. Previously, these cases returned 200 with an empty list. Unknown or empty basket ids still return 200 with recommendations.
Documentation
The default of direction on items/basket is desc, not asc as previously documented. In v2, items/basket accepts identifier_type, max_reduced_by and include_user_data, but not include_fashion_ids. The reference now also documents max_reduced_by and outfits_per_occasion on v2 partner_outfits, exclude_source_garment on v2 similar, max_reduced_by on v1 top and basket, and unisex as a department on v2 top.
September 2026
Feature
We’ve released version 2 of the items endpoints. Each type of recommendation now has its own call, and the product identifier is passed as a parameter instead of being part of the URL.
/api/v2/items/similar
/api/v2/items/outfits
/api/v2/items/partner_outfits
/api/v2/items/top
/api/v2/items/basket
The response changed too. A v2 call returns only the key that applies to that endpoint, so /api/v2/items/similar returns similar_items without the empty outfits and partner_outfits keys that v1 sends alongside it. If you move an existing integration across, the code that reads the response needs adjusting.
A few parameters changed with it. garment_format now takes simple or detailed, where simple returns the same as the v1 value retailer_ids. include_dressipi_ids is now include_fashion_ids and defaults to false, so raw garment ids are only returned if you ask for them. max_similar_items is now max_items. The methods, try_all_methods, fields, stores, sku_refinement and include_user_data parameters are not part of v2.
v1 is unchanged and still maintained, so existing integrations don’t need to do anything. New integrations should use v2 wherever a v2 endpoint exists.
February 2026
Feature
We’ve released a new call, items/basket, that allows you to make curated recommendations based on products on the page.
December 2025
Feature
We’ve released a new call, items/top, that lets you make curated recommendations to customers.
September 2025
Bugfix
Fixed an issue where the API used an outdated recommendation model for unknown users or first page views. The correct, up-to-date recommendation model is now applied.