Contacts

Merge Contact

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}.

post/contacts/{contact_id}/merge

Request

  • Base URL: https://be.graph8.com/api/v1
  • URL: https://be.graph8.com/api/v1/contacts/{contact_id}/merge
  • Auth: HTTP bearer

Path parameters

contact_idinteger required

The contact that SURVIVES the merge.

Headers

Authorizationstring nullable
X-Target-Org-Idstring nullable

Request body

secondary_idinteger required

The record merged AWAY.

suggestion_idstring nullable

The duplicate suggestion this merge acts on, if any.

trigger'manual' | 'bulk_criterion'

What prompted the merge. Recorded on the audit row.

bulk_criterionstring nullable

The bulk criterion, when trigger is bulk_criterion.

Response

Successful Response

dataCrmRecordPayload required

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".

Changes

No recorded changes to this operation across all 2 revisions of this API.