List products

The seller's id on the marketplace. Usually paired with marketplace — on its own it isn't guaranteed unique across marketplaces.

The seller's or brand's own internal SKU for this listing (not our external_id). Deliberately not required to pair with seller_id — the real brand use case is usually "find my SKU wherever it's being resold," not "only under one specific reseller."

Substring match against seller_code, for when a seller adds their own prefix/suffix around your internal SKU (e.g. vendor SKU 34100001, listed as 34100001/0958) — pass just the part you know. Unlike seller_code, this is not a precise identity lookup: a short value can match multiple unrelated codes, so pair it with seller_id/marketplace when you can.

The marketplace's own SKU (WB nmId, Ozon sku, etc.). Only unique paired with marketplace — pass both.

A product page URL. Query string and fragment (?utm_source=..., #reviews, etc.) are stripped automatically before matching — paste it exactly as copied from a browser.

Containment match against category_path (any level of the hierarchy, not just the leaf). See GET /categories for the available values. Matches against any of a product's known-language translations, not just the one returned as its default category_path in the response.

Exact brand name match, case-insensitive — not a substring search like name_contains. Brand casing varies across marketplaces/submissions as scraping noise, not a meaningful distinction, so the match ignores it. See GET /brands for the available values.

Case-insensitive substring match against the product name (no stemming or morphological matching). Matches against any of a product's known-language translations, not just the one returned as its default name in the response — a product can match here even if the term doesn't appear in the name you see on the result.

Filter by trust status. When omitted, products of every status are returned — the API deliberately never withholds unverified/flagged rows; the caller decides what to trust.

Invalid or missing values are silently clamped to the default rather than rejected with a 400.

500 max — deliberately generous relative to a typical UI-facing API, sized for bulk pulls.