canonical: https://jentic.com/apis/fashioncloud.com/fashioncloud

# Fashion Cloud API

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. The current spec exposes an authentication exchange and resource read endpoints, intended for integrations that need to pull catalogue resources by identifier. Authentication is performed against `/auth/token` and subsequent calls use the issued credentials in the X-API-Key header.

## For AI agents

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

## Scope

Does not handle order placement, payments, or inventory updates - use for B2B fashion product resource retrieval only.

## Capabilities

- 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}`
- Feed downstream PIM and ERP systems with Fashion Cloud product data on a scheduled pull
- Sync brand assortments into retailer storefronts without manual file transfers

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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

| 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 |

## Key resources

- **Authentication** — Exchange API credentials for an access token via `/auth/token`
- **Resources** — List and retrieve B2B fashion product resources by id

## Why Jentic

- **Setup:** Wiring the Fashion Cloud API by hand means exchanging credentials for a token at `/auth/token`, then setting the X-API-Key header on every product-resource call yourself. Through Jentic you install once, import Fashion Cloud from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Fashion Cloud puts the resource id in the URL path (`/resources/{id}`), so a rule can pin your agent to one product resource. You choose the operations it may call, and the resource reads here are lookups that make no changes to inventory or orders.
- **Credential handling:** Your Fashion Cloud X-API-Key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as '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.

## Related APIs

- **Shopify** — Push Fashion Cloud product resources into a Shopify storefront catalogue
- **Cloudinary Upload** — Process and host Fashion Cloud product imagery at scale
- **Airtable** — Generic catalogue store used when no fashion B2B platform is in place

## FAQ

### 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. Get started with Jentic One, the self-hosted execution layer.

### 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.

### Can I limit what my agent is allowed to do with the Fashion Cloud API?

Yes. Because you run Jentic One yourself, your own rules decide which Fashion Cloud operations the agent may call, so you can allow it to list resources with GET /resources and read one with GET `/resources/{id}` while blocking anything else. Since the resource id sits in the URL path, a rule can pin the agent to a single product resource. These operations are read-only lookups, so a scoped agent cannot change inventory or place orders. Your X-API-Key stays with your instance and is added at execution time rather than handed to the agent.