Recent modifications API #969
Description
(Just some notes): Calling /search?last_change>yesterday might be a valid way to identify what entities should be considered candidates for re-screen, but it's limited to 10000 results. We could offer a second API, /changes?since=TS which runs a scan on the ES index and returns all changed IDs.
The problem is still: now that you have this set of changed entities, how do you decide which customer records to forward-feed into the /match API again?