Merge Contact
POST /contacts/{contact_id}/merge
Merge secondary_id INTO this contact. THE SECONDARY STOPS EXISTING.
Both contacts must be writable by the key; the handler checks both.
Undo is one merge at a time via POST /duplicates/undo-merge/{id}.
Authorizations
Parameters
Path Parameters
The contact that SURVIVES the merge.
The contact that SURVIVES the merge.
Header Parameters
Request Body required
Merge secondary_id INTO the record in the path. The secondary stops existing.
Mirrors _MergeContactRequest / _MergeCompanyRequest, which are identical.
object
Decide individual fields instead of the app’s rules.
Which side of a merge wins one field.
object
Field name, e.g. CONTACT_JOB_TITLE.
Which record’s value to keep.
The record merged AWAY.
What prompted the merge. Recorded on the audit row.
Responses
200
Successful Response
object
An open envelope for one record, one dashboard or one job receipt.
Open because most of these reads are COMPUTED shapes - an engagement summary, a next-best-step, an intelligence status - that grow with the product, and dropping a field from an advisory read makes it say “nothing to report” rather than “we did not tell you”.
object
object
Whether there are more pages
Items per page
Current page number (1-indexed)
Total number of items
422
Validation Error