Category Overview

Quick Reference

Endpoint Summary

This table provides quick access to the category query service under the Category section. Detailed request and response fields are included under the relevant section.

NoServiceEndpoint
1Category QueryPOST /api/v1/query/categories
General Usage

General Technical Information

Authentication

For the Category query endpoint on this page, authentication information is sent in the request body. ClientId and AppKey fields are required.

Category Scope

This section is prepared to query the category records used to classify products hierarchically within the catalog. The endpoint does not create or update data; it lists existing category definitions.

Category Hierarchy

The category tree is interpreted through the ParentId and, if available, Children fields. For root categories, ParentId can be empty or null.

Leaf Category

The IsLeaf field indicates whether the category is a final-level category. This field can be critical in product assignment and category-based filtering scenarios.

Response Structure

Records are returned in the Result field, while the total record count is returned in the TotalCount field.

Category is the catalog structure that enables products to be classified under logical groups according to their common characteristics. A properly structured category setup is a key reference data source for product listing, filtering, search, and user navigation.

Category information can be used to display products in the correct catalog position, enable category-based filters, and manage business rules such as campaigns or commissions through product groups.

1. Category Query — POST /api/v1/query/categories

This endpoint is used to retrieve the data shown in the Categories list and category tree structure in the PIM UI through the API.

Technical Note
  • GetCategories is used to query category records centrally defined in PIM.
  • CategoryIds parameter can be used to query specific category records by ID.
  • Names, IncludesNames, and ExcludesNames parameters are used in filtering scenarios by category name.
  • Codes and IntegrationCodes fields can be used as references when matching categories with external systems.
  • IncludeFullNames field enables the full path information of the category hierarchy to be returned in the response.
  • DimensionId can be used to interpret the dimension or classification structure to which the category belongs.

Usage Notes for Category Data

  • The category structure is the main reference data for listing products under the correct catalog breakdown.
  • The category hierarchy can be used to create menus, breadcrumbs, and category filters on the marketplace or storefront side.
  • In product assignment processes, the IsLeaf field should be checked for final-level categories.
  • In multi-system integrations, it is recommended to use Code or IntegrationCode instead of only the category name when matching categories.
  • The Status field can be used to interpret the active/passive status of the category record.

Endpoint-Specific Query Parameters

API Parameter Type PIM UI Equivalent / Meaning Description
CategoryIdsarray (integer)Category System ID ListUsed to filter specific categories by ID.
Namesarray (string)Category Name FilterExact-match filter by category name.
IncludesNamesarray (string)Category Names ContainingReturns category names that contain the specified texts.
ExcludesNamesarray (string)Excluded Category NamesExcludes categories that contain the specified texts.
Codesarray (string)Category Code FilterFilters by the Code field of the category.
IntegrationCodesarray (string)Integration Code FilterFilters by the integration code of the category.
DimensionIdsarray (integer)Dimension ID FilterFilters by specific dimension definitions.
IncludeFullNamesbooleanInclude Full Path NameWhen set to true, returns the full path name of the category hierarchy, such as Clothing > Tops > T-Shirt.

API Response Parameters and UI Equivalents

Each Category object in the Result array contains the following fields:

API Response Field Type PIM UI Equivalent / Field Name Description
CategoryIdintegerCategory System IDUnique category number assigned by the system.
ParentIdinteger?Parent Category IDID of the parent category in the hierarchy. null is returned for root categories.
NamestringCategory NameName displayed in the category tree and list in the UI.
CodestringCategory CodeUnique code of the category.
IntegrationCodestringIntegration CodeExternal system matching code.
ShortDescriptionstringShort DescriptionShort description in the category detail.
LongDescriptionstringLong DescriptionLong description in the category detail.
SortOrderintegerSort OrderDisplay order in the category tree in the UI.
IsLeafbooleanIs Leaf Category?true means it is the final node/category with no child categories.
DimensionIdintegerDimension IDDimension definition to which the category belongs.
ChildrenarrayChild CategoriesList of child categories under the category.
ProductsarrayProducts in the CategoryList of products linked to the category.
PicturesarrayCategory ImagesImages assigned to the category.
PropertiesarrayCategory PropertiesCustom fields defined for the category.
FiltersarrayCategory FiltersFilter configurations defined for the category.
TagsarrayCategory TagsTags assigned to the category.
TranslationsarrayMultilingual ValuesTranslations of the category name and descriptions.
StatusintegerStatus1 = Active, -1 = Passive.
CreateddatetimeCreation DateDate when the category was added to the system.
Updateddatetime?Update DateLast update date.

Usage Guide in the UI

  • Category Tree: The hierarchical category tree you see in the left panel of the UI is created using the ParentId and Children fields. Categories with ParentId = null are root nodes.
  • Full Path Name: By sending IncludeFullNames = true, you can retrieve the full category path in the Clothing > Tops > T-Shirt format displayed in the product list in the UI.
  • Leaf Category: Products are generally assigned only to leaf categories (IsLeaf = true).

Error Management

Common Error Cases

The table below is prepared for the common error cases that may apply to the endpoint under the Category section. When endpoint-specific error messages are finalized, they can be added to the Error Message column.

HTTP StatusStatusError Message
400Bad Request
401Unauthorized
403Forbidden
404Not Found
422Unprocessable Entity
429Too Many Requests
500Internal Server Error