Managing Updates to Records

When a Validic customer has an active streaming API connection open, any updated user
data will be pushed by Validic through this connection for the customer to
process. In the case of receiving an event that updates a record, a developer would leverage the record ID to find the existing record in their system. When an updated record contains modified data the updated record’s checksum will be different than the existing record’s checksum. A final validation of the existing and updated record’s ‘created_at’ value can occur if there is concern about out of order processing.

The REST API use case is to serve on demand requests for users and is not the preferred method for consuming all of a user's data. However, any requests to the REST API after a user's data has been updated will result in the API returning the most recent data collected for that user given the parameters of the request.

What’s Next