Mapp Fashion: Product IDs, SKUs and Faceted Search in the API

New
  • 1 minute(s) read
Prev Next

14 October 2026 Mapp Fashion API responses now include product IDs and in-stock SKUs for the recommended items. You can request recommendations by SKU, and faceted search is available in version 2 of the API. All changes are additions or fixes, so your existing integrations keep working as they are.

Key Benefits

  • Attribute recommendation performance

    If you track products by SKU or product ID, you can now attribute recommended items directly.

  • Request recommendations by SKU

    Variant SKUs now work as identifiers in requests.

  • Faceted search in version 2

    Faceted search is now also available with the v2 response format.

How Does it Work?

The release extends the existing endpoints. Your requests stay the same unless you want to use the new options.

  • New fields: Recommended items now contain product_id, which groups all colors and sizes of a product, if your product data includes it. Recommendation Tracking can use it to attribute purchases at product level. available_skus lists the in-stock SKUs of each recommended item. Both are returned in version 1 and version 2, in the simple and in the detailed format. For how these fields relate to your Product Catalog, see Product and Customer Identifiers.

  • Lookup by SKU: Set identifier_type=sku and pass a variant SKU. For barcodes, use gtin. The value ean never worked and has been removed from the documentation.

  • Faceted search: /api/v2/facetted returns the same recommendations as the v1 endpoint, in the v2 response format. Price ranges are filtered with min_price and max_price. The v1 endpoint stays unchanged. For details, see the API documentation.

  • Basket fixes: Basket recommendations sorted with direction=asc now return results. If basket recommendations cannot be generated, the endpoint now returns an error code, for example 404 if no recommender is configured, instead of 200 with an empty list. Both apply to version 1 and version 2. If your integration treats every basket response as successful, check its error handling.

Note

Product IDs and SKUs are only returned correctly if product ID, style ID and variant ID are filled in your Product Catalog. available_skus also requires that your products have their real product images from the first import on. Placeholder images or dummy URLs can cause SKUs of other products to be assigned.

All changes are listed in the API changelog.

Availability

These changes are available now to all Mapp Fashion API users. No changes to your integration are required. For an overview of which identifier belongs where, see Product and Customer Identifiers.