Get Customers that have changed

Use of the Customer/CustomerChanges end point provides additional filtering and will have faster performance than using TServerMethodsWebAPI/Get_Customer_Changes. Filters such as the EffectiveDate, PageSize and PageNumber can allow pagination of the data being returned to reduce payload sizes.

This is more efficient than TServerMethodsWebAPI/Get_Customer_Changes method which required a second call to obtain the customer field information.

You must be using version 6.2.2.535 or 6.2.7.415 of the WebAPI to have this end point. Check the WebAPI version using TServerMethodsWebAPI\Connect.

Sample Customer Pseudocode

  • GET list of Customer/CustomerChanges filtered by last updated date
  • For each customer returned
    • Update customers in online shopping cart

Get_Customer_Changes

This endpoint is not recommended to use for any large amounts of data as it is known to have speed performance issues and is not efficient.

The TServerMethodsWebAPI/Get_Customer_Changes returns the list of customer Unique numbers that have changed since the Effective Date. It translates inside the API using an XML DOM which has a memory and performance impact. If you are using this end point, we strongly recommend updating to use Customer/CustomerChanges.

Back to WebAPI Samples