Menu//
- Modify the available and unavailable status(in batch)
Query ShopCategory list
Create a ShopCategory
Modify a ShopCategory
Delete ShopCategories(in batch)
Adjust order of a ShopCategory
Adjust order of ShopCategories(in batch)
Query category attribute list
Query products list
Query a specific product
Create products(in batch)
Modify products(in batch)
Query conflict ChoiceGroup before unavailable (in batch)
Delete products(in batch)
Adjust order of a product(in a specific ShopCategory)
Adjust products order in a ShopCategory(in batch)
Adjust products order in a Shop(in batch)
Batch bind Spus picture(support other image urls)
Query ChoiceGroup list
Create ChoiceGroups(in batch)
Modify ChoiceGroups(in batch)
Batch query which products are using these ChoiceGroups
Delete ChoiceGroups(in batch)
Modify ChoiceGroupSkus available/unavailable status(in batch)
Modify the available and...
- Product data that can be transmitted in one batch should not exceed 200. If there are more products, please create them in batches.
- The interface supports partial synchronization success and partial synchronization failure. However, if there is a parameter format error, all will fail.
- If there is no available product in a ShopCategory, the ShopCategory will disapear at user APP.
- If needLinkage=1, this API will also modify the status linked to the ChoiceGroupSkus (the same name with Spu). But if the ChoiceGroupSku status violates the rule of ChoiceGroup, it wouldn't be modified.
Rate limit: 10 QPS by appId dimension.
POST
curl -i -X POST \
https://open.mykeeta.com/api/open/product/spustatus/batchupdate \
-H 'Content-Type: application/json' \
-d '{
"shopId": 25381,
"spuIdList": [
1,
2,
3
],
"status": 1,
"needLinkage": 1
}'Batch status update result.
A numeric status identifier indicating the result of the interface call, used to determine whether the operation executed successfully.
| Enum Value | Description |
|---|---|
| 0 | The request was executed successfully. |
| Non-zero value | The request execution failed. Specific error details can be viewed in the message field. |
Example:0
Text description corresponding to the status code, explaining the operation result or error cause to users.
Example:"Success"
Response
{ "code": 0, "message": "Success", "data": [ { … } ], "errorList": [ { … } ] }