Bulk Export (Seeding)

This is the same products endpoint documented in Products & Prices, called with detail=full. It is how you build your initial copy of the catalog.

Bulk export

GET /v4/retailers/collections/{collection_id}/products?detail=full

The same endpoint as summary products, with detail=full. Each product comes back in exactly the same shape as GET /v4/retailers/products/{id}, so one parser serves both paths.


Page size	25 maximum, and 25 is also the default at this depth. Asking for more returns `400`
Shape	Identical to single product full detail
Scoping	The collection in the path is applied, exactly as `collection_id` is on the single product endpoint
Round trips	About 25 times fewer than pulling product by product

This is how you seed. For a 139,000 product catalog: roughly 5,600 bulk pages, against roughly 139,000 individual requests. At the default credit budget that is the difference between about an hour and a half and about two days.

curl -G https://api.jooraccess.com/v4/retailers/collections/1146216/products \
  -H "Authorization: Bearer $TOKEN" \
  -d account=40975 \
  -d detail=full \
  -d limit=25

The collection in the path scopes the detail. There is no collection_id query parameter to pass here, and none is needed: the endpoint passes the collection from the path down to the detail fetch, so every product comes back scoped exactly as GET /v4/retailers/products/{id}?collection_id={id} returns it. That collection's color exclusions and its per collection SKU delivery windows are applied. A seed built from the bulk export is correctly scoped, and you do not need to follow it with per product reads to fix the scoping up.

Not yet contractual. Treat the shape documented here as provisional; report anything that deviates from it.