GENERAL INFORMATION
Use this endpoint to create merchandise category levels. If you would have a hierarchal structure which goes 3 levels deep, this endpoint is used to create only the levels. The merchandise categories are linked to the levels. If you do not have a hierarchical structure you can just send 1 level hardcoded and put the id of this level on all the POST /MerchandiseCategories. Direct link to Swagger documentation:
https://public-api-dev.wair.cloud/swagger/index.html#/Items/post_api_v1_MerchandiseCategoryLevels
REQUEST
Authentication
Bearer token, information on page POST /Token
Headers
Name | Description | Example |
|---|---|---|
X-Tenant | Tenant code supplied by Wair | “TENANT” |
QueryParameters:
Name | Description | Example |
|---|---|---|
fullLoad | See documentation: Integration core principles | true |
Body example:
{
"merchandiseCategoryLevels": [
{
"merchandiseCategoryLevelId": "guid01",
"code": "LEVEL01",
"description": "Level 1"
},
{
"merchandiseCategoryLevelId": "guid02",
"code": "LEVEL02",
"description": "Level 2"
}
]
}Additional information:
merchandiseCategoryLevelId and code = Use of "id" and "code"archived
description = description of the merchandise category level.
RESPONSE
StatusCodes:
200 = OK
401 = Unauthorized, which means an expired/missing/invalid token
400 = Bad request, see body of the response to check which validation errors have occured
500 = System error, see body of the response to check which error has occured or contact integration support
Body Example:
No body in the response.