For accounts that were using the previous version of InkSoft and then transitioned into our SalesDoc environment, some API call changes will be necessary if you are currently using these calls.
The information below gives a breakdown of these changes:
1. Changed the Id and ItemGuid for OrderShipmentPackageItem
A. Changed Id to Guid
B. Changed OrderRetailItemSizeId to ItemGuid
2. Any structure that had a RetailItemId, CartRetailItemId, OrderRetailItemId, RetailItemSizeId, CartRetailItemSizeId, or OrderRetailItemSizeId has been changed. These properties have been removed and we recommend you use the UniqueId field instead.
3. Integer “SessionId” parameter is no longer accepted in many API calls. The Globally Unique ID (UUID) “SessionToken” parameter should be used instead. The signatures for these endpoints have been updated to expect a UUID “SessionToken” parameter in place of the former SessionId (or in a few cases, the endpoint is altogether removed):
Endpoint |
Change Description |
{storeUri}/Api2/GetCart |
Endpoint is eliminated |
{storeUri}/Api2/GetCartCheckoutFieldValues |
Endpoint is eliminated |
{storeUri}/Api2/SetCartCheckoutFieldValues |
Endpoint is eliminated |
{storeUri}/Api2/GetCartPackage |
SessionId parameter has been removed |
{storeUri}/Api2/GetShippingMethods |
SessionId parameter has been removed |
{storeUri}/Api2/SaveArt |
SessionId parameter has been removed |
{storeUri}/Api2/SaveCartOrder |
SessionId parameter has been removed |
{storeUri}/Api2/SetCart |
SessionId parameter has been removed |
{storeUri}/Api2/UploadArt |
SessionId parameter has been removed |
{storeUri}/Api2/CreateMobileUploadRequest |
Endpoint is eliminated |
{storeUri}/Api2/SendArtEmail |
Endpoint is eliminated |
{storeUri}/Api2/SendDesignEmail |
SessionId parameter has been removed |
GetCart/{StoreID}/{SessionToken}/{CartRetailItemID}/{ReadyToOrder}/{IncludeAddOns} |
SessionId parameter has been removed |
SendDesignEmail/{StoreID}/{SessionToken}/{UserID}/{DesignID} |
SessionId parameter has been removed |
You can read more about our API here! If you have any questions, please let us know!
Comments
0 comments
Article is closed for comments.