One of the main uses of the Get Lead Changes endpoint for the REST API is to retrieve previous value data, often when some process has gone awry and values need to be reverted. In high-activity instances, there may be several things changing a data value, however—even if you attempt to constrain by using a generated static list for relevant changes, if a value changes multiple times, you wind up getting noise in your results to try to find the original data value change. Given that all Data Value Change activities will always have an associated Reason attribute, would it be possible to add a Reason filter when retrieving data? This would streamline the process of retrieving data for reversions.
... View more