API to merge leads?

  • 4 October 2021
  • 4 replies

Userlevel 2
Badge +4 has the API for leads.

However… it does not allow merging two leads (e.g. duplicates)

Looking at the network trace from the web UI, I can see we do a POST to'

where ###### is my company-id (e.g. my copper account id), and in the body:

{"ids":[ID1,ID2],"conflicts":{field: value, ...}

Is this correct? How come it is not exposed in the documented API?


This topic has been closed for comments

4 replies

Userlevel 7
Badge +7

Hi @donbowman, great question! I’ve pinged our internal API experts for this question. They’ll respond here shortly.

Userlevel 3
Badge +1

@donbowman the merge endpoint is not available to the developer API (aka documented API) due to inability to manage data conflicts between records. Within the web-app, the user is prompted of any conflicts and has to manually choose to which data to keep and which to delete. 

There are no plans of making this endpoint for the developer API. 

Userlevel 2
Badge +4

to be honest this seems a bit short sighted . The API used by the web interface would have been fine if accessible w/ my token since it allows specifying which data to keep etc already.


it makes impossible to programmatically merge *identical* leads.


is there a workaround?

Userlevel 3
Badge +1

There is unfortunately not a workaround at this time.