FYNDNA retail banking suite
  1. Dedupe configuration
FYNDNA retail banking suite
  • Party deduplication
    • Dedupe configuration
      • Create dedupe configuration
        POST
      • Retrieve all dedupe configurations
        GET
      • Update a dedupe configuration
        PUT
      • Delete a dedupe configuration
        DELETE
      • Modify a dedupe configuration
        POST
      • Update a specific criterion in a dedupe configuration
        PATCH
      • Retrieve a specific dedupe configuration
        GET
      • Delete a specific dedupe configuration
        DELETE
      • Retrieve the dedupe configuration for a party type
        GET
    • Dedupe execution
      • Initiate synchronous dedupe
      • Initiate asynchronous dedupe
    • Dedupe results
      • Retrieve dedupe results
  1. Dedupe configuration

Update a dedupe configuration

PUT
/party-dedupe-criteria-configuration
Deduplication is based on specific criteria defined in the dedupe policy. Each policy is a dedupe configuration. You can update a dedupe configuration using this endpoint. For example, if "Aadhar" is already a part of the dedupe criteria, you can add "full name" to it as an additional criterion. This indicates that dedupe check should be performed against the Aadhar number and the full name of the party/prospect.
Note that you cannot add new dedupe criteria or delete an existing criterion from the policy, using this end point. Use the "Modify a dedupe configuration" endpoint for these purposes.

Request

Body Params application/json

Examples

Responses

🟢200OK
*/*
OK
Body

🟠400Bad Request
Request Request Example
Shell
JavaScript
Java
Swift
curl --location --request PUT 'https://dev.your-api-server.com/party-dedupe-criteria-configuration' \
--header 'Content-Type: application/json' \
--data-raw '[
    {
        "criteriaId": "37ed6422-68ac-44bd-9ab9-75c9ced5a202",
        "status": "ACTIVE",
        "version": "0",
        "createdOn": "2024-08-24T14:15:22.123Z",
        "createdBy": "system",
        "updatedOn": "2024-10-18T14:15:22.123Z",
        "updatedBy": "system",
        "dirty": true,
        "deleted": true,
        "jsonContent": {
            "extensionFields": {},
            "partyType": "INDIVIDUAL",
            "partySearchPolicyType": "CONFIRMED",
            "criteriaName": "PAN",
            "attributes": [
                "panNumberIndividual"
            ]
        }
    }
]'
Response Response Example
200 - Example 1
[
    {
        "criteriaId": "37ed6422-68ac-44bd-9ab9-75c9ced5a202",
        "status": "ACTIVE",
        "version": "0",
        "createdOn": "2024-08-24T14:15:22.123Z",
        "createdBy": "system",
        "updatedOn": "2024-10-18T14:15:22.123Z",
        "updatedBy": "system",
        "jsonContent": {
            "extensionFields": {},
            "partyType": "INDIVIDUAL",
            "partySearchPolicyType": "CONFIRMED",
            "criteriaName": "PAN",
            "attributes": [
                "panNumberIndividual"
            ]
        }
    }
]
Modified at 2025-02-17 09:34:26
Previous
Retrieve all dedupe configurations
Next
Delete a dedupe configuration
Built with