Mapp Fashion API

Mapp Fashion's API provides access to personalization features for fashion and apparel use cases. It allows you to retrieve product recommendations, including related items and curated suggestions, as well as product data for integration into your shop or application.

Recommendations can be generated based on specific items, user profiles, or predefined contexts.

When to Use This API

The Mapp Fashion API is typically used after the core Mapp Fashion integration is in place, including:

• Product data feeds

• Tracking implementation

• Enrichment and recommendation model setup

The API provides access to recommendation results and product data but does not replace the underlying data integration.

For a complete overview of data flows, setup, and system architecture, refer to the Mapp Fashion Integration Overview and related documentation.

Note

Some request parameters, headers, or response fields may still use the term dressipi. This reflects legacy naming within the API and does not indicate a separate product. All references to dressipi in the API correspond to Mapp Fashion.

What can I do with the Mapp Fashion API?

• Fetch related products or outfit recommendations

• Request personalized suggestions for users, including facetted and themed types

• Retrieve product details

• Handle authentication using JWTs for secure server-side communication

API Structure

The API is available in two versions. v1 (/api/...) covers the established endpoints and is fully maintained, with no deprecation planned. v2 (/api/v2/...) standardises the inputs and provides one endpoint per recommendation type. New integrations should use v2 wherever a v2 endpoint exists. For which endpoint to use when, see Recommendation Strategy.

The reference is divided into the following sections:

• Items (v2)
  The v2 endpoints: similar items, outfits, partner outfits, top recommendations and basket recommendations, each as its own endpoint.

• Items (v1)
  The v1 endpoints: related outfits or items, complementary items and product information.

• Recommendations
  Personalised suggestions for users, including facetted and themed options. There is no v2 equivalent for these, so use the v1 endpoints.

• Authorization
  Access tokens for authenticated requests using JSON Web Tokens (JWT).

Recommendation Context

Recommendation results depend on the context parameters provided in the request.

If no explicit context (for example, department) is defined, recommendations are generated based on default catalog settings.

For shops with multiple departments (such as menswear, womenswear, or kidswear), always provide the appropriate context to ensure relevant results — especially for general placements such as homepages or basket pages.

Getting Started

To work with the Mapp Fashion API, follow these steps:

• Understand authentication, request structure, and core concepts in Core Concepts & Setup.

• Learn how to choose the right endpoint for your use case in Recommendation Strategy.

The API documentation also includes detailed endpoint references, parameter definitions and usage, and example requests and responses. Each endpoint page provides a description of the endpoint and its purpose, authentication requirements, definitions for path and query parameters, and example response codes and curl command samples.

Some parameter values (for example, identifier_type) may depend on your integration setup. Refer to the Basics section or validate your configuration accordingly.

Access the Full Mapp Fashion Documentation

For additional information beyond the API — including use cases, technical background, and integration guides — refer to the full Mapp Fashion documentation.