Overview

Use this page to understand how JOOR's v2 and v4 APIs work together across wholesale workflows.

JOOR provides two complementary API versions: v2 and v4. Both versions are stable, maintained, and available through the version selector at the top right of the documentation.

These APIs are used to manage wholesale workflows for fashion, including collections, styles, orders, and related operations.

Understand the pricing model

A style (also called a product) is the default level at which pricing is applied.
A SKU is a specific combination of style + size + color.

In most cases, pricing is set at the style level. In some cases, a specific SKU needs its own price because that size and color combination is more expensive or more exclusive than the rest of the style.

Choose between v2 and v4

v2 is the legacy API family and continues to support stable style-level pricing workflows.
v4 extends v2 rather than replacing it. Use v4 when you need SKU-level pricing or 2-way sync orders.

The following table shows which API version supports each feature:

Feature	v2	v4
Styles / products	✅	✅
Categories	✅	✅
Images / assets	✅	✅
Connections	✅	❌
Orders	✅ *readonly	✅
Inventory	✅	❌
Prices	❌	✅
SKUs	❌	✅
Collections	❌	✅
Seasons	❌	✅
Doors	❌	✅
Price types	❌	✅
Casepacks	❌	✅
Payments	❌	✅

Authentication across both versions

The v4 authentication setup is also compatible with v2 endpoints. You can use a single authentication configuration and still call endpoints from either version, giving you the flexibility to combine v2 and v4 endpoint families in the same integration.