Skip to main content
POST
MergeLeadsAPI makes two lead identities one lead: the absorbed identity points

Authorizations

Authorization
string
header
required

An Erdo API key (erdo_api_...) or scoped token (erdo_token_...).

Path Parameters

datasetSlug
string
required
leadRef
string
required

Body

application/json
absorb_lead_id
string
required
overwrite_columns
string[]

Response

Success response

absorbed_lead_id
string

existing so the capture receipts referencing it stay accurate.

aliases_moved
integer<int64>
lead
CanonicalLead is everything an operator needs to judge one lead. · object
rows_combined
integer<int64>
state
string

the two were already one lead — which is also what a retry of an uncertain merge answers.