Fashion Cloud API

Name: Fashion Cloud API
Brand: Fashion Cloud API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceInventoryapiKey3 EndpointsREST

For Agents

Authenticate against Fashion Cloud and retrieve B2B fashion product resources by identifier or list.

Install Jentic One Beta

Connect the Fashion Cloud API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Fashion Cloud API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Fashion Cloud API.

Exchange credentials for an access token via POST /auth/token

List available B2B product resources from a brand or retailer's Fashion Cloud account via GET /resources

Retrieve a specific resource (product asset, document, or catalogue entry) by id via GET /resources/{id}

GET STARTED

Start building with Fashion Cloud API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Fashion Cloud API for, with concrete tasks.

★ Brand Assortment Sync to Retailer PIM

Multi-brand retailers use Fashion Cloud to receive product data and assets from their brand partners. The API lets the retailer's PIM authenticate via /auth/token and pull resources via /resources on a schedule, eliminating manual catalogue uploads. Integration takes a couple of days given the small endpoint surface.

Call POST /auth/token to obtain credentials, then GET /resources to list the available product resources for syncing

Asset Pull for Storefront Display

Retailers pulling brand product imagery and copy use GET /resources/{id} to fetch individual resources by Fashion Cloud identifier, then push assets into their storefront CMS. Lets the retailer keep brand-approved content in sync without scraping. Useful for fashion marketplaces and multi-brand boutiques.

Given a list of resource ids, call GET /resources/{id} for each and push the returned product data into the storefront CMS

AI Buying Assistant via Jentic

Buyers and merchandisers use AI assistants that call Fashion Cloud through Jentic to look up brand resources by id during conversation. Jentic handles the X-API-Key credential and exposes /resources as an intent-matched operation, so the agent does not embed keys or manage the auth token exchange. Cuts integration time from days to under an hour.

Through Jentic, search 'retrieve a fashion product resource', load GET /resources/{id}, and execute with the resource id from the buyer's question

Key Endpoints

3 endpoints — the fashion cloud api provides programmatic access to the fashion b2b platform's product resources, used by retailers and brands to exchange product data, images, and assortments.

METHOD

PATH

DESCRIPTION

POST

/auth/token

Exchange credentials for an access token

GET

/resources

List available product resources

GET

/resources/{id}

Retrieve a specific resource by id

POST

/auth/token

Exchange credentials for an access token

GET

/resources

List available product resources

GET

/resources/{id}

Retrieve a specific resource by id

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Fashion Cloud X-API-Key is stored encrypted in the Jentic vault. Agents call operations by intent and Jentic injects the header at execution time — the raw key never enters prompts or logs.

Intent-based discovery

Agents search 'list fashion product resources' and Jentic returns the GET /resources operation with its filter schema, so the agent calls the right endpoint without reading the Apiary docs.

Time to first call

Direct integration: 1-2 days for the auth-token exchange and resource pagination. Through Jentic: under 30 minutes — search, load, execute.

FAQs

Specific to using Fashion Cloud API through Jentic.

What authentication does the Fashion Cloud API use?

Fashion Cloud uses an API key in the X-API-Key header, with an initial token exchange via POST /auth/token. Through Jentic the X-API-Key is stored encrypted in the vault and injected at execution time so it does not enter the agent's context.

Can I retrieve product resources with the Fashion Cloud API?

Yes. GET /resources lists the available resources for the account and GET /resources/{id} returns a specific resource by Fashion Cloud identifier. The spec does not expose write endpoints in this version.

What are the rate limits for the Fashion Cloud API?

Fashion Cloud does not publish explicit rate limits in the OpenAPI spec. Treat resource sync as a periodic batch and back off on 429 responses.

How do I sync brand assortments through Jentic?

Install with pip install jentic, search 'list fashion product resources', load GET /resources, then iterate with GET /resources/{id} for each entry. Sign up at https://app.jentic.com/sign-up.

Does the Fashion Cloud API include order or inventory endpoints?

Not in this spec. The current 3-endpoint surface covers authentication and resource retrieval only. For order management or stock updates use the Fashion Cloud portal or contact the vendor for additional endpoints.