JOOR API
JOOR is an end-to-end wholesale platform connecting fashion brands and retailers across discovery, digital linesheets, order management, and embedded payments—spanning 14,000+ brands and 700,000+ buyers. An unofficial API lets you programmatically pull orders, styles, SKUs, prices, retailers, seasons, and doors—and push updates like new orders, price types, and product syncs back into JOOR.
What is JOOR?
JOOR is an end-to-end wholesale platform that connects fashion brands and retailers to manage B2B ecommerce from discovery through payment. Brands use JOOR to run virtual showrooms, digital linesheets, and order management and to collect payments via JOOR Pay; retailers use it to discover brands, plan assortments, place orders, and attend digital trade shows through JOOR Passport. The network spans 14,000+ brands across 53 categories and 700,000+ global buyers, with over $100B in wholesale volume transacted on the platform.
Core product areas include:
- JOOR Discover and the retailer network (brand sourcing and connection)
- Virtual Showrooms and Digital Linesheets
- B2B Order Management with bidirectional order sync
- JOOR Pay (embedded wholesale payments)
- JOOR Passport (digital trade show portal) and Visual Assortment Planning
- Reporting & Analytics and the Product Sync App for Shopify, plus 100+ pre-built ERP & PLM integrations
Common data entities:
- Styles/Products, Categories, Images, Collections, Seasons
- SKUs (style + size + color), Prices, Price Types, Casepacks
- Orders, Payments, Doors, Connections
- Brands, Retailers/Buyers, and network discovery records
The JOOR Integration Challenge
Brands and retailers run mission-critical wholesale workflows on JOOR daily, but turning its portal-driven, dual-version surface into reliable API-driven automation is non-trivial:
- Dual API generations: v2 supports stable style-level pricing and read-only orders, while v4 adds SKU-level pricing and bidirectional order sync—integrations must reconcile both object models
- Brand API access gates: programmatic access is provisioned per brand account, so credentials and entitlements differ across tenants and partner relationships
- Two-sided data model: orders span a selling brand and a buying retailer, so style, SKU, door, and price-type records must stay aligned across both sides of a connection
- Pricing complexity: prices apply at the style level by default but can drop to SKU level, with price types and casepacks layered on per season and connection
- Rate limits and throttling: the documented endpoints enforce throttling, so high-volume catalog and order syncs need careful backoff and pagination
- Seasonal cadence: linesheets, collections, and assortments turn over each market and season, so catalog and order endpoints shift in shape and volume throughout the year
How Supergood Creates JOOR APIs
Supergood reverse-engineers authenticated JOOR sessions alongside the documented v2 and v4 Brand API surfaces to deliver a resilient, normalized API layer for your JOOR account—across catalog, orders, pricing, and payments.
- Handles JOOR's unified authentication securely, with a single configuration spanning v2 and v4 endpoints
- Maintains session continuity with automated refresh and change detection across markets and seasons
- Normalizes responses across styles, SKUs, prices, orders, and doors so you integrate once and reconcile v2 and v4 object models consistently
- Respects documented rate limits with adaptive throttling, pagination, and backoff tuned to your account
Use JOOR with AI agents: JOOR MCP Server →
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your JOOR account, API version (v2/v4), and the catalog, order, and pricing entities you need.
- Supergood Generates and Validates Your API
We deliver a production-ready JOOR adapter tailored to your account, entitlements, and seasonal cadence.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as JOOR's v2/v4 endpoints evolve.
API Endpoints
Authentication
/authenticateAuthenticate to a JOOR Brand account using the unified credential configuration and obtain a session token compatible with v2 and v4 endpoints.
Catalog
/stylesList styles/products with categories, images, collections, and season filters across the brand catalog.
Catalog
/skusRetrieve SKUs (style + size + color) with associated prices, price types, and casepacks for SKU-level pricing workflows.
Orders
/ordersRead orders across connections with status, season, door, and retailer filters.
Orders
/create_orderCreate or update an order using v4 bidirectional order synchronization against a brand-retailer connection.
Pricing
/pricesPull style- and SKU-level prices, price types, and casepacks by season and connection.
Use Cases
Sync the wholesale catalog into commerce and PLM systems
- Pull styles, images, categories, collections, and seasons into a single product catalog - Expand to SKU-level data with sizes, colors, prices, and casepacks for downstream merchandising - Keep linesheet and assortment changes in sync each market and season
Automate wholesale order management
- Read orders across all retailer connections into ERP and OMS systems - Push new and updated orders back to JOOR with v4 bidirectional sync - Reconcile order line items against doors, seasons, and price types
Centralize pricing and payments reporting
- Sync style- and SKU-level prices, price types, and casepacks into pricing tools - Surface JOOR Pay payment activity alongside orders for AR reconciliation - Flag pricing or casepack mismatches across connections before market
Power brand and retailer network analytics
- Pull connection, door, and retailer records to map the brand's wholesale network - Combine order and catalog data for sell-in and assortment reporting - Feed normalized JOOR data to BI dashboards and AI agents
Technical Specifications
Authentication
JOOR unified credential configuration handled in a managed session, compatible across v2 and v4 endpoints
Connectivity
Documented v2 and v4 Brand API (OpenAPI-described REST) plus authenticated session flows where needed
Response format
Normalized JSON across styles, SKUs, prices, orders, doors, and payments
Rate limits
Adaptive throttling and pagination tuned to JOOR's documented rate limits to avoid account-side throttling
Session management
Automatic session refresh and credential rotation across the unified v2/v4 configuration
Data freshness
Near real-time pulls for orders and catalog with optional scheduled batch syncs by season
Security
Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging
Webhooks
Event-style callbacks for order creation, order updates, and catalog/price changes
Latency
Sub-second reads on cached catalog entities; multi-second writes when posting orders via v4 sync
Throughput
Horizontally scaled workers sized to seasonal catalog and order volume across many retailer connections
Reliability
Retry, backoff, and idempotency keys for order writes and price updates
Adaptation
Continuous monitoring of JOOR v2/v4 endpoint changes, pricing model shifts, and seasonal catalog turnover
Frequently asked questions
Yes. Supergood works against JOOR's unified authentication, which is compatible across v2 and v4, and normalizes both object models—so you get stable style-level pricing and read-only orders from v2 plus SKU-level pricing and bidirectional order sync from v4 through one consistent surface.
Both. v2 exposes read-only orders, while v4 adds bidirectional order synchronization. Supergood lets you read orders across all connections and push new and updated orders back into JOOR through the v4 surface.
Prices apply at the style level by default and can drop to SKU level when needed. Supergood preserves prices, price types, and casepacks at both levels so style and SKU pricing stay accurate across seasons and connections.
No. Supergood works with your existing JOOR Brand account credentials and entitlements. We operate against the same authenticated and documented API surfaces your account already has access to.
JOOR documents rate limits and throttling on its endpoints. Supergood applies adaptive throttling, pagination, and backoff tuned to your account so high-volume catalog and order syncs run reliably without tripping account-side limits.