2 Replies Latest reply on Nov 21, 2017 8:02 AM by Markus Bianchi

    Custom deduplication / Sync Leads REST API

    Markus Bianchi

      As I wasn't able to find any information on that topic in the documentation, I was wondering if the "Sync Leads" REST API endpoint will honor custom deduplication rules (if set)? So, by default, the "Sync Leads" API endpoint will create or update persons based on the email address (if "lookupField" is not set). Will this default behaviour also change if a custom deduplication logic is setup by Support to e.g. "email" and "custom field" or is there any other way to set more than one "lookupField" (probably some kind of workaround as using more than one lookup field is not possible )?

       

      As an example, let's assume we have three persons in our database with the following information.

       

      IdEmail AddressCustom Field
      1test@test.comtest1
      2test@test.comtest2
      3test@test.comtest3

       

      If the custom deduplication is set to "Email Address" and "Custom Field" and I were to use the Sync Leads REST API endpoint with the following body...

       

      {
        "input": [
          {
            "email": "test@test.com",
            "customField": "test3"
          }
        ]
      }
      

       

      would the third person (id = 3) get updated?

       

      Many thanks,
      Markus