External systems can exchange order-related information using the Orders Entity Views and Actions API.
The Views and Actions API is an authoring API designed to service a business user interface and is not optimized for integration scenario.
You should consider the following when using the Views and Actions API for your commerce integration:
Commerce views are exposed via the Authoring API. This Authoring API is based on OData, but is significantly simplified and more dynamically structured to support a data-driven user experience.
The Authoring API targets authoring and management experiences, while the Shops API targets runtime experiences for a shop or storefront. The Authoring API is logically separated from the Shops API to allow more direct control over the availability of functionality in different engine roles.
For example, you may want the Authoring API to be accessible on an internal instance of the Commerce Engine, but not on the Commerce Engine instance that is serving storefronts.
You can only add a line to an order when the status of the order is on hold.
To add a line item to a pending order using C#:
Get the entity view (the request must specify the order ID), for example:
EntityView view = Proxy.GetValue(query);
Specify the line item property and the quantity, for example:
Execute the action:
As shown in above example, calls to the Orders Views and Actions API typically include the following steps:
For any API calls to the XC Commerce Engine, you must:
Let us have coffee together and discuss your requirement for Sitecore. Mail us at firstname.lastname@example.org.