Product Catalog & Extensions endpoints
Verb | Path | Method |
|---|---|---|
POST | /api/v1/product_catalog/bulk_create_or_update/ | Upsert product catalog and extensions (extended product catalog) |
To proceed with this endpoint you must first validate the following points: 1. Create the product catalog configuration: Product Catalog endpoints 2. [Optional] Add dynamic schema for the extended catalog: Extensions endpoints 3. Add extension values allowed for the different extensions: Extensions endpoints
A product is uniquely identified by its code. If the product: 123AZERTY does not exist yet, it will be created with the following values. If it already exists, its attribute values will be updated using the new ones provided in the list in the example above.
As we also import the extended catalog, a product code can be present multiple times in the list. In this case, the attributes associated with this product code must always be the same. Otherwise, it will result in a conflict and raise an HTTP 400 error.
Extended catalog rows are uniquely identified by the product code and the values for the extensions.
If the extended catalog row already exists it will update the active column value.
If it does not exist yet, it will create it. The values provided for the extensions must appear in the business_extension table, otherwise, it will return a 400.
The data sent for the dynamic columns of the product catalog and the extended catalog are checked and cast to the right type. You can provide text data as long as it can be cast into the right type. Ex: “10.80” for float, “True” for bool.
Not providing the right type of data will result in a 400
Upon success, the response is 200 OK and returns
