User Tools

Site Tools


webapi_swagger_documentation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
webapi_swagger_documentation [2020/02/10 10:18 (4 years ago)] – [Samples] kevinwebapi_swagger_documentation [2020/02/10 10:28 (4 years ago)] kevin
Line 140: Line 140:
   * Version 6.2.2.535 – November 20, 2019   * Version 6.2.2.535 – November 20, 2019
     * [57691/TFS 19695] Two new end points have been added to the S5WebAPI to provide faster and more efficient access to the information provided by the Record State Tracking feature.      * [57691/TFS 19695] Two new end points have been added to the S5WebAPI to provide faster and more efficient access to the information provided by the Record State Tracking feature. 
-    * GET [[webapi:examples:customer_changes|Customer/CustomerChanges]] returns all of the customer records that have changed in a single call.  This is better than /Get_Customer_Changes method which required a second call to obtain the customer field information. +    * GET [[webapi:examples:customer_changes|Customer/CustomerChanges]] returns all of the customer records that have changed in a single call.  This is more efficient than TServerMethodsWebAPI/Get_Customer_Changes method which required a second call to obtain the customer field information. 
     * GET [[webapi:examples:inventory_changes|Inventory/InventoryChanges]] returns a small sub-set of the inventory record, only the UniqueID, Sale Start and End Dates, Pricing and In Stock Quantity are returned. This makes the call far faster and provides the information most commonly used for updating an online shopping cart.     * GET [[webapi:examples:inventory_changes|Inventory/InventoryChanges]] returns a small sub-set of the inventory record, only the UniqueID, Sale Start and End Dates, Pricing and In Stock Quantity are returned. This makes the call far faster and provides the information most commonly used for updating an online shopping cart.
   * Version 6.2.2.517 – October 29, 2019   * Version 6.2.2.517 – October 29, 2019
Line 223: Line 223:
   * Version 6.2.7.415 – November 21, 2019   * Version 6.2.7.415 – November 21, 2019
     * [57691/TFS 19695] Two new end points have been added to the S5WebAPI to provide faster and more efficient access to the information provided by the Record State Tracking feature.      * [57691/TFS 19695] Two new end points have been added to the S5WebAPI to provide faster and more efficient access to the information provided by the Record State Tracking feature. 
-    * GET [[webapi:examples:customer_changes|Customer/CustomerChanges]] returns all of the customer records that have changed in a single call.  This is better than /Get_Customer_Changes method which required a second call to obtain the customer field information. +    * GET [[webapi:examples:customer_changes|Customer/CustomerChanges]] returns all of the customer records that have changed in a single call.  This is more efficient than TServerMethodsWebAPI/Get_Customer_Changes method which required a second call to obtain the customer field information. 
     * GET [[webapi:examples:inventory_changes|Inventory/InventoryChanges]] returns a small sub-set of the inventory record, only the UniqueID, Sale Start and End Dates, Pricing and In Stock Quantity are returned. This makes the call far faster and provides the information most commonly used for updating an online shopping cart.     * GET [[webapi:examples:inventory_changes|Inventory/InventoryChanges]] returns a small sub-set of the inventory record, only the UniqueID, Sale Start and End Dates, Pricing and In Stock Quantity are returned. This makes the call far faster and provides the information most commonly used for updating an online shopping cart.
   * Version 6.2.7.414 – November 21, 2019   * Version 6.2.7.414 – November 21, 2019
webapi_swagger_documentation.txt · Last modified: 2022/02/23 13:40 (2 years ago) by kevin