Introduction

Dressipi’s API gives you access to personalized fashion recommendations, item metadata, and authentication workflows. It is designed for use in both client-side and server-side environments, depending on your integration needs.

What You Can Do

With the Dressipi API, you can:

• Retrieve item details and fetch related product or outfit recommendations
• Request personalized suggestions for users, including facetted and themed types
• Handle authentication using JWTs for secure server-side communication

The API is divided into the following sections:

Deployment Modes

Client-side Integration

When used in a browser context, the API uses cookies managed by Dressipi’s tracking script. Authentication happens automatically via the dressipi_jwt cookie. No manual token handling is required – any authentication parameters sent manually will be ignored.

Server-side Integration

In server-side scenarios, authentication requires explicit handling via a JWT. The token must be submitted in the x-dressipi-jwt request header.

• If the token is missing or expired, item-related endpoints will return anonymous results (where possible).
• You can validate the token by checking its exp (expiration) claim.
• The token is refreshed automatically by the tracking tag when used in a browser environment.

URL

https://dressipi.example.com/api

The URL includes your domain and should include the method name.

How to Use This Documentation

All endpoint pages listed in the navigation menu include:

• A description of the endpoint and its purpose
• Required authentication headers
• Definitions for path and query parameters
• A “Try it” function to execute test requests
• Example response codes and curl command samples

Some parameter values (e.g. identifier_type) may depend on your integration setup – feel free to reach out for guidance.

Access the Regular Dressipi Documentation

Looking for more than the API?
Explore use cases, technical background, and integration guides in the full Dressipi documentation.