Article Hierarchy**

POST

/master/article_hierarchy/

master

Captures the article hierarchy at the outlet level. You can have 10 levels on your hierarchy.
For e.g. 1 can be department, 2 can be category, 3 can be subcategory, 4 can be brand. Use -1 if not used.

Request

Header Params

X-SYNC-TOKEN

string

required

<sync_token>

Accept-Encoding

string

required

gzip (mandatory)

Body Params application/json

array of:

article_id

string

required

article_name

string

required

store_id

string

required

hierarchy_level_1

string

required

The details of the hierarchy is taken from the hierarchy_headers and hierarchy_details models.
Appropriate values from the hierarchy details should be used to indicate which hierarchy is used.
All these 10 levels are mandatory. If the hierarchy_level_ is not utilised, use -1 as the value.

hierarchy_level_2

string

required

hierarchy_level_3

string

required

hierarchy_level_4

string

required

hierarchy_level_5

string

required

hierarchy_level_6

string

required

hierarchy_level_7

string

required

hierarchy_level_8

string

required

hierarchy_level_9

string

required

hierarchy_level_10

string

required

Example

Request samples

Shell

JavaScript

Java

Swift

PHP

Python

HTTP

Objective-C

Ruby

OCaml

Dart

curl --location --request POST 'https://test.your-api-server.com/master/article_hierarchy/' \
--header 'X-SYNC-TOKEN;' \
--header 'Accept-Encoding;' \
--header 'Content-Type: application/json' \
--data-raw ''

Responses

🟢200OK

application/json

Successful Sync

Body

status

string

optional

message

string

optional

Example

{
  "status": "string",
  "message": "string"
}

🟠400Bad Request

🟠403Forbidden

🟠405405

Modified at 2025-02-10 12:39:04

Hierarchy Details**

Article Attributes