JOOR Integration

B2B wholesale management for fashion — push products, SKUs, prices and collections to retailers; pull orders, line items, payments, shipments and retailer assortments. Connect JOOR sales events to workflows that help reps respond quickly and keep records current. Start with Watch Orders, then trigger Get Assortment or Get Assortment SKUs when prospects move forward.

Explore Documentation

3-day trialCancel anytimeUp to 10 minutes quick set up

GDPR
Data Encryption
2FA
Local Data Region

Supported triggers and actions for JOOR integration

Triggers can detect changes in JOOR and run actions that can create, search or modify data inside JOOR automatically [3] — exactly how you set them.

Watch OrdersTriggers when an order is created or updated.
Get AssortmentReturns one assortment with extended detail: brand, season, creator and editable users, currency conversions, attribute options, price modifiers, and merchandising hierarchy nodes.
Get Assortment SKUsReturns a cursor-paginated list of SKU rows for a single assortment, including style/color/size, quantities by door, images, swatches, financials (linesheet vs actual currency), and SKU-scoped attribute options.
Get AssortmentsReturns a cursor-paginated list of assortments for the authenticated retailer account, with optional filters (status, brands, created/modified ranges, archived state).
Get CasepacksFetch a list of casepacks — pre-defined size/quantity groupings used when creating or updating SKUs.
Get CategoriesFetch a list of product categories. Category IDs feed the category_ids rows on product create/update modules.
Get CollectionsFetches a list of collections (linesheets), optionally filtered by ID, name, or archived status.
Get ConnectionsRetrieves brand-to-retailer connections.
Get DoorsFetch a list of retailer doors/locations. Door IDs feed the door_id field on order line item rows.
Get Job Batch StatusChecks the progress of an asset upload batch started by Create Product Assets or Create Product Color Assets.
Get Line ItemsFetches a list of order line items (SKUs on an order), including quantities, discounts, and warehouse delivery dates.
Get OrdersFetches a list of orders. Supports JOOR's real page-based pagination (page/page_size/sort_by/sort_order) plus filters by status, export status, approval date, and last-modified date.
Get PaymentsFetch payment information for orders. An order with no payments is not included in the response.
Get Price TypesFetches a list of price types. The price type assigns a currency, wholesale price, and retail price to a SKU — use its ID in Create/Update Prices.
Get PricesFetches a list of prices for your SKUs.
Get ProductsFetches a list of products from your JOOR catalog, optionally filtered by IDs, season, collection, badge, custom tags, price type, currency, division, fabrication, silhouette, country of origin, material, size, or color.
Get SeasonsFetches a list of seasons defined in your JOOR account, for mapping to collections/linesheets.
Get ShipmentsList shipments, with optional filters by external ID, line item, status, carrier, and shipping or delivery date ranges. Includes vendor-side pagination.
Get SKUsFetches a list of SKU data for your products. At least one of Product IDs or SKU IDs must be provided.
Get TraitsFetch a list of product and SKU traits. Trait IDs are base64-encoded strings — pass the id through verbatim wherever a trait is referenced (e.g. product_trait_values rows).
Create CollectionsCreates one or more collections (linesheets) of products in bulk. Returns per-row results in `data`; any per-row failures are reported in `errors` without failing the whole run.
Create Collections by Product External IDCreates one or more collections (linesheets), referencing products by your own system ID instead of the JOOR product ID. Returns per-row results in `data`; any per-row failures are reported in `errors` without failing the whole run.
Create Line ItemsAdds one or more SKU line items to existing orders in a single batch call. If a SKU is already on the order, the requested quantity is added to the existing quantity. Only orders in In Progress, Notes, or Pending status accept new line items.
Create or Update Connections in BulkCreates or updates brand-to-retailer connections in bulk.
Create OrdersCreates one or more order objects in a single batch call. Add line items to a created order with the Create Line Items module.
Create PricesCreates prices for your SKUs.
Create Prices by External IDCreates prices for your SKUs using your system ID.
Create Product AssetsUpload image, swatch, or video assets to products by source URL — JOOR downloads the file itself, no upload required. Runs as an async batch; pass the returned batch_id to Get Job Batch Status to check progress.
Create Product Color AssetsUploads color/swatch assets to a product's SKU trait (e.g. a specific color) by source URL — JOOR downloads the file itself, no upload required. Runs as an async batch; pass the returned batch_id to Get Job Batch Status to check progress.
Create ProductsCreates one or more products in your JOOR catalog in a single batch request, including categories, trait values, custom tags, and badge.
Create SeasonsCreates one or more seasons in bulk. Returns per-row results in `data`; any per-row failures are reported in `errors` without failing the whole run.
Create ShipmentsCreate one or more shipment records (does not replace existing shipments for the order). The Shipping API is a paid add-on — confirm it is enabled on your JOOR account before running this module.
Create SKUsCreates SKUs for your products.
Delete Line ItemsDeletes one or more SKU line items from existing orders in a single batch call — all units of the line item are removed. This cannot be undone.
Delete Price TypesDeletes your price types. A price type tied to any order that is not yet Approved or Canceled cannot be deleted.
Delete Product AssetsRemoves one or more assets from products in a single batch call.
Delete Product Color AssetsRemoves one or more color/swatch assets from a SKU trait in a single batch call.
Delete ProductsPermanently deletes one or more products from your JOOR catalog in a single batch request. This cannot be undone.
Delete ShipmentsDelete one or more shipment records by ID or External ID. The Shipping API is a paid add-on — confirm it is enabled on your JOOR account before running this module.
Make an API CallPerforms an arbitrary authorized API request to the JOOR API.
Update CollectionsUpdates one or more existing collections (linesheets) in bulk. Returns per-row results in `data`; any per-row failures are reported in `errors` without failing the whole run.
Update Collections by Product External IDUpdates one or more existing collections (linesheets), referencing products by your own system ID instead of the JOOR product ID. Returns per-row results in `data`; any per-row failures are reported in `errors` without failing the whole run.
Update Line ItemsUpdates one or more existing SKU line items in a single batch call — for example, to change quantities, cancel a line item, or apply a discount. Only line items on orders in In Progress, Notes, or Pending status can be updated.
Update OrdersUpdates one or more existing orders in a single batch call — for example, to change an order's status.
Update PricesUpdates prices for your SKUs.
Update ProductsUpdates one or more existing products in your JOOR catalog in a single batch request, identified by JOOR product ID or External ID.
Update Products by External IDUpdates one or more existing products in your JOOR catalog in a single batch request, identified by your own system's External ID.
Update SeasonsUpdates one or more existing seasons in bulk. Returns per-row results in `data`; any per-row failures are reported in `errors` without failing the whole run.
Update ShipmentsPartially update shipments. Only provided fields are updated. The Shipping API is a paid add-on — confirm it is enabled on your JOOR account before running this module.
Update SKUsUpdates SKUs for your products.
Update SKUs by External IDUpdates SKUs for your products using your system ID.
Upsert Collections VisibilitySets retailer visibility settings for one or more collections in bulk. Returns per-row results in `data`; any per-row failures are reported in `errors` without failing the whole run.
Upsert Price TypesUpdates your existing price types or inserts new price types.

How to integrate JOOR in automation workflow?

3 simple steps to make your JOOR connected with other apps in automation workflows on WEXTL. Up to 10 minutes integration set up.

STEP 1

Select JOOR in workflow

Pick JOOR app in the workflow builder [4] - just one click to select the app.

STEP 2

Connect JOOR

When prompted, authorize access to JOOR in WEXTL once. JOOR credentials are encrypted and never shared with WEXTL. Authorization will be reused in any future API calls [3].

WEXTL wants to integrate with your JOOR account. Approve?

STEP 3

Build a workflow

Build your workflow with JOOR yourself or with WEXTL® AI Builder. Connect JOOR to any available integrations [5], or use HTTP node to go beyond them.

JOOR

How JOOR connects and integrates with WEXTL

Save and approve your credentials once — WEXTL® stores authorization information encrypted and reuses the authentication whenever JOOR app is called in workflows. That allows your sales automations to run without your attention, per defined schedule [7]. Explore documentation [6] for a detailed list of fields that JOOR supports.

Full JOOR API documentation

The following table illustrates what fields JOOR integration require during authorization flow inside our workflow builder [4].

Demonstration of JOOR connection step inside WEXTL Workflow Builder [4].

Field	Type	Help
EnvironmentRequired	select	JOOR issues separate credentials per environment — sandbox tokens do not work in production.
Client IDRequired	password	Issued by JOOR.
Client SecretRequired	password	Issued by JOOR.
API UsernameRequired	text	Typically the API user email provided by JOOR during onboarding.
API PasswordRequired	password	Set during onboarding.
Account IDRequired	text	Your Account ID — sent as the `account` parameter on every request.

Connect JOOR to popular apps on WEXTL

Enter a name of the other app you want to sync with JOOR below. Click on selected app to explore integration options with JOOR. If the app you search for is not available in WEXTL yet, you can use HTTP node [10] instead to integrate it directly.

Example automation with JOOR integration

Select Watch Orders trigger from JOOR - this will be a starting point in your automation. Whenever event happens in JOOR, workflow will start [7] from Watch Orders node.

Search for Create Collections, connect it as the next step of integration sequence. You can use filters between Watch Orders and Create Collections, so only important data pass from Watch Orders to the next step. WEXTL gives you full control over the process of JOOR automation. All parts of workflow are visible on the canvas [4].

JOOR on WEXTL has 53 modules for combining sales automations. Explore JOOR documentation for more.

JOOR

Watch Orders

Loopio

Performs action

Loopio

Triggers

JOOR

Create Collections

Demonstration of how visual JOOR automation [6] looks in WEXTL.

Frequently asked questions

Common questions about automating JOOR in your workflows.

JOOR has 1 trigger, including "Watch Orders". Triggers are start points of the workflow, and automations may start from them.

Integration has 52 actions, including "Get Assortment", "Get Assortment SKUs", and "Get Assortments", and more. Refer to our JOOR Documentation for detailed inputs and outputs.

No. Most automations are built visually on the canvas by picking triggers, actions, and mapping fields. You can add custom JavaScript with Functions when advanced logic is needed — but our customers do that in rare cases [4].

Yes. Connections are authenticated per account, credentials are encrypted at rest, and you can enforce approvals and team-level access controls on any automation.

The JOOR integration on WEXTL runs directly on its vendor public API — every field name, authentication method, and rate limit is controlled by JOOR official API and covered in documentation [3]. WEXTL handles the request signing and pagination for you.

Absolutely. Where JOOR provides native webhooks, you can use instant triggers to eliminate polling delay. For custom webhooks, WEXTL offers Custom Webhook node, so you can start automation whenever JOOR or any other service sends event to webhook URL.

WEXTL is an AI-first visual canvas. The platform allows you to describe automation in plain text — and AI will wire nodes for JOOR inside the workflow builder [4]. You can also use built-in workflow nodes (AI Agent, Human in the Loop, Condition, Aggregate Results) in pair with JOOR modules to craft complex integration flows with branches, filtering, and conditional logic. There are absolutely no limits of what you can build.

References

List of sources used to gather information about the JOOR integration.

JOOR integration source code, module specs and credentials implementation.
Internal JOOR integration documentation, structured input and output parameters, scopes, and authentication methods.
Official JOOR vendor API documentation — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
WEXTL® Visual Workflow Builder, anonymized data from our technical support team.
WEXTL® Apps Library
WEXTL® JOOR App Documentation
WEXTL® Workflow Scheduler
WEXTL® HTTP node documentation

JOOR Integration

Supported triggers and actions for JOOR integration