16 September 2026 Version 2 of the Mapp Fashion items endpoints is now available. We have standardised the inputs across the API and given each type of recommendation its own call, so that new integrations are quicker to build and harder to get wrong. Your existing integrations keep working exactly as they are.
Key Benefits
Ask for exactly what you display
Similar items, outfits and partner outfits are separate calls now, rather than one call that returns several kinds of result at once. Each response contains only what you asked for.
Fewer decisions when you integrate
The product identifier is a normal request parameter instead of part of the URL, the response format option works the same way on every endpoint, and the list of identifier types has been reduced to the ones our customers actually use.
A stable base to build on
These paths and their behaviour will stay as they are, and further work on the API will build on them. Version 1 remains available and maintained, with no end of support planned, so you can move one placement at a time or stay where you are.
How Does it Work?
The v2 endpoints use the same recommendation engine as v1 and return the same items in the same order. What changed is how you ask for them.
/api/v2/items/similar
/api/v2/items/outfits
/api/v2/items/partner_outfits
/api/v2/items/top
/api/v2/items/basket
To get started, see:
Availability
These endpoints are available to all Mapp Fashion API users.