Categories
Categories are used in order to organize your product catalogue within your e-commerce platform. They work as hierarchical levels of product classification. There are no limits to the number of levels of categories, though it is recommended not to use too many levels. One product can belong to only one category. The same applies to categories, a category can have only one parent category.
Category Lookup keysβ
| Key | Type | Description |
|---|---|---|
id | integer | Propeller category id, auto-generated |
sourceId | string | External system unique id. sourceId should be combined with source |
Fieldsβ
| Name | Description | Type |
|---|---|---|
names | Category name | array[LocalizedString] |
descriptions | Category description | array[LocalizedString] |
shortDescriptions | Category short description | array[LocalizedString] |
language | Category default language. | string ISO 639-1 |
parent | Parent category. | JSON object that identifies the parent. id or sourceId in combination with source |
sourceId | External system unique id | string |
source | External system | string |
metadataTitles | Metadata title | array[LocalizedString] |
metadataDescriptions | Metadata description | array[LocalizedString] |
metadataKeywords | Metadata keywords | array[LocalizedString] |
metadataCanonicalUrls | Metadata canonical URL | array[LocalizedString] |
hidden | Controls category visibility | enum Y = Yes N = No |
Category Errorsβ
This section describes error codes specific for the Category resource.
| Code | Error Type | Status Code | Message | Reason |
|---|---|---|---|---|
30004 | CategoryExists | 400 | Category already exists | Category with such lookup key already exists |
30005 | CategoryMultipleFound | 400 | Multuple categories found. Please provide additional filters | Multiple categories with such lookup key exist |
30006 | CategoryNotFound | 404 | Category does not exist | Category with such lookup key not found |
30007 | ParentCategoryNotFound | 404 | Parent category not found | Parent category with such lookup key not found. This error is typical when working with category sub-resources (e.g. attributes) |
ποΈ Introduction
The Propeller REST API is based on resource-oriented URL's, returns JSON-encoded responses and uses standard HTTP response codes, authentication and HTTP methods. The main goal of the REST API is efficiently importing/exporting large amounts of data in/out of the Propeller platform.
ποΈ Add Setting to Cluster Config
Use this endpoint to add additional settings to a cluster config. If a cluster config setting is successfully created, the response will include the `id`.
ποΈ attribute-descriptions
7 items
ποΈ attributes
5 items
ποΈ authentication
2 items
ποΈ Authentication
Authentication
ποΈ Bulk Categories by Id
The bulk endpoints offer an efficient way of importing/updating large amounts of categories with just a single API call. When using the bulk `id` endpoint, the categories are identified by Propeller category `id`. If a category with such `id` doesn't already exist, it will be created. If it does exist, the category will be updated.
ποΈ Bulk Categories by sourceId
The bulk endpoints offer an efficient way of importing/updating large amounts of categories with just a single API call. When using the bulk `sourceId` endpoint, the categories are identified by `sourceId`, `source`. If a category doesn't already exist, it will be created. If it does exist, the category will be updated.
ποΈ Bulk Cluster Options by lookupKey
The bulk endpoints offer an efficient way of importing/updating large amounts of cluster options with just a single API call. The same lookup key is used for the options as for the cluster. When using the bulk `id` endpoint, the options are identified by Propeller option `id`. If an option with such `id` doesn't already exist, it will be created. If it does exist, the option will be updated.
ποΈ Bulk Cluster Products by sourceId
The bulk endpoints offer an efficient way of importing/updating large amounts of cluster products with just a single API call. The same lookup key is used for the products as for the cluster. When using the bulk `id` endpoint, the products are identified by Propeller product `id`. If a product with such `id` doesn't already exist, it will be created. If it does exist, the product will be updated.
ποΈ Bulk Clusters by Id
The bulk endpoints offer an efficient way of importing/updating large amounts of clusters with just a single API call. When using the bulk `id` endpoint, the clusters are identified by Propeller cluster `id`. If a cluster with such `id` doesn't already exist, it will be created. If it does exist, the cluster will be updated.
ποΈ Bulk Clusters by sourceId
The bulk endpoints offer an efficient way of importing/updating large amounts of clusters with just a single API call. When using the bulk `sourceId` endpoint, the clusters are identified by `sourceId` and `source`. If a cluster doesn't already exist, it will be created. If it does exist, the cluster will be updated.
ποΈ Bulk Companies by Id
The bulk endpoints offer an efficient way of importing/updating large amounts of companies with just a single API call. When using the bulk `id` endpoint, the companies are identified by `id`. If a company with such `id` doesn't already exist, it will be created. If it does exist, the company found will be updated.
ποΈ Bulk Companies by source id
The bulk endpoints offer an efficient way of importing/updating large amounts of companies with just a single API call. When using the bulk `sourceId` endpoint, the companies are identified by `sourceId` and `source`. If a company doesn't already exist, it will be created. If it does exist, the company found will be updated.
ποΈ Company Bulk Addresses
Use this endpoint to create multiple company addresses with a single API request. If an address with the code provided is found, it will be updated, otherwise a new address will be created. If the code is not provided, a new address will be created. When a new address is successfully created, the response will include the address `id`.
ποΈ Bulk Contacts by Id
The bulk endpoints offer an efficient way of importing/updating large amounts of contacts with just a single API call. When using the bulk `id` endpoint, the contacts are identified by `id`. If a contact doesn't already exist, it will be created. If it does exist, the contact found will be updated.
ποΈ Bulk Contacts by source id
The bulk endpoints offer an efficient way of importing/updating large amounts of contacts with just a single API call. When using the bulk `sourceId` endpoint, the contacts are identified by `sourceId` and `source`. If a contact doesn't already exist, it will be created. If it does exist, the contact found will be updated.
ποΈ bulk-cost-prices
6 items
ποΈ Customer Bulk Addresses
Use this endpoint to create multiple customer addresses with a single API request. If an address with the code provided is found, it will be updated, otherwise a new address will be created. If the code is not provided, a new address will be created. When a new address is successfully created, the response will include the address `id`.
ποΈ Bulk Customers by Id
The bulk endpoints offer an efficient way of importing/updating large amounts of customers with just a single API call. When using the bulk `id` endpoint, the customers are identified by `id`. If a customer doesn't already exist, it will be created. If it does exist, the customer found will be updated.
ποΈ Bulk Customers by source id
The bulk endpoints offer an efficient way of importing/updating large amounts of customers with just a single API call. When using the bulk `sourceId` endpoint, the customers are identified by `sourceId` and `source`. If a customer doesn't already exist, it will be created. If it does exist, the customer found will be updated.
ποΈ Bulk Inventory by lookup key / inventory type
The bulk inventory endpoint is used to create or update inventory records. The products can be identified based on one of their lookup keys. The inventory record type can be either `local` or `supplier`.
ποΈ Bulk Local Inventory (deprecated)
The bulk local inventory endpoint is used to create or update inventory records.
ποΈ bulk-prices
6 items
ποΈ Bulk Product by Id
The bulk endpoints offer an efficient way of importing/updating large amounts of products with just a single API call. When using the bulk `id` endpoint, the products are identified by Propeller product `id`. If a product with such `id` doesn't already exist, it will be created. If it does exist, the product will be updated.
ποΈ Bulk Product by source id
The bulk endpoints offer an efficient way of importing/updating large amounts of products with just a single API call. When using the bulk `sourceId` endpoint, the products are identified by `sourceId` and `source`. If a product doesn't already exist, it will be created. If it does exist, the product found will be updated.
ποΈ Bulk Supplier Inventory (deprecated)
The bulk supplier inventory endpoint is used to create or update inventory records.
ποΈ Bulk User Addresses
Use this endpoint to create multiple user addresses with a single API request. If an address with the code provided is found, it will be updated, otherwise a new address will be created. If the code is not provided, a new address will be created. When a new address is successfully created, the response will include the address `id`.
ποΈ Bulk Usergroup Addresses
Use this endpoint to create multiple usergroup addresses with a single API request. If an address with the code provided is found, it will be updated, otherwise a new address will be created. If the code is not provided, a new address will be created. When a new address is successfully created, the response will include the address `id`.
ποΈ Bulk Usergroups by Id
The bulk endpoints offer an efficient way of importing/updating large amounts of usergroups with just a single API call. When using the bulk `id` endpoint, the usergroups are identified by `id`. If a usergroup with such `id` doesn't already exist, it will be created. If it does exist, the usergroup found will be updated.
ποΈ Bulk Usergroups by source id
The bulk endpoints offer an efficient way of importing/updating large amounts of usergroups with just a single API call. When using the bulk `sourceId` endpoint, the usergroups are identified by `sourceId` and, `source`. If a usergroup doesn't already exist, it will be created. If it does exist, the usergroup found will be updated.
ποΈ Bulk Users by Id
The bulk endpoints offer an efficient way of importing/updating large amounts of user with just a single API call. When using the bulk `id` endpoint, the products are identified by `id`. If a user doesn't already exist, it will be created. If it does exist, the user found will be updated.
ποΈ Bulk Users by source id
The bulk endpoints offer an efficient way of importing/updating large amounts of user with just a single API call. When using the bulk `sourceId` endpoint, the users are identified by `sourceId` and `source`. If a user doesn't already exist, it will be created. If it does exist, the user found will be updated.
ποΈ bundles
9 items
ποΈ carriers
6 items
ποΈ categories
10 items
ποΈ Categories
Categories
ποΈ cluster-config
7 items
ποΈ Cluster Config
Cluster Config
ποΈ clusters
21 items
ποΈ Clusters
Clusters
ποΈ companies
15 items