2024 Changelog
Customer Segment Service - new endpoint for checking match criteria
attention
This functionality is in preview mode — some of the features may not be fully operational yet.
Overview
We extended the service with a new endpoint for checking which items match specified criteria. This endpoint allows you to specify IDs of products and IDs of segments to check which of the products are assigned to any of the provided segments. The response includes the IDs of products that belong to one of the provided segments (directly or indirectly through a category).
Added endpoints
Endpoint | Description |
---|---|
Checking which items match criteria | Checking which items belong to segment. |
Known problems
There are no known problems.
Cart Service - added information about legalEntity
Overview
The request and response bodies of endpoints for managing carts were extended withlegalEntityId
field.Updated endpoints
Endpoint | Description |
---|---|
Creating a new cart | The request body has a new field - legalEntityId . |
Updating a cart | The request body has a new field - legalEntityId . |
Retrieving a cart's details by criteria | The response body has a new field - legalEntityId . |
Retrieving a cart's details by ID | The response body has a new field - legalEntityId . |
Known problems
There are no known problems.
Customer Segment Service - endpoints for retrieving items assignments
attention
This functionality is in preview mode — some of the features may not be fully operational yet.
Overview
We added new API for retrieving items assignments and category trees of category assignments.
Added endpoints
Endpoint | Description |
---|---|
Retrieving category trees for a customer segments | It retrieves category trees for the customer segments. |
Retrieving all items assignments for a customer segments | It retrieves all items assignments for the customer segments. |
Known problems
There are no known problems.
Category Service - new query parameter
Overview
Query parametersegmentsIds
has been added to GET category assignments endpoint. The new query parameter allows to filter the assigned resources by the segmentsIds - only category assignments will be returned which category is assigned to provided segments list.Updated endpoints
Endpoint | Description |
---|---|
Retrieving resources assigned to a category | The new query parameter segmentsIds has been added. |
Known problems
There are no known problems.
AI Service - Completion functionality
Overview
The AI Service supports completion functionality. Generates a completion based on conversation history.
Updated endpoints
Endpoint | Description |
---|---|
AI Completions | Generates a completion based on conversation history. |
Known problems
There are no known problems.
Order Service - Q-param behaviour
Overview
The q-param accepts string values both with and without quotes, while number values should be provided without quotes.
Updated endpoints
Endpoint | Description |
---|---|
Retrieving orders | Q-param accepts string values both with and without quotes. Number values should be provided without quotes. |
Retrieving a list of orders | Q-param accepts string values both with and without quotes. Number values should be provided without quotes. |
Known problems
There are no known problems.
Availability Service - upsert operation support
Overview
The Availability Service supportsUPSERT
operation. The PUT
method updates the availability for given product and site or creates a new one if such a availability does not exist yet.Updated endpoints
Endpoint | Description |
---|---|
Upserting availability information of a product | Sending a request to the upsert endpoint with a non-existing product availability creates a new availability for the given product and site. |
Known problems
There are no known problems.
Price Service - upsert operation support
Overview
The Price Service supportsUPSERT
operation. The PUT
method updates the price with the given id or creates a new one if such a price does not exist yet.Updated endpoints
Endpoint | Description |
---|---|
Upserting a price | Sending a request to the upsert endpoint with a non-existing price id creates a new price with the given id. |
Upserting multiple prices | Sending a request to the upsert endpoint with a non-existing price id creates a new price with the given id. |
Upserting a price model | Sending a request to the upsert endpoint with a non-existing price model id creates a new price model with the given id. |
Upserting a price list | Sending a request to the upsert endpoint with a non-existing price list id creates a new price list with the given id. |
Upserting a price in a price list | Sending a request to the upsert endpoint with a non-existing price id creates a new price with the given id for the specified price list. |
Upserting multiple prices in a price list | Sending a request to the upsert endpoint with a non-existing price id creates a new price with the given id for the specified price list. |
Known problems
There are no known problems.
Product Service - upsert operation support
Overview
The Product Service supportsUPSERT
operation. The PUT
method updates the product with the given id or creates a new one if such a product does not exist yet.
The Product Service has a new product.product_manage
was added to the product service.
The scopes product.product_update
, product.product_create
and product.product_delete
have been deprecated in favour of product.product_manage
.Updated endpoints
Endpoint | Description |
---|---|
Creating a new product | The endpoint requires a new product.product_manage scope, as the product.product_create scope is deprecated. |
Creating multiple products | The endpoint requires a new product.product_manage scope, as the product.product_create scope is deprecated. |
Upserting a product | The endpoint requires a new product.product_manage scope, as the product.product_update scope is deprecated. Sending a request to the upsert endpoint with a non-existing product id creates a new product with the given id. |
Upserting multiple products | The endpoint requires a new product.product_manage scope, as the product.product_update scope is deprecated. Sending a request to the upsert endpoint with a non-existing product id creates a new product with the given id. |
Partially updating a product | The endpoint requires a new product.product_manage scope, as the product.product_update scope is deprecated. |
Deleting a product | The endpoint requires a new product.product_manage scope, as the product.product_delete scope is deprecated. |
Known problems
There are no known problems.
Customer Management Service - upsert operation support
Overview
The Customer Management Service supportsUPSERT
operation. For LegalEntity, Location and ContactAssignment the PUT
method updates an entity with the given id or creates a new one if such a entity does not exist yet.Updated endpoints
Endpoint | Description |
---|---|
Upserting a legal entity | Sending a request to the upsert endpoint with a non-existing legal entity id creates a new legal entity with the given id. |
Upserting a location | Sending a request to the upsert endpoint with a non-existing location id creates a new location with the given id. |
Upserting a contact assignment | Sending a request to the upsert endpoint with a non-existing contact assignment id creates a new contact assignment with the given id. |
Known problems
There are no known problems.
Coupon Service - new segment-related fields
Overview
FieldssegmentRestricted
and restrictions.segments
were added to coupon's model. The new fields allow to keep information about segments restrictions in the coupon.Updated endpoints
Endpoint | Description |
---|---|
Creating a new coupon | The request body has new fields - segmentRestricted and restrictions.segments . |
Updating the coupon by code | The request body has new fields - segmentRestricted and restrictions.segments . |
Partially updating the coupon by code | The request body has new fields - segmentRestricted and restrictions.segments . |
Retrieving information about particular coupon by code | The response body has new fields - segmentRestricted and restrictions.segments . |
Retrieving list of coupons by criteria | The response body has new fields - segmentRestricted and restrictions.segments . |
Known problems
There are no known problems.
Coupon Service - added information about legalEntity to redemption endpoints
Overview
The request and response bodies of endpoints for redeeming coupons were extended withlegalEntityId
field. It means that if a customer is assigned to many legal entities then he can redeem coupons separately for each of them.Updated endpoints
Endpoint | Description |
---|---|
Validating redeemability of a coupon | The request body has a new field - legalEntityId . |
Redeeming the coupon by creating a redemption | The request body has a new field - legalEntityId . |
Retrieving a coupon redemption | The response body has a new field - legalEntityId . |
Retrieving a list of redemptions by criteria | The response body has a new field - legalEntityId . |
Known problems
There are no known problems.
Customer Service - added information about legalEntities and businessModel
Overview
FieldslegalEntities
and businessModel
were added to customer's model. The new fields are readonly and gives instant information whether customer is of B2B or B2C business model.Updated endpoints
Endpoint | Description |
---|---|
Retrieving a customer's own profile | The response has two new fields - b2b.legalEntities and businessModel . |
Retrieving a customer's profile | The response has two new fields - b2b.legalEntities and businessModel . |
Retrieving a list of customers | The response has two new fields - b2b.legalEntities and businessModel . |
Known problems
There are no known problems.
IAM Service Service - upsert operation support for groups and assignments
Overview
The IAM Service supportsUPSERT
operation for groups and assignment. The PUT
method updates the user group with the given id or creates a new one if such a group does not exist yet.
A new scope iam.group_manage
was added to the IAM service.
The scopes iam.group_update
, iam.group_create
and iam.group_delete
have been deprecated in favour of iam.group_manage
.Updated endpoints
Endpoint | Description |
---|---|
Creating a new group | The endpoint requires a new iam.group_manage scope, as the iam.group_create scope is deprecated. |
Upserting a group | The endpoint requires a new iam.group_manage scope, as the iam.group_update scope is deprecated. Sending a request to the upsert endpoint with a non-existing group id creates a new catalog with the given id. |
Deleting a group | The endpoint requires a new iam.group_manage scope, as the iam.group_delete scope is deprecated. |
Adding a user to a group | The endpoint requires a new iam.assignment_manage scope, as the iam.assignment_create scope is deprecated. |
Removing all users from a group | The endpoint requires a new iam.assignment_manage scope, as the iam.assignment_delete scope is deprecated. |
Removing a user from a group | The endpoint requires a new iam.assignment_manage scope, as the iam.assignment_delete scope is deprecated. |
Removing a user from all groups | The endpoint requires a new iam.assignment_manage scope, as the iam.assignment_delete scope is deprecated. |
Upserting user assignment to a group | New endpoint that allows to create or update group assignment. |
Known problems
There are no known problems.
Catalog Service - upsert operation support
Overview
The Catalog Service supportsUPSERT
operation. The PUT
method updates the catalog with the given id or creates a new one if such a catalog does not exist yet.
A new scope catalog.catalog_manage
was added to the catalog service.
The scopes catalog.catalog_update
, catalog.catalog_create
and catalog.catalog_delete
have been deprecated in favour of catalog.catalog_manage
.Updated endpoints
Endpoint | Description |
---|---|
Creating a new catalog | The endpoint requires a new catalog.catalog_manage scope, as the catalog.catalog_create scope is deprecated. |
Upserting a catalog | The endpoint requires a new catalog.catalog_manage scope, as the catalog.catalog_update scope is deprecated. Sending a request to the upsert endpoint with a non-existing catalog id creates a new catalog with the given id. |
Partially updating a catalog | The endpoint requires a new catalog.catalog_manage scope, as the catalog.catalog_update scope is deprecated. |
Removing a catalog | The endpoint requires a new catalog.catalog_manage scope, as the catalog.catalog_delete scope is deprecated. |
Known problems
There are no known problems.
Customer Service - upsert operation support
Overview
The Customer Service support theUPSERT
operation. The PUT
method updates the customer with the given id or creates a new one if such a customer does not exist yet. The same applies to customer's address PUT
method.
The field metadata.version
is now optional to support the UPSERT
operation. When you don't provide the value, the optimistic locking is not enabled.
The Customer Service has a new customer.customer_manage
scope.
The scopes customer.customer_update
, customer.customer_create
and customer.customer_delete
have been deprecated in favour of customer.customer_manage
.Updated endpoints
Endpoint | Description |
---|---|
Creating a customer | The endpoint requires a new customer.customer_manage scope, as the customer.customer_create scope is deprecated. |
Upserting a customer profile | The endpoint requires a new customer.customer_manage scope, as the customer.customer_update scope is deprecated. Sending a request to the upsert endpoint with a non-existing customer id creates a new customer with the given id. |
Partially updating a customer profile | The endpoint requires a new customer.customer_manage scope, as the customer.customer_update scope is deprecated. |
Assigning an account to an existing customer profile | The endpoint requires a new customer.customer_manage scope, as the customer.customer_update scope is deprecated. |
Deleting a customer profile | The endpoint requires a new customer.customer_manage scope, as the customer.customer_delete scope is deprecated. |
Adding a customer address | The endpoint requires a new customer.customer_manage scope, as the customer.customer_update scope is deprecated. |
Upserting a customer address | The endpoint requires a new customer.customer_manage scope, as the customer.customer_update scope is deprecated. Sending a request to the upsert endpoint with a non-existing address id creates a new address with the given id. |
Partially updating a customer address | The endpoint requires a new customer.customer_manage scope, as the customer.customer_update scope is deprecated. |
Deleting a customer address | The endpoint requires a new customer.customer_manage scope, as the customer.customer_update scope is deprecated. |
Adding tags to a customer address | The endpoint requires a new customer.customer_manage scope, as the customer.customer_update scope is deprecated. |
Deleting tags from a customer address | The endpoint requires a new customer.customer_manage scope, as the customer.customer_update scope is deprecated. |
Known problems
There are no known problems.
Category Service - upsert improvements
Overview
The fieldmetadata.version
is now optional to support the UPSERT
operation. When you don't provide the value, the optimistic locking is not enabled.
The Category Service as a new category.category_manage
scope.
The scopes category.category_update
, category.category_create
and category.category_delete
have been deprecated in favour of category.category_manage
.Updated endpoints
Endpoint | Description |
---|---|
Creating a new category | The endpoint requires a new category.category_manage scope, as the category.category_create scope is deprecated. |
Upserting a category | The endpoint requires a new category.category_manage scope, as the category.category_update scope is deprecated. Sending a request to the upsert endpoint with a non-existing category id creates a new category with the given id. |
Partially updating a category | The endpoint requires a new category.category_manage scope, as the category.category_update scope is deprecated. |
Deleting a category | The endpoint requires a new category.category_manage scope, as the category.category_delete scope is deprecated. |
Assigning a resource to a category | The endpoint requires a new category.category_manage scope, as the category.category_update scope is deprecated. |
Assigning resources to a category | The endpoint requires a new category.category_manage scope, as the category.category_update scope is deprecated. |
Upserting a resource to a category assignment | The endpoint requires a new category.category_manage scope, as the category.category_update scope is deprecated. Sending a request to the upsert endpoint with a non-existing category assignment id creates a new assignment with the given id. |
Updating assignments | The endpoint requires a new category.category_manage scope, as the category.category_update scope is deprecated. |
Deleting a category assignment by reference id | The endpoint requires a new category.category_manage scope, as the category.category_update scope is deprecated. |
Deleting a category assignment by id | The endpoint requires a new category.category_manage scope, as the category.category_update scope is deprecated. |
Deleting all category assignments | The endpoint requires a new category.category_manage scope, as the category.category_update scope is deprecated. |
Known problems
There are no known problems.
Webhook Service - new events
attention
This functionality is now fully operational.
Overview
The new events were added to webhook-service.
Added events
Event | Description |
---|---|
client-management.contactassignment-created | The event is emitted when contact assignment is created. |
client-management.contactassignment-deleted | The event is emitted when contact assignment is deleted. |
client-management.contactassignment-updated | The event is emitted when contact assignment is updated. |
customer-segment.segment-created | The event is emitted when a customer segment is created. |
customer-segment.segment-deleted | The event is emitted when a customer segment is deleted. |
customer-segment.segment-updated | The event is emitted when a customer segment is updated. |
customer-segment.customer-assignment-created | The event is emitted when a customer assignment to a customer segment is created. |
customer-segment.customer-assignment-updated | The event is emitted when a customer assignment to a customer segment is updated. |
customer-segment.customer-assignment-deleted | The event is emitted when a customer assignment to a customer segment is deleted. |
customer-segment.item-assignment-created | The event is emitted when an item is assigned to a customer segment. |
customer-segment.item-assignment-deleted | The event is emitted when an item is unassigned from a customer segment. |
customer-segment.item-assignment-updated | The event is emitted when an item assignment to a customer segment is updated. |
site.site-created | The event is emitted when site is created. |
site.site-deleted | The event is emitted when site is deleted. |
site.site-updated | The event is emitted when site is updated. |
Known problems
There are no known problems.
Customer Segment Service - endpoints for managing B2C customer assignments
attention
This functionality is in preview mode — some of the features may not be fully operational yet.
Overview
We added new API for managing B2C customer assignments.
Added endpoints
Endpoint | Description |
---|---|
Retrieving a customer assignment | It retrieves a customer assignment. |
Upserting a customer assignment | It creates or updates a customer assignment. |
Deleting a customer assignment | It deletes a customer assignment. |
Known problems
There are no known problems.
Category Service - mixins validation
Overview
A new property is available in the category model -metadata.mixins
. It allows validation of mixins against the provided schema.Updated endpoints
Endpoint | Description |
---|---|
Creating a new category | We added metadata.mixins property. |
Upserting a category | We added metadata.mixins property. |
Partially updating a category | We added metadata.mixins property. |
Retrieving a list of categories | We added metadata.mixins property. |
Retrieving a category's details | We added metadata.mixins property. |
Retrieving parents for a category | We added metadata.mixins property. |
Retrieving subcategories for a category | We added metadata.mixins property. |
Known problems
There are no known problems.
IAM Service - custom ID support for groups
Overview
The IAM Service now supports custom IDs for group creation. If the ID is already in use, the service returns a 409 status code.
Updated endpoints
Endpoint | Description |
---|---|
Creating a new group | The id field added. |
Known problems
There are no known problems.
Customer Service - custom ID support for addresses
Overview
The Customer Service now supports custom IDs for customer's addresses creation. If the ID is already in use, the service returns a 409 status code.
Updated endpoints
Endpoint | Description |
---|---|
Adding a customer address | The id field added. |
Known problems
There are no known problems.
Customer Management Service - custom ID support
Overview
The Customer Management Service now supports custom IDs for Legal Entities, Locations, Contact Assignments creation. Theid
field can have 1 - 66 characters and must match ^[a-zA-Z0-9_-]$
regular expression.
If the ID is already in use, the service returns a 409 status code.Updated endpoints
Endpoint | Description |
---|---|
Creating a new legal entity | The id field added. |
Creating a new location | The id field added. |
Creating a new contact assignment | The id field added. |
Known problems
There are no known problems.
Customer-Management Service - search legal entities endpoint
Overview
The Customer-Management Service has been enhanced with the new endpoint which allows to retrieve legal entities that match criteria provided in request payload.
Added endpoints
Endpoint | Description |
---|---|
Searching for legal entities | The new endpoint which allows to retrieve legal entities by criteria provided in request payload |
Customer Segment Service - endpoints for managing segments
attention
This functionality is in preview mode — some of the features may not be fully operational yet.
Overview
We added new API for managing customer segments, items assigned to segments and customers assigned to segments.
Added endpoints
Endpoint | Description |
---|---|
Creating a segment | It creates a new segment. |
Retrieving segments | It retrieves segments. |
Searching for segments | It searches for segments. |
Retrieving a segment | It retrieves a segment. |
Updating a segment | It updates a segment. |
Patching a segment | It partially updates a segment. |
Deleting a segment | It deletes a segment. |
Creating segments in bulk | It creates segments in bulk. |
Updating segments in bulk | It updates segments in bulk. |
Deleting segments in bulk | It deletes segments in bulk. |
Retrieving customer assignments | It retrieves customer assignments. |
Searching for customer assignments | It searches for customer assignments. |
Retrieving a customer assignment | It retrieves a customer assignment. |
Upserting a customer assignment | It creates or updates a customer assignment. |
Deleting a customer assignment | It deletes a customer assignment. |
Upserting customer assignments in bulk | It creates or updates customer assignments in bulk. |
Deleting customer assignments in bulk | It deletes customer assignments in bulk. |
Retrieving item assignments | It retrieves item assignments. |
Searching for item assignments | It searches for item assignments. |
Retrieving an item assignment | It retrieves an item assignment. |
Updating an item assignment | It updates an item assignment. |
Removing an item assignment | It removes an item assignment. |
Upserting item assignments in bulk | It creates or updates item assignments in bulk. |
Deleting item assignments in bulk | It deletes item assignments in bulk. |
Known problems
There are no known problems.
Customer Service - custom ID support
Overview
The Customer Service now supports custom IDs for customer creation. Theid
field can have 1 - 66 characters and must match ^[a-zA-Z0-9_-]$
regular expression.
If the ID is already in use, the service returns a 409 status code.Updated endpoints
Endpoint | Description |
---|---|
Creating a new customer | The id field added. |
Known problems
There are no known problems.
Category Service - custom ID support
Overview
The Category Service now supports custom IDs for category creation. If the ID is already in use, the service returns a 409 status code. Along with that upsert operation was introduced that allows to create or update a category based on the provided ID.
Category assignments support upsert operation for single and multiple assignments.
Updated endpoints
Endpoint | Description |
---|---|
Creating a new category | The id field added. |
Upserting a category | The new endpoint that allows you to either create or update a category with a given id. |
Upserting a resource to a category assignment | The new endpoint that allows you to either create or update an assignment. |
Upserting multiple category assignments | The new endpoint that allows you to either create or update multiple assignments. |
Known problems
There are no known problems.
Catalog Service - custom ID support
Overview
The Catalog Service now supports custom IDs for catalog creation. Theid
field can have 1 - 66 characters and must match ^[a-zA-Z0-9_-]$
regular expression.
If the ID is already in use, the service will return a 409 status code.Updated endpoints
Endpoint | Description |
---|---|
Creating a new catalog | The id field added. |
Known problems
There are no known problems.
Order Service - discount calculation type
Overview
The discount model was expanded with a new field to include the coupondiscountCalculationType
property, which determines whether the discount is calculated based on the total or subtotal cart value.Updated endpoints
Endpoint | Description |
---|---|
Retrieving all orders | The discount.discountCalculationType field added. |
Creating an order | The discount.discountCalculationType field added. |
Retrieving an order | The discount.discountCalculationType field added. |
Updating an order | The discount.discountCalculationType field added. |
Partially updating an order | The discount.discountCalculationType field added. |
Known problems
There are no known problems.
Cart Service - discount calculation type
Overview
The discount model was expanded with a new field to include the coupondiscountCalculationType
property, which determines whether the discount is calculated based on the total or subtotal cart value.
Also total
object was expanded with discount
property, which holds discount amount for a given total
.Updated endpoints
Endpoint | Description |
---|---|
Retrieving all carts | The discount.discountCalculationType and total.discount fields added. |
Retrieving a cart | The discount.discountCalculationType and total.discount fields added. |
Applying a discount | The discountCalculationType field added. |
Retrieving all discounts | The discountCalculationType field added. |
Known problems
There are no known problems.
Coupon Service - discount calculation type
Overview
The coupon model was expanded with adiscountCalculationType
field, which determines whether the discount is calculated based on the total or subtotal order value.Updated endpoints
Endpoint | Description |
---|---|
Retrieving all coupons | The discountCalculationType field added. |
Creating a coupon | The discountCalculationType field added. |
Retrieving a coupon | The discountCalculationType field added. |
Updating a coupon | The discountCalculationType field added. |
Partially updating a coupon | The discountCalculationType field added. |
Known problems
There are no known problems.
Webhook Service - new event customer.email-change-request
type
attention
This functionality is now fully operational.
Overview
The event is emitted when a customer requests changing the email. For more information, see Customer events.
Known problems
There are no known problems.
Order Service - introduction of feeYrnAggregate
and fees
fields
Overview
New fieldsfeeYrnAggregate
and fees
were introduced. The feeYrnAggregate
field was added to the order model and the fees
field was added to the order entry model. This change allows adding custom externally sources fees to the customer's order.Updated endpoints
Endpoint | Description |
---|---|
Retrieving orders | The response body schema contains feeYrnAggregate and fees fields. |
Creating a new order | The request body schema contains feeYrnAggregate and fees fields. |
Retrieving a specific order by ID | The response body schema contains feeYrnAggregate and fees fields. |
Updating an order | The request body schema contains feeYrnAggregate and fees fields. |
Partially updating an order | The request body schema contains feeYrnAggregate and fees fields. |
Retrieving a list of orders | The response body schema contains feeYrnAggregate and fees fields. |
Creating a new order | The request body schema contains feeYrnAggregate and fees fields. |
Retrieving order details | The response body schema contains feeYrnAggregate and fees fields. |
Known problems
There are no known problems.
Cart Service - introduction of externalFees
field
Overview
New fieldexternalFees
was added to the cart item model. This change allows to calculate custom external fees at the customer's cart level.Updated endpoints
Endpoint | Description |
---|---|
Retrieving a cart's details by criteria | The response body schema of items field contains new field externalFees . |
Retrieving a cart's details by ID | The response body schema of items field contains new field externalFees . |
Adding multiple products to cart | The request body schema contains new field externalFees . |
Retrieving all products added to a cart | The response body schema contains new field externalFees . |
Adding a product to cart | The request body schema contains new field externalFees . |
Retrieving a cart item | The response body schema contains new field externalFees . |
Updating a cart item | The request body schema contains new field externalFees . |
Known problems
There are no known problems.
Site Settings Service - taxDeterminationBasedOn
property added
Overview
The Site object was expanded with thetaxDeterminationBasedOn
property, which specifies whether tax calculation is based on a customer's billing or shipping address.
Default value is BILLING_ADDRESS
.info
countryCode
from the relevant address.
The default setting for a site is the billing address.If you set the tax determination as shipping address, the country for calculating tax is determined in the following order:
- For the cart service:
a. cart'scountryCode
b. if thecountryCode
is not provided for a cart, a customer's default shipping addresscountryCode
c. if a customer doesn't have a default shipping address, the first customer's shipping addresscountryCode
on the list
d. if a customer doesn't have any shipping addresses, the defaultcountryCode
from the site settings - For the checkout service:
a. a shipping addresscountryCode
, provided during checkout
b. if a shipping address is not provided, a customer's billing addresscountryCode
is taken as a fallback
Updated endpoints
Endpoint | Description |
---|---|
Retrieving sites | The taxDeterminationBasedOn property allows you to determine the address for relevant tax calculation. |
Retrieving a site | The taxDeterminationBasedOn property allows you to determine the address for relevant tax calculation. |
Creating a site | The taxDeterminationBasedOn property allows you to determine the address for relevant tax calculation. |
Updating a site | The taxDeterminationBasedOn property allows you to determine the address for relevant tax calculation. |
Partially updating a site | The taxDeterminationBasedOn property allows you to determine the address for relevant tax calculation. |
Known problems
There are no known problems.
Webhook Service - new event customer.email-change
type
attention
This functionality is now fully operational.
Overview
The event is emitted when a customer confirms changing the email. For more information, see Customer events.
Known problems
There are no known problems.
Product Service - introduction of brandId
and labelIds
field
Overview
New fieldsbrandId
and labelIds
were added to the product model. Use these fields instead of mixins.productCustomAttributes.brand
and mixins.productCustomAttributes.labels
.Updated endpoints
Endpoint | Description |
---|---|
Creating a new product | The request body schema contains two new fields brandId and labelIds . |
Retrieving a product's details | The response body schema contains two new fields brandId and labelIds . |
Retrieving a list of products | The response body schema contains two new fields brandId and labelIds . |
Upserting a product | The request body schema contains two new fields brandId and labelIds . |
Partially updating a product's details | The request body schema contains two new fields brandId and labelIds . |
Creating multiple products | The request body schema contains two new fields brandId and labelIds . |
Upserting multiple products | The request body schema contains two new fields brandId and labelIds . |
Known problems
There are no known problems.
Customer Management Service - name
field not mandatory
Overview
From now onname
field is no longer mandatory for creating and updating locations.Updated endpoints
Endpoint | Description |
---|---|
Creating location | name field in request payload is no longer mandatory |
Upserting location | name field in request payload is no longer mandatory |
Known problems
There are no known problems.
Customer Service - metadataCreatedAt
field in response
Overview
Responses from endpoints for retrieving customers were enriched with themetadataCreatedAt
field.Updated endpoints
Endpoint | Description |
---|---|
Retrieving customers | Response payload contains the metadataCreatedAt field. |
Retrieving a customer | Response payload contains the metadataCreatedAt field. |
Known problems
There are no known problems.
Cart Service - support for external prices
Overview
To handle external prices, the request payload now includes theitemType
and tax
properties. To fetch external prices, you also need to generate the cart.cart_manage_external_prices
scope, set the enableExternalPrices
system preference to true, set the price.type
to EXTERNAL
, and provide the tax
values.Updated endpoints
Endpoint | Description |
---|---|
Adding item to cart | The request includes the itemType and tax properties. |
Adding item to cart in batch | The request includes the itemType and tax properties. |
Updating item in cart | The request includes the itemType and tax properties. |
Known problems
There are no known problems.
Order Service - introduction of add entries endpoint
Overview
Order Service has a new endpoint that is responsible for modifying and adding new entries to a given order.
New endpoints
Endpoint | Description |
---|---|
Adding entries | A new endpoint for adding entries to existing orders. |
Known problems
There are no known problems.
Configuration Service - introduction of clients endpoint
Overview
Configuration Service has a new endpoint that is responsible for returning list of clients for given tenant.
New endpoints
Endpoint | Description |
---|---|
Retrieving clients | A new endpoint for retrieving clients. |
Known problems
There are no known problems.
Customer Service (customer-managed) - site
field for password reset requests
Overview
There is a new propertysite
added to password reset model and 'customer.password-reset' event message. It allows to save site from which password reset request was sent.Updated endpoints
Endpoint | Description |
---|---|
Requesting password reset | The site property added to password reset model. |
Known problems
There are no known problems.
Cart Service - introduction of refresh endpoint
Overview
Cart Service has a new endpoint that is responsible for refreshing a specified cart and its items. If the prices assigned to the items in a cart have changed, invoking the endpoint recognizes the changes and reassigns them in the cart.
New endpoints
Endpoint | Description |
---|---|
Refreshing a cart | A new endpoint that refreshes a specified cart and its items. |
Known problems
There are no known problems.
Shopping-list Service - removal of deprecated endpoints
All previously deprecated endpoints are now removed.
Removed endpoints
Endpoint |
---|
Fetching all shopping lists - GET /shoppinglists |
Creating a shopping list - POST /shoppinglists |
Updating a shopping list - PUT /shoppinglists |
Removing a shopping list - DELETE /shoppinglists |
Fetching a shopping list - GET /shoppinglists/{customerNumber} |
Shipping Service - support for slot delivery method quote
Overview
Shipping Service has a new endpoint that is responsible for calculating the delivery cost for a slot delivery method. Additionally, the cart service can now calculate the shipping cost based on the selected delivery window slot if you provide the slot id and window id.
New endpoints
Endpoint | Description |
---|---|
Calculating the shipping cost for a given slot | A new endpoint that retrieves the minimum delivery cost for a given time slot. |
Known problems
There are no known problems.
Shopping List Service - support for shopping lists mixins
Overview
Shopping List Service from now on supports the mixins feature. Two new properties are available in the model -mixins
and metadata.mixins
.Updated endpoints
Endpoint | Description |
---|---|
Fetching all shopping lists | We added the mixins and metadata.mixins properties. |
Creating a shopping list | We added the mixins and metadata.mixins properties. |
Updating a shopping list | We added the mixins and metadata.mixins properties. |
Fetching a shopping list | We added the mixins and metadata.mixins properties. |
Known problems
There are no known problems.
Webhook Service - new HTTP header for HTTP Webhook Strategy
Overview
A new HTTP headeremporix-event-publish-time
is from now on attached to all requests sent to destinationUrl
of HTTP Webhook Strategy. This header contains a timestamp in RFC3339 UTC "Zulu" format informing about the time at which the message was published.Known problems
There are no known problems.
Schema Service - PRICE_LIST
type support
Overview
We extended the schema with a newPRICE_LIST
type.Updated endpoints
Endpoint | Description |
---|---|
Creating a schema | The new type is available. |
Updating a schema | The new type is available. |
Updating types of a schema | The new type is available. |
Creating a reference | The new type is available. |
Updating a reference | The new type is available. |
Known problems
There are no known problems.
Schema Service - support for object attributes
Overview
Schema Service now supports object attributes. TheOBJECT
type was added to SchemaAttribute.type
enum and attributes
property was added to SchemaAttribute
object. The attributes
property contains information about the object's attributes.Updated endpoints
Endpoint | Description |
---|---|
Creating a schema | Schema attribute in the request body can now be of OBJECT type. |
Updating a schema | Schema attribute in the request body can now be of OBJECT type. |
Known problems
There are no known problems.
Schema Service - support for array attributes
Overview
Schema Service now supports array attributes.ARRAY
type was added to SchemaAttribute.type
enum and arrayType
property was added to SchemaAttribute
object. arrayType
property contains additional information about array - for example, what is the type of array items.Updated endpoints
Endpoint | Description |
---|---|
Creating a schema | Schema attribute in the request body can now be of ARRAY type. |
Updating a schema | Schema attribute in the request body can now be of ARRAY type. |
Known problems
There are no known problems.
Cart Service - support for discount deletion by code
Overview
The Cart Service has been updated to enable the removal of discounts using the discountcode
.- If no discount
code
is provided, all discounts are removed from the cart, maintaining previous functionality. - A new endpoint has been implemented for retrieving all discounts.
- A new attribute called
discountIndex
has been introduced to allow the removal of discounts by index.
Updated endpoints
Endpoint | Description |
---|---|
Retrieving all cart discounts | New endpoint for getting all discounts from a cart. |
Deleting discount by code | New query param codes that allows to remove discounts by provided code. |
Known problems
There are no known problems.
Price Service (v2) - support for price lists mixins
Overview
Price Service (v2) from now on supports the mixins feature for price lists. Two new properties are available in the model -mixins
and metadata.mixins
.Updated endpoints
Endpoint | Description |
---|---|
Retrieving all price lists | We added the mixins and metadata.mixins properties. |
Retrieving price list by id | We added the mixins and metadata.mixins properties. |
Creating a price list | We added the mixins and metadata.mixins properties. |
Updating a price list | We added the mixins and metadata.mixins properties. |
Known problems
There are no known problems.
Schema Service - support for nullable attributes
Overview
Schema Service now supports nullable attributes.nullable
boolean property was added to SchemaAttribute.metadata
object and this property informs whether the attribute could accept null or not. Default value is false
.Updated endpoints
Endpoint | Description |
---|---|
Creating a schema | Schema attribute in the request body can now be nullable. |
Updating a schema | Schema attribute in the request body can now be nullable. |
Known problems
There are no known problems.
Schema Service - support for DECIMAL
type
Overview
Schema Service now supportsDECIMAL
type. Supported multiplicity is 0.01
.Updated endpoints
Endpoint | Description |
---|---|
Creating a schema | Schema attribute in the request body can now be of DECIMAL type. |
Updating a schema | Schema attribute in the request body can now be of DECIMAL type. |
Known problems
There are no known problems.
Category Service - new endpoint for creating category assignments in bulk
Overview
A new endpoint has been introduced for creating category assignments in bulk. It allows to create up to 200 assignments by one request.
Updated endpoints
Endpoint | Description |
---|---|
Assigning resources to a category | New endpoint for creating category assignments in bulk. |
Known problems
There are no known problems.
Category Service - supercategoriesIds
in response
Overview
The endpoint for retrieving a list of categories for which the reference ID is assigned was enriched withexpandSupercategoriesIds
boolean query parameter. The parameter adds information about IDs of supercategories of a given category to the supercategoriesIds
response field.Updated endpoints
Endpoint | Description |
---|---|
Retrieving a list of categories of the assignment | New expandSupercategoriesIds parameter and supercategoriesIds field in response are available. |
Known problems
There are no known problems.
Webhook Service - new event customer.opt-in
type
attention
This functionality is now fully operational.
Overview
The event is emitted when a customer opts in. For more information, see Customer events.
Known problems
There are no known problems.
Checkout Service - guest checkout
Overview
We introduce the guest checkout functionality that makes it possible to complete a purchase without a customer account. Thecustomer
object in the request now contains the guest
field that indicates if a purchase is made by an anonymous or logged in customer.Updated endpoints
Endpoint | Description |
---|---|
Triggering a checkout | The customer object contains the guest field. If set to true , the checkout process proceeds for a guest customer without the need for registering or logging in. |
Known problems
There are no known problems.
Returns Service - returns for anonymous orders
Overview
The newrequestor.anonymous
and requestor.email
parameters allow creating returns for orders that were created by guest users without a customer account.Updated endpoints
Endpoint | Description |
---|---|
Creating a single return entity | New requestor.anonymous and requestor.email parameters are available. |
Known problems
There are no known problems.
Cart Service - couponDiscounts
field in response
Overview
Responses from endpoints for retrieving cart details were enriched with thecouponDiscounts
field. The couponDiscounts
is an array which contains pairs of couponId
and value
parameters that indicate how much the item's price was lowered by the given coupon.Updated endpoints
Endpoint | Description |
---|---|
Getting Carts | Response contains the couponDiscounts field. |
Getting Cart | Response contains the couponDiscounts field. |
Known problems
There are no known problems.
OAuth Service - deprecation of anonymous_token
parameter
Overview
Theanonymous_token
parameter is now deprecated when refreshing an anonymous token. We recommend using the refresh_token
parameter instead. The deprecated parameter will be removed in 6 months.Updated endpoints
Endpoint | Description |
---|---|
Refreshing an anonymous token | The anonymous_token parameter is now deprecated. |
Known problems
There are no known problems.
Quote Service - generation of quotes using the customer's email and usage of service tokens possibility
Overview
We introduced a new attributecustomerEmail
for the quote creation schema that allows you to create a quote using the customer's email address.We updated the Quote Service so that it allows for using a service token (generated from the API Keys in Developer Portal), which is not linked to any specific user. You can perform all Quote Service API operations using the service token. The merchant and customer access tokens can still be used with the Quote API. For more information, see Developer Portal.
Updated endpoints
Endpoint | Description |
---|---|
Creating a new quote | Use the customerEmail property to generate a quote for a user's contact email address instead of the customer ID. |
Known problems
There are no known problems.
Coupon Service - coupon code in both upper and lower cases
Overview
A new system preferenceenableCouponCodeCaseSensitivity
is available. It allows you to save the coupon code both in upper and lower case.Updated endpoints
Endpoint | Description |
---|---|
Creating a new coupon | You can save the code property in both upper and lower case. |
Known problems
There are no known problems.
Webhook Service - custom headers
Overview
Config for HTTP provider is now enriched with theheaders
property. It allows you to define a list of custom headers which are added to the HTTP request.Updated endpoints
Endpoint | Description |
---|---|
Creating a config | You can define custom headers in the request body. |
Updating a config | You can define custom headers in the request body. |
Partially updating a config | You can define custom headers in the request body. |
Known problems
There are no known problems.
Invoice Service - invoice API
Overview
There is a new API for generating and verifying invoice creation tasks.
New endpoints
Endpoint | Description |
---|---|
Creating invoice job | It creates a new invoice job. |
Retrieving invoice job | It retrieves invoice job details. |
Known problems
There are no known problems.
Category Service - published
field for assignments
Overview
There is a new propertypublished
added to assignment model that is updated automatically based on product published
attribute. It allows you to filter out assignments with unpublished products.Updated endpoints
Endpoint | Description |
---|---|
Retrieving category assignments | We introduced the hideUnpublishedProducts parameter. Additionally, we added the published attribute into the category assignment model. |
Known problems
There are no known problems.
Customer Management Service - contact to customer transformation
Overview
We introduced a new functionality for transforming a contact to a customer. The transformation happens whentype
property is changed from CONTACT
to CUSTOMER
.
The action causes sending two emails (if the emails are configured):- reset password email
- account activation confirmation email
Updated endpoints
Endpoint | Description |
---|---|
Updating customer | We introduced logic for changing a type from CONTACT to CUSTOMER . |
Known problems
There are no known problems.
Customer Management Service - contactDetails.tags
field
Overview
The location model has a newcontactDetails.tags
property. It allows for labeling the location.Updated endpoints
Endpoint | Description |
---|---|
Creating a location | Type property contactDetails.tags added. |
Retrieving all locations | Type property contactDetails.tags added. |
Retrieving a location | Type property contactDetails.tags added. |
Upserting a location | Type property contactDetails.tags added. |
Known problems
There are no known problems.
Cart Service - making cart item properties optional
Overview
Propertyprice.currency
for a cart item can be set as optional. There are new system preferences that allow you to disable validation for the property.Updated endpoints
Endpoint | Description |
---|---|
Adding multiple products to cart | Property price.currency can be optional. Validation is configurable by the system preferences. |
Adding a product to cart | Property price.currency can be optional. Validation is configurable by the system preferences. |
Updating a cart item | Property price.currency can be optional. Validation is configurable by the system preferences. |
Known problems
There are no known problems.
Webhook Service - configuration API update
attention
This functionality is in preview mode — some of the features may not be fully operational yet.
Overview
We extendedconfig
API. PATCH
operation is now available and DELETE
endpoint now includes the force
flag.Updated endpoints
Endpoint | Description |
---|---|
Removing a config | We added the force flag, which allows you to remove active configs. |
Added endpoints
Endpoint | Description |
---|---|
Partially updating a config | It partially updates a webhook config. |
Known problems
There are no known problems.
Availability Service - support for mixins
Overview
Availability Service from now on supports the mixins feature. Two new properties are available in the model -mixins
and metadata.mixins
.Updated endpoints
Endpoint | Description |
---|---|
Retrieving all availabilities for a site | We added the mixins and metadata.mixins properties. |
Retrieving an availability | We added the mixins and metadata.mixins properties. |
Creating an availability | We added the mixins and metadata.mixins properties. |
Upserting availability information of a product | We added the mixins and metadata.mixins properties. |
Retrieving product availabilities for a site | We added the mixins and metadata.mixins properties. |
Known problems
There are no known problems.
Indexing Service - configuration API
Overview
We released new API for configuring indexing providers. The functionality allows you to configure custom Algolia subscription and trigger reindexing the index.
Added endpoints
Endpoint | Description |
---|---|
Creating a config | It creates a new index config. |
Retrieving configs | It retrieves all index configs. |
Updating a config | It updates an index config. |
Retrieving a config | It retrieves an index config. |
Removing a config | It removes an index config. |
Retrieving public configs | It retrieves all index public configs. |
Retrieving a public config | It retrieves an index public config. |
Reindexing | It triggers reindex operation. |
Known problems
There are no known problems.
Webhook Service - configuration API
attention
This functionality is in preview mode — some of the features may not be fully operational yet.
Overview
We added new API for configuring webhook providers.
Added endpoints
Endpoint | Description |
---|---|
Creating a config | It creates a new webhook config. |
Retrieving configs | It retrieves webhook configs. |
Updating a config | It updates a webhook config. |
Retrieving a config | It retrieves a webhook config. |
Removing a config | It removes a webhook config. |
Known problems
There are no known problems.
Schema Service - CUSTOMER.ADDRESS
type support
Overview
We extended the schema with a newCUSTOMER.ADDRESS
type.Updated endpoints
Endpoint | Description |
---|---|
Creating a schema | The new type is available. |
Updating a schema | The new type is available. |
Updating types of a schema | The new type is available. |
Creating a reference | The new type is available. |
Updating a reference | The new type is available. |
Known problems
There are no known problems.