Changelog

Prev

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.