/api/catalog-seller-portal/products/{productId}/description

Update Product Description by Product ID

• Content-Type (header, required) — Type of the content being sent.
• Accept (header, required) — HTTP Client Negotiation _Accept_ Header. Indicates the types of responses the client can understand.
• productId (path, required) — Product unique identifier number.

/api/catalog-seller-portal/brands

Get List of Brands

• Content-Type (header, required) — Type of the content being sent.
• Accept (header, required) — HTTP Client Negotiation _Accept_ Header. Indicates the types of responses the client can understand.
• q (query) — Search word.
• from (query) — The first page of the interval of the brand list.
• to (query) — The last page of the interval of the brand list.
• orderBy (query) — The order that the list is displayed. You can select `name`, or `updated_at` to select the order criteria. Then you can add `,` , `asc` or `desc` to define the brands order.
• name (query) — Brand name.

/api/catalog-seller-portal/brands

Create Brand

• Content-Type (header, required) — Type of the content being sent.
• Accept (header, required) — HTTP Client Negotiation _Accept_ Header. Indicates the types of responses the client can understand.

/api/catalog-seller-portal/brands/{brandId}

Get Brand by ID

• Content-Type (header, required) — Type of the content being sent.
• Accept (header, required) — HTTP Client Negotiation _Accept_ Header. Indicates the types of responses the client can understand.
• brandId (path, required) — Brand unique identifier number.

/api/catalog-seller-portal/brands/{brandId}

Update Brand

• Content-Type (header, required) — Type of the content being sent.
• Accept (header, required) — HTTP Client Negotiation _Accept_ Header. Indicates the types of responses the client can understand.
• brandId (path, required) — Brand unique identifier number.

/api/catalog-seller-portal/category-tree

Get Category Tree

• Content-Type (header, required) — Type of the content being sent.
• Accept (header, required) — HTTP Client Negotiation _Accept_ Header. Indicates the types of responses the client can understand.
• depth (query) — Category tree level.

/api/catalog-seller-portal/category-tree

Update Category Tree

• Content-Type (header, required) — Type of the content being sent.
• Accept (header, required) — HTTP Client Negotiation _Accept_ Header. Indicates the types of responses the client can understand.

/api/catalog-seller-portal/category-tree/categories

Create Category

• Content-Type (header, required) — Type of the content being sent.
• Accept (header, required) — HTTP Client Negotiation _Accept_ Header. Indicates the types of responses the client can understand.

/api/catalog-seller-portal/category-tree/categories/{categoryId}

Get Category by ID

• Content-Type (header, required) — Type of the content being sent.
• Accept (header, required) — HTTP Client Negotiation _Accept_ Header. Indicates the types of responses the client can understand.
• categoryId (path, required) — Category unique identifier number.

/api/catalog-seller-portal/products

Create Product

• Content-Type (header, required) — Type of the content being sent.
• Accept (header, required) — HTTP Client Negotiation _Accept_ Header. Indicates the types of responses the client can understand.

/api/catalog-seller-portal/products/{param}

Get Product by external ID, SKU ID, SKU external ID or slug

• Content-Type (header, required) — Type of the content being sent.
• Accept (header, required) — HTTP Client Negotiation _Accept_ Header. Indicates the types of responses the client can understand.
• param (path, required) — This part of the path must follow this format: `{param}={value}`. Replace `{param}` with the name of the parameter used to fetch a product, which can be one of the following: `external-id` (product reference unique identifier number in the store), `sku-id` (SKU unique identifier number), `sku-external-id` (SKU reference unique identifier number in the store) or `slug` (reference of the product in the URL of the store). Replace `{value}` with the value of the selected param. Make sure there is a `=` between them.

/api/catalog-seller-portal/products/{productId}

Get Product by ID

• Content-Type (header, required) — Type of the content being sent.
• Accept (header, required) — HTTP Client Negotiation _Accept_ Header. Indicates the types of responses the client can understand.
• productId (path, required) — Product unique identifier number.

/api/catalog-seller-portal/products/{productId}

Update Product

• Content-Type (header, required) — Type of the content being sent.
• Accept (header, required) — HTTP Client Negotiation _Accept_ Header. Indicates the types of responses the client can understand.
• productId (path, required) — Product unique identifier number.

/api/catalog-seller-portal/products/{productId}/description

Get Product Description by Product ID

• Content-Type (header, required) — Type of the content being sent.
• Accept (header, required) — HTTP Client Negotiation _Accept_ Header. Indicates the types of responses the client can understand.
• productId (path, required) — Product unique identifier number.

/api/catalog-seller-portal/skus/_search

Search for SKU

• Content-Type (header, required) — Type of the content being sent.
• Accept (header, required) — HTTP Client Negotiation _Accept_ Header. Indicates the types of responses the client can understand.
• from (query) — The first page of the interval of the product list.
• to (query) — The last page of the interval of the product list.
• id (query) — SKU unique idenfier number.
• externalid (query) — SKU reference unique identifier number in the store.

/api/catalog-seller-portal/skus/ids

Get List of SKUs

• Content-Type (header, required) — Type of the content being sent.
• Accept (header, required) — HTTP Client Negotiation _Accept_ Header. Indicates the types of responses the client can understand.
• from (query) — The first page of the interval of the product list.
• to (query) — The last page of the interval of the product list.