End-to-end workflow · Guides
Product catalog and cards
Product search, full card retrieval, model creation, brand and category dictionaries, and marketplace parameters.
A SelSup card is hierarchical — model, color variants, and final products or sizes. Reliable synchronization stores identifiers for every level.
PIM, ERP, and catalog integrations01
Find a product and load the full card
Product search returns a lightweight list representation. Store productId, skuId, viewId, and modelId separately because they identify different entities.
Load the model by modelId for the complete card. When dynamic parameter values are required, enable the corresponding query option documented for the model endpoint.
- 1
Search page by page
Use stable ID sorting and avoid count on every page.
- 2
Read the model identifier
Obtain modelId or view.model.id from the search result, depending on the response representation.
- 3
Load the complete model
The model contains variants and sizes needed for editing the card.
Related API endpoints
GET/api/product/findSearch productsGET/api/model/{modelId}Load the complete model
02
Create a minimal card
A model still needs one variant and one final product even when the business does not use colors or sizes.
Find or create the brand and category first. Persist their identifiers in your system so repeated imports do not create duplicates.
Use the model article as a stable external key. SelSup can generate missing barcodes, but explicit barcode mapping is safer for two-way synchronization.
Shared models contain service fields. Send only the fields listed in the current endpoint request body.
{
"article": "MODEL-001",
"title": "Basic T-shirt",
"brandId": 8124,
"categoryId": 27640,
"organizationId": 1,
"views": [
{
"color": "Black",
"sizes": [
{
"name": "Basic T-shirt, M",
"size": "M"
}
]
}
]
}
03
Update without losing data
Use PATCH for a partial final-product change when the endpoint supports merging. Treat model PUT as replacement of the editable structure.
Before PUT, load the latest model, change the required fields in your copy, and send the reconciled structure. Do not reuse an old response when the card may have changed in the UI.
When no entity version or ETag is available, minimize the read-to-write window and perform a verification read after saving.
04
Parameters and allowed values
Parameter values may live at category, model, variant, or product level. A more specific level normally wins, while marketplace rules determine what can actually be sent.
For multiValueAllowed, send multiple values with the same paramId. Select the value shape from valueType, and resolve an allowed option first when displayType is SUGGEST.
Marketplace categories and parameters change. Refresh them regularly and never use the display name as a permanent key.
GET https://params.selsup.ru/knowledge/getParams?ozonCategoryId=91025609
GET https://options.selsup.ru/option/fetchOption?paramId=60019&query=cotton&limit=10