Dedupe is based on specific criteria defined in the Dedupe policy. You can set up different dedupe policies - one for individual type of party and one for non-individual type. Each policy contains two sets of search criteria viz:-Confirmed Match - This set consists of criteria consisting of unique identification attributes related to a party. Each criterion can be a single identification attribute or a combination of two or more attributes. For example, in India criterion 1 could be Aadhar, criterion 2 could be PAN + mobile number. If a record matches any one of the criteria, then it is considered a confirmed match.Potential Match - This set consists of criteria that cannot be unique to any party. For example mobile number, name, date of birth etc. If a record matches any one of the criteria, it is considered a potential match.The following endpoints are available for dedupe configuration:Create a dedupe configuration
Retrieve all dedupe configurations
Update a dedupe configuration
Delete a dedupe configuration
Modify a dedupe configuration
Update a specific criterion in a dedupe configuration
Retrieve a specific dedupe configuration
Delete a specific dedupe configuration
Retrieve the dedupe configuration for a party type
Modified at 2025-03-05 10:58:37
