List categories
marketplace is required — category taxonomies differ per site, so an unscoped list would mix unrelated hierarchies together.
This endpoint doesn't count against your daily data quota — only the per-minute rate limit. It's a lookup endpoint for navigation, not a data export, so it can never return quota_exceeded.
Authorization
bearerAuth Bearer token — see API Overview for how to get one and use it.
In: header
Query Parameters
Value in
- "ozon"
- "wildberries"
- "yandex_market"
- "lamoda"
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/categories?marketplace=wildberries"{ "data": [ { "category_path": [], "product_count": 11197 }, { "category_path": [ "Зоотовары", "Фермерство" ], "product_count": 455 }, { "category_path": [ "Обувь", "Мужская", "Кеды и кроссовки" ], "product_count": 37 } ]}List brands GET
`marketplace` is optional here, unlike `GET /categories` — a brand is the same real-world entity across marketplaces, so an unscoped list (a brand's total footprint across every site) is meaningful, unlike an unscoped category list, which would mix unrelated per-site taxonomies together. This endpoint doesn't count against your daily data quota — only the per-minute rate limit. It's a lookup endpoint for navigation, not a data export, so it can never return `quota_exceeded`.
Get a product by ID GET
`id` is our own internal identifier (a UUID), not a marketplace SKU. The only way to obtain it is via `GET /products` (by `url`, `external_id`+`marketplace`, or `seller_code`) — nothing external ever knows it up front.